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)
- dynamodb does not accept empty set
- dynamodb could not be mapped for type string
- DynamoDB ConditionalCheckFailedException
- lambda function not triggering from dynamodb
- dynamodb list_append if_not_exists not working
- Unable to start DynamoDB Local process
- ExpressionAttributeValues contains invalid value: One or more parameter values were invalid: An AttributeValue may not contain an empty string
- sls dynamodb install not working
- dynamodb cannot convert undefined or null to object
- DynamoDB TTL Not Working
- dynamodb cannot read property 's' of undefined
- DynamoDB Auto Scaling Not Working
- 'dynamodb' object has no attribute 'table'
- dynamodb-admin not working
- DynamoDB Local NoClassDefFoundError
Spend less time in the AWS console, use Dynobase.
Try 7-day free trial. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase