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)
- localstack dynamodb not working
- could not transform a dynamodb amazonserviceexception to a compatible kinesis exception
- dynamodb net scan condition or not working
- accessdeniedexception dynamodb
- sls dynamodb install not working
- resourcenotfoundexception dynamodb nodejs
- 'dynamodb' object has no attribute 'table'
- missing required key 'key' in params dynamodb
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- lambda function not triggering from dynamodb
- DynamoDB ConditionalCheckFailedException
- dynamodb query not returning the full item
- dynamodb atomic counter not working
- appsync dynamodb not seeing all fields
Tired of switching accounts and regions? Use Dynobase.
First 7 days are. No credit card needed.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase