Error: AWS DynamoDB errors ResourceNotFoundException
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)
- name key is not defined dynamodb
- dynamodb put function not working
- DynamoDB ValidationException: Query condition missed key schema element
- is not authorized to perform dynamodb:* on resource
- dynamodb put item not working
- DynamoDB Auto Scaling Not Working
- dynamodb query key condition not supported
- ValidationException: Invalid KeyConditionExpression: Attribute name is a reserved keyword;
- lambda function not triggering from dynamodb
- comparison operator does not return all attributes dynamodb
- DynamoDB Errors InvalidSignatureException Signature Expired
- dynamodb net scan condition or not working
- Error ValidationException: One or more parameter values were invalid: Type mismatch for key X expected: S actual: M
- DynamoDB Invalid UpdateExpression Syntax Error Token
- CORS Error DynamoDB
Tired of AWS Console? Try Dynobase.
Try 7-day free trial. No credit card needed.
© 2022 Dynobase