AWS Developer Forums: DynamoDB Local loses tables? ...

AWS Developer Forums: DynamoDB Local loses tables? ...

One possibility is that your client is being initialized using EC2 Role credentials. These credentials change periodically, and the client automatically retrieves updated credentials from the EC2 instance metadata periodically. When this happens, the client starts using a new access key id. Since DynamoDB Local is local only and doesn't perform request authentication, it uses your access key as your "account identifier". So when the "account identifier" changes in the client, DynamoDB things that your client is a brand-new caller. Tables are unique to the "account identifier".

In other words, if you look in the directory in which you are running dynamodb local, you will likely see many *.db files all starting with ASIA. To fix this, you can instantiate your client with a fixed access key and secret key (NOTE: just use garbage hardcoded strings, not actual keys).

Please let us know if anything you're seeing on your side matches up, or if this doesn't solve the problem.

Read full article from AWS Developer Forums: DynamoDB Local loses tables? ...