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 ConditionalCheckFailedException
- an expression attribute name used in the document path is not defined
- could not load profile default dynamodb
- aws.dynamodb.converter.unmarshall not working
- dynamodb connection timeout
- ConfigError: Missing region in config
- DynamoDB Network Error: self signed certificate in chain
- dynamodb can not resolve withkeyconditionexpression
- One or more parameter values were invalid: some AttributeDefinitions are not used
- dynamodb mapper save not persisting
- dynamodb list_append if_not_exists not working
- sls dynamodb install not working
- dynamodb getItem() is not a function
- 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
Login to the AWS Console less. Use Dynobase.
Try 7-day free trial. No credit card needed.
Product Features
DynamoDB Tools
DynamoDB Info
© 2024 Dynobase