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)
- ConfigError: Missing region in config
- DynamoDB Key element does not match the schema
- DynamoDB ValidationException: Query condition missed key schema element
- DynamoDB Invalid UpdateExpression Syntax Error Token
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- sls dynamodb install not working
- DynamoDB Internal Server Error
- AWS DynamoDB errors ResourceNotFoundException
- ImportError: No module named boto3 (DynamoDB)
- AWS DynamoDB CredentialsError: Missing credentials in config
- DynamoDB Network Error: self signed certificate in chain
- ValidationException: Invalid KeyConditionExpression: Attribute name is a reserved keyword;
- ExpressionAttributeValues contains invalid value: One or more parameter values were invalid: An AttributeValue may not contain an empty string
- Error ValidationException: One or more parameter values were invalid: Type mismatch for key X expected: S actual: M
Tired of AWS Console? Try Dynobase.
Try 7-day free trial. No credit card needed.
© 2021 Dynobase