Dynamo DB local Image 2.0.0 security token

Question

The latest version of the amazon/dynamodb-local:2.0.0 was released recently. Since upgrading dynamo local is giving issues "The Access Key ID or security token is invalid." according to this documentation as long as you have the Access Key and Security key defined as something it should work. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.DownloadingAndRunning.html

My docker compose file looks identical to the one in the documentation.

Please advise how to fix this.

My docker compose file looks identical to the one in the documentation.

Please advise how to fix this.

Answer

Starting from version 2.0.0 and 1.23.0 DynamoDB local AWS_ACCESS_KEY_ID can contain only letters (A–Z, a–z) and numbers (0–9).

https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.DownloadingAndRunning.html

https://hub.docker.com/r/amazon/dynamodb-local

Answer

One reason you might encounter this behaviour is using non-maintained packages, which use access keys that are now considered invalid. This is discussed in https://github.com/99x/serverless-dynamodb-local/pull/298

To fix this, upgrade the packages to maintained forks (disclaimer: I am a contributor to these forks), for example:

- `dynamodb-localhost` -> [`aws-dynamodb-local`](https://github.com/raisenational/aws-dynamodb-local#migrating-from-dynamodb-localhost)
- `serverless-dynamodb-local` -> [`serverless-dynamodb`](https://github.com/raisenational/serverless-dynamodb#migrating-from-serverless-dynamodb-local)

Also see: https://repost.aws/articles/ARc4hEkF9CRgOrw8kSMe6CwQ/troubleshooting-the-access-key-id-or-security-token-is-invalid-error-after-upgrading-dynamodb-local-to-version-2-0-or-greater

Dynamo DB local Image 2.0.0 security token

関連するコンテンツ