Error: AWS DynamoDB errors ResourceNotFoundException
Answered by Rafal Wilinski
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)
- could not load profile default dynamodb
- DynamoDB Query Limit Not Working
- KMS Key Access Denied Error DynamoDB
- DynamoDB missing items
- dynamodb cannot convert undefined or null to object
- DynamoDB Invalid UpdateExpression Syntax Error Token
- DynamoDB string set cannot be empty
- Error ValidationException: One or more parameter values were invalid: Type mismatch for key X expected: S actual: M
- DynamoDB ConditionExpression not working
- cannot find module 'dynamodb-doc'
- DynamoDB table not updating
- CORS Error DynamoDB
- why is the GSI dynamodb not showing item count
- DynamoDB could not invoke null on class
- ConfigError: Missing region in config
Login to the AWS Console less. Use Dynobase.
Try 7-day free trial. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase