Error: com amazonaws services dynamodbv2 model resourcenotfoundexception
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 Invalid UpdateExpression Syntax Error Token
- ExpressionAttributeValues contains invalid value: One or more parameter values were invalid: An AttributeValue may not contain an empty string
- dynamodb query key condition not supported
- Unable to start DynamoDB Local process
- 'dynamodb' object has no attribute 'table'
- ConfigError: Missing region in config
- DynamoDB ValidationException: Query condition missed key schema element
- ValidationException: Invalid KeyConditionExpression: Attribute name is a reserved keyword;
- requested resource not found aws dynamodb
- ImportError: No module named boto3 (DynamoDB)
- cannot find module 'dynamodb-doc'
- failed to begin subsegment named 'amazondynamodbv2': segment cannot be found.
- DynamoDB Key element does not match the schema
- AWS DynamoDB CredentialsError: Missing credentials in config
Tired of switching accounts and regions? Use Dynobase.
First 7 days are. No credit card needed.
© 2022 Dynobase