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 unknown error
- dynamodb index does not exist
- error retrieving dynamodb table item serializationexception
- dynamodb global secondary index does not project
- dynamodb table not exists
- dynamodb problem function call failed
- dynamodb-admin not working
- DynamoDB batch write is not working
- dynamodb query is not null
- dynamodb query is null
- dynamodb condition does not exist
- dynamodb consistent reads are not supported on global secondary indexes
- DynamoDB delete fails
- dynamodb validation error detected
- Dynamodb error 500
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today
Product Features
- New in Dynobase 3.0
- Semantic and Vector Search
- Schema Explorer
- Visual JSON Path Filtering
- Visual Item Diff
- MCP Server for AI Tools
- Use SQL with DynamoDB
- Import CSV To DynamoDB
- Import JSON To DynamoDB
- Export DynamoDB To JSON
- Export DynamoDB To S3
- Export DynamoDB To CSV
- DynamoDB Update Item
- DynamoDB Delete All Items
- DynamoDB Delete Item
- DynamoDB Create Table
- DynamoDB Delete Table
- DynamoDB Conditional Update
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase