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

Allow custom AWS regions for local DynamoDB instances #70

Closed
wants to merge 3 commits into from
Closed

Allow custom AWS regions for local DynamoDB instances #70

wants to merge 3 commits into from

Conversation

JordanBCX
Copy link

@JordanBCX JordanBCX commented May 6, 2020

DynamoDB local appears to segment tables by their region, and the credentials passed. Therefore, the GUI client must pass any region the user desire, and their requested credentials (Instead of randomly generating them), to access their data.

Everyone has a unique configuration, so it is hard to enforce required fields. The client does a good job at displaying errors, so end-users shouldn't be confused if there is a configuration error.

See Step 4 of the AWS documentation for running DynamoDB locally.

This should fix #68, by allowing any input to be used as a region for local connections.

I also took the liberty of fixing the remaining Linter errors while I was making these changes, there doesn't seem to be any ill-effect for doing so.

@cool-studio cool-studio closed this by deleting the head repository May 12, 2024
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

Successfully merging this pull request may close these issues.

Custom region support
2 participants