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 connection timeout
- dynamodb-admin not working
- DynamoDB ConditionalCheckFailedException
- failed to list tables not authorized dynamodb
- dynamodb converter not found for enhancedtype
- is not authorized to perform dynamodb:* on resource
- name key is not defined dynamodb
- cannot find module 'dynamodb-doc'
- DynamoDB Expression Not Null
- dynamodb autoscaling not fast enough
- DynamoDB Errors InvalidSignatureException Signature Expired
- dynamodb put item not working
- dynamodb list_append if_not_exists not working
- boto3 dynamodb unable to locate credentials
- DynamoDB Delete Method Not Working For The First Time
Tired of switching accounts and regions? Use Dynobase.
Try 7-day free trial. No credit card needed.
Product Features
DynamoDB Tools
DynamoDB Info
© 2024 Dynobase