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 Network Error: self signed certificate in chain
- dynamodb type custid is not supported
- DynamoDB console unable to delete this item
- dynamodb unable to locate property for key attribute
- DynamoDB delete fails
- DynamoDB no attribute schema defined
- DynamoDB local is not available for stage test
- DynamoDB consistent read not working
- boto3 dynamodb client error
- dynamodb trigger no records processed
- dynamodb the table does not have the specified index
- DynamoDB string set may not be empty
- dynamodb number_value cannot be converted to string
- failed to list tables not authorized dynamodb
- dynamodb attribute does not exist
Tired of switching accounts and regions? Use Dynobase.
Try 7-day free trial. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase