It lacks some of the features of original DynamoDB; it doesn't scale as well but has the same API for most of the calls, making it an excellent choice for offline testing and dev experiments. It's a fully managed, multi-region, multi-active, durable database with built-in security, backup and restore, and in-memory caching for internet-scale applications. Of course, we can run any container our heart desires; however, three containers will do in our case. The region, access_key and secret_access_key will default … Use this to customize the framework-internal communication, e.g., if services are started in different containers using docker-compose. Generally speaking, running container is better than running a jar file in your local computer because it gives you more flexibility and consistency. We will run one container for our serverless app, one for DynamoDB, and one for dynamodb-admin. Now we need to create a docker-compose.yml file. --region -r Region that dynamodb should be remotely executed. DynamoDB. So if you use the DynamoDB with no configuration specified it will default to using ‘docker-registry-repository’ as the respository_table name, and ‘docker-registry-version’ as the version_table name. Amazon DynamoDB 공식 문서를 보면 DynamoDB를 로컬 환경에 구축하는 3가지 방법을 제공합니다. The new Docker image also enables you to include DynamoDB local in your containerized builds and as part of your continuous integration testing. --stage -s Stage that dynamodb should be remotely executed. DEFAULT_REGION: AWS region to use when talking to the API (default: us-east-1). DynamoDB local Docker image enables you to get started with DynamoDB local quickly by using a docker image with all the DynamoDB local dependencies and necessary configuration built in. The local instance is provided by the used docker image (see below) The Region and the AWSProfileName are required to let the SDK know where to find your Amazon credentials and which region to use. So that image use by default in-memory dynamodb (what you can find by running docker inspect on that image) "CMD [\"-jar\" \"DynamoDBLocal.jar\" \"-inMemory\"]" So if you want to keep your data you need to do something like this in you docker-compose: tl;dr: Run DynamoDB locally using Docker: docker run -d -p 8000:8000 dwmkerr/dynamodb Try it out by opening the shell, localhost:8000/shell: That's all there is to it! --table_prefix -t Dynamodb Table name prefixs (E.g. There are two ways to run DynamoDB locally, (1) using a jar file or (2) using a docker image. AWS offers a DynamoDB local Docker image. HOSTNAME: Name of the host to expose the services internally (default: localhost). 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. Having DynamoDB running locally is handy for local development. Amazon DynamoDB is a key-value and document database that delivers single-digit millisecond performance at any scale.