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)
- failed to list tables not authorized dynamodb
- aws lambda dynamodb nodejs not working after few puts
- boto3 dynamodb unable to locate credentials
- DynamoDB Hostname Cannot Be Null
- dynamodb mapper save not persisting
- resourcenotfoundexception dynamodb nodejs
- dynamodb scan missing values
- sls dynamodb install not working
- cognitoidentitycredentials is not authorized to perform dynamodb describetable
- dynamodb converter not found for enhancedtype
- could not unconvert attribute dynamodb
- dynamodb query key condition not supported
- DynamoDB ValidationException: Query condition missed key schema element
- dynamodb unable to locate property for key attribute
- dynamodb cannot read properties of undefined
Tired of AWS Console? Try Dynobase.
Try 7-day free trial. No credit card needed.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase