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 aliasing is not supported
- DynamoDB TTL Not Working
- One or more parameter values were invalid: some AttributeDefinitions are not used
- aws.dynamodb.converter.unmarshall not working
- sls dynamodb install not working
- DynamoDB Key element does not match the schema
- dynamodb ttl not deleting / erasing items
- DynamoDB ValidationException: Query condition missed key schema element
- DynamoDB Not Supported Requires @DynamoDBTyped Or @DynamoDBTypeConverted
- ConfigError: Missing region in config
- aws.dynamodb.documentclient is not a constructor
- Unable to start DynamoDB Local process
- com amazonaws services dynamodbv2 model resourcenotfoundexception
- dynamodb unable to execute http request
- dynamodb could not connect to the endpoint url
Spend less time in the AWS console, use Dynobase.
First 7 days are on us. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase