Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently you can configure a nonsensical AWS region for DynamoDB and it doesn't stop you - it'll just start using another region silently. I propose that we just check it's a valid region for the current SDK and throw an exception instead of proceeding.