Error: AWS DynamoDB errors ResourceNotFoundException
Solution
DynamoDB responds with this error when you're trying to run an operation against non-existent or not active table.
Troubleshooting steps:
- Make sure you haven't made any spelling mistake in TableName parameter while running SDK/CLI operations. Table name must be exactly the same as the name of provisioned table. It's case sensitive so make sure capitalization is also correct.
- Make sure that your table exists and it's in ACTIVE state
- Check if you're using the same AWS account and correct region. DynamoDB Table must be in the same region as CLI/SDK configuration
- Make sure you or your resource (e.g. Lambda function) has correct IAM permissions to perform operations on selected table
Other Common DynamoDB Errors (with Solutions)
- DynamoDB Delete Not Working
- missing required key 'key' in params dynamodb
- dynamodb query key condition not supported
- dynamodb local shell not working
- dynamodb mapper save not persisting
- com amazonaws services dynamodbv2 model resourcenotfoundexception
- dynamodb does not accept empty set
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- dynamodb put item not working
- Float types are not supported. Use decimal types instead.
- DynamoDB Invalid UpdateExpression Syntax Error Token
- dynamodb connection timeout
- DynamoDB Code Working In Node But Not SAM
- AWS DynamoDB Provisioning Error
- DynamoDB Network Error: self signed certificate in chain
Dynobase is a Professional GUI Client for DynamoDB
Try 7-day free trial. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2023 Dynobase