Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No data saved at all on DynamoDB local. #61

Open
manodupont opened this issue Nov 8, 2019 · 5 comments
Open

No data saved at all on DynamoDB local. #61

manodupont opened this issue Nov 8, 2019 · 5 comments

Comments

@manodupont
Copy link

manodupont commented Nov 8, 2019

Is it normal to not see any Table from the command line aws tool

test@testmac test (master) $ aws dynamodb list-tables --endpoint http://localhost:8000
{
    "TableNames": []
}

Even if I created thousands of rows on DynamoDBGui Client ?!?!?

Am i missing something ?!! Whats the goal of that tool ?!

@manodupont
Copy link
Author

Heres what I have in my DynamoDBGui

Screenshot 2019-11-08 at 17 04 31

I should have one table. But i got none using the officiel aws client.
Yes i only have on server running at localhost:8000.

@skybleu
Copy link

skybleu commented Nov 28, 2019

Local DynamoDB has separate tables if you select different region or apiKey.

DynamoDB does not allow filling in those fields when you use Local tab.

I have mirror situation - no matter what region I set up in [dafault] section of ~/.aws/credentials i still have no tables visible in DynamoDBgui, while aws CLI shows me what I want and what my webapps see.

Conclusion would be that DynamoDBgui has hard-coded region or creds that are different than ones I'm using, while you guys use the region or creds same as DynamoDB gui but your ~/.aws/credentials has none or different settings in [default] section.

@Heanthor
Copy link

Heanthor commented Feb 3, 2020

Has anyone else been able to solve this? My tables created through the cli end up in us-east-1 and do not show up in the GUI, but I do not see the table I created through the GUI in the cli.

@Heanthor
Copy link

Heanthor commented Feb 3, 2020

^ fixed above, the solution was to add the -sharedDb option when starting Dynamo local. This removes the segmentation by environment/access key.

@eazytracer
Copy link

Had the same issue and did what @Heanthor suggested, added -sharedDb flag. However, docker would not run when passing that flag unless I also supplied the -jar argument. Full command that worked for me to start Docker local and connect with GUI:

docker run -d -p 8000:8000 amazon/dynamodb-local -jar DynamoDBLocal.jar -sharedDb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants