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.
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.