- Newest
- Most votes
- Most comments
Hi, it looks like the issue is with the region code you're using. eu-east-2 isn't listed on our region list:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html
It looks like you are using a region which does not exist. Check the value of your DynamoDBConfig.region
and ensure it points to a region listed here:
Code | Region |
---|---|
us-east-2 | US East (Ohio) |
us-east-1 | US East (N. Virginia) |
us-west-1 | US West (N. California) |
us-west-2 | US West (Oregon) |
af-south-1 | Africa (Cape Town) |
ap-east-1 | Asia Pacific (Hong Kong) |
ap-southeast-3 | Asia Pacific (Jakarta) |
ap-south-1 | Asia Pacific (Mumbai) |
ap-northeast-3 | Asia Pacific (Osaka) |
ap-northeast-2 | Asia Pacific (Seoul) |
ap-southeast-1 | Asia Pacific (Singapore) |
ap-southeast-2 | Asia Pacific (Sydney) |
ap-northeast-1 | Asia Pacific (Tokyo) |
ca-central-1 | Canada (Central) |
eu-central-1 | Europe (Frankfurt) |
eu-west-1 | Europe (Ireland) |
eu-west-2 | Europe (London) |
eu-south-1 | Europe (Milan) |
eu-west-3 | Europe (Paris) |
eu-north-1 | Europe (Stockholm) |
me-south-1 | Middle East (Bahrain) |
sa-east-1 | South America (São Paulo) |
Hi,
InvalidSignatureException
error is when your credentials for the IAM user may not have the right DynamoDB actions for that DynamoDB table or IAM user or for that specific region it is not authorised. As you have mentioned, on localhost it is working recheck the DynamoDB table or region it is using.
the issue was occurring because of the typo in the region where I had this: 'eu-east-2' instead of this: ''us-east-2'
Relevant content
- Accepted Answerasked 8 months ago
- asked 6 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
MY GOD! That was a typo, aaahggg! Thank you so much for the input, you've saved me several days!