Error: com amazonaws services dynamodbv2 model resourcenotfoundexception

Answered by Rafal Wilinski
What's Causing This Error
This error occurs in Java when you try to access a DynamoDB Table, GSI, or LSI that does not exist or is still in the "CREATING" status.
Solution - Here's How To Resolve It
First, verify that the region you've specified when initializing the SDK is the same region in which the DynamoDB tables are provisioned.
Then, verify that the table, LSI, or GSI name you are trying to access is correct.
Finally, visit the AWS Console to determine if the table is in the "Active" status. If your table has been created, you should see the status below.
Figure - Observing the table status in the DynamoDB console
Other Common DynamoDB Errors (with Solutions)
- DynamoDB ConditionalCheckFailedException
- Could not connect to the endpoint URL https:dynamodb.singapore.amazonaws.com
- dynamodb botocore.exceptions.nocredentialserror unable to locate credentials
- boto3 dynamodb unable to locate credentials
- dynamodb docker unable to open database file
- aws.dynamodb.converter.unmarshall not working
- DynamoDB Scan Not Working
- aws.dynamodb.documentclient is not a constructor
- dynamodb put item not working
- DynamoDB Error All Attributes Must Be Indexed
- sls dynamodb install not working
- DynamoDB Mapper Could Not Instantiate Class
- Error ValidationException: One or more parameter values were invalid: Type mismatch for key X expected: S actual: M
- DynamoDB Local Docker Not Working
- DynamoDB aliasing is not supported
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase