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 local unable to open database file
- DynamoDB missing items
- DynamoDB table not updating
- dynamodb scan missing values
- dynamodb value cannot be null. (parameter 'type')
- DynamoDB is missing the key id in the item
- dynamodb unknown error
- dynamodb condition does not exist
- DynamoDB ConditionExpression not working
- DynamoDB Get not found
- dynamodb put function not working
- KMS Key Access Denied Error DynamoDB
- DynamoDB stream not working
- DynamoDB Local Cannot Create Preexisting Table
- dynamodb local could not load credentials from any providers
Login to the AWS Console less. Use Dynobase.
First 7 days are. No credit card needed.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase