Install local dynamodb Offline#

version: '3.8'Ĭontainer_name: dynamoDbLocalDockerCompose docker stop mydynamodbĪlternatively, we can use docker-compose to run the container instead of using the docker build and run command with the existing Dockerfile. ReadCapacityUnits=10,WriteCapacityUnits=5Īws dynamodb list-tables -endpoint-url Once you stop the local dynamodb docker and restart it, you can still see the table created persists. ĭocker run -d -name mydynamodb -p 8000:8000 -v dynamodb-local:/home/dynamodblocal/db local-dynamodb-dataĪttributeName=SongTitle,AttributeType=S ^ Then build and run with the command below. See dynamodb-local-persist.Ĭreate a Dockerfile as below FROM amazon/dynamodb-localĬMD There is already an example available for both Dockerfile. We can do this by using Dockerfile to create a local data folder in the container and map it to the volume on the local machine. To persist data, the best option is to mount a volume to this. However, once you stop the container, all the data will be lost because everything is stored in memory. Now we can start creating tables and inserting data into this.

Install local dynamodb Offline#

It lacks some of the features of original DynamoDB it doesnt scale as well but has the same API for most of the calls, making it an excellent choice for offline testing and dev experiments. # installĭocker run -dp 8000:8000 -name localDynamoNoMount amazon/dynamodb-local DynamoDB Local is a mirror of the original AWS DynamoDB database but instead of behind managed in the cloud by AWS, it can run locally. We can pull the image and run it in your local machine easily. AWS offers a DynamoDB local Docker image. Generally speaking, running container is better than running a jar file in your local computer because it gives you more flexibility and consistency. There are two ways to run DynamoDB locally, (1) using a jar file or (2) using a docker image. Having DynamoDB running locally is handy for local development.