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 could not instantiate class
- dynamodb query not returning the full item
- One or more parameter values were invalid: some AttributeDefinitions are not used
- could not unmarshal the value dynamodb
- is not authorized to perform dynamodb:* on resource
- DynamoDB aliasing is not supported
- DynamoDB FilterExpression not working
- dynamodb unknown error
- DynamoDB query is slow
- DynamoDB delete fails
- Unable to start DynamoDB Local process
- DynamoDB stream lambda error
- dynamodb query key condition not supported
- dynamodb atomic counter not working
- DynamoDB parameter validation failed
Tired of AWS Console? Try Dynobase.
Try 7-day free trial. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase