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 1 validation error detected value
- dynamodb getItem() is not a function
- Boto3 DynamoDB KeyError
- dynamodb query not returning the full item
- dynamodb net scan condition or not working
- could not unconvert attribute dynamodb
- DynamoDB ValidationException: Query condition missed key schema element
- DynamoDB Is Unsupported It Cannot Be Instantiated
- why is the GSI dynamodb not showing item count
- DynamoDB Expression Not Null
- dynamodb mapper save not persisting
- aws lambda dynamodb nodejs not working after few puts
- requested resource not found aws dynamodb
- DynamoDB Error All Attributes Must Be Indexed
- ProvisionedThroughputExceededException DynamoDB
Tired of switching accounts and regions? Use Dynobase.
Try 7-day free trial. No credit card needed.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase