AWS DynamoDB resource not found exception

Question

I have a problem with connection to DynamoDB. I get this exception:

com.amazonaws.services.dynamodb.model.ResourceNotFoundException: Requested resource not found (Service: AmazonDynamoDB; Status Code: 400; Error Code: ResourceNotFoundException; Request ID: ..

But I have a table and region is correct.

Any chance that you have this problem with Terraform S3 backend? I just ran into the same problem after changing the backen configuriation of Terraform and found out that Terraform is not using the values from the terraform.tf but from the state that is stored in .terraform/terraform.tfstate. — Nils Rommelfanger, Aug 29 '18 at 05:38
I just ran into this problem this week too. Rebooting my EC2 instances appears to have resolved it at the moment. Weird... — Dave Splat, Aug 30 '18 at 16:13

score 113 · Answer 1 · answered Oct 23 '16 at 09:53

113

From the docs it's either you don't have a Table with that name or it is in CREATING status.

I would double check to verify that the table does in fact exist, in the correct region, and you're using an access key that can reach it

answered Oct 23 '16 at 09:53

Chen Harel

9,684
5
44
58

14

I was indeed looking into different region. Fixed it by looking into right region. Thanks! – user2884707bond Sep 11 '18 at 13:26
3

For me it was my access key, it was for a different account. Me so stupid. You rock! – Paul Siersma Nov 07 '18 at 20:01
2

I somehow had both the region wrong and had deleted the table last night when trying to re-create it after updating the schema. So double fail on my part... – fIwJlxSzApHEZIl Mar 22 '19 at 06:36
If you're still having an issue like I was check your JavaScript object instantiation. I had `RequestItems: { tableName: item_row }`. But I needed to use the table name's directly: `RequestItems: { "myTable": item_row }`. The issue is that my variable for the tableName was not being accessed. The table name was always `tableName` in the request which obviously didn't exist. – fIwJlxSzApHEZIl Apr 09 '19 at 03:16
If you are trying from `sls offline` make sure you have the env variables set correctly. – A.R Naseef Apr 13 '20 at 14:58
I had a problem in the TableName! – Juan José Ramírez Nov 03 '21 at 23:20
Again an incorrect region :( – harishanth raveendren Dec 17 '21 at 14:38
1

@fIwJlxSzApHEZIl, To use a variable as an object key, put it in brackets, i.e. { [tableName]: item_row } – joematune Aug 17 '22 at 15:36

score 19 · Answer 2 · answered Oct 28 '20 at 16:48

19

My problem was stupid but maybe someone has the same... I changed recently the default credentials of aws (~/.aws/credentials), I was testing in another account and forgot to rollback the values to the regular account.

answered Oct 28 '20 at 16:48

pmiranda

7,602
14
72
155

I created the table manually and it worked. It also happens because of creating and removing the table multiple times. – Trishant Pahwa Jan 21 '22 at 10:55
1

In my case I deleted the `~/.aws/credentials` and it started working as before. Thanks for the hint. – Revanth Kumar May 20 '22 at 19:59
Same here, I had to change my aws credentials back to different profile – Nick Scherer May 14 '23 at 08:45

Oleg Ushakov · Answer 3 · 2021-12-01T22:29:35.820

I spent 1 day researching the problem in my project and now I should repay a debt to humanity and reduce the entropy of the universe a little. Usually, this message says that your client can't reach a table in your DB. You should check the next things:

1. Your database is running
2. Your accessKey and secretKey are valid for the database
3. Your DB endpoint is valid and contains correct protocol ("http://" or "https://"), and correct hostname, and correct port
4. Your table was created in the database.
5. Your table was created in the database in the same region that you set as a parameter in credentials. Optional, because some
database environments (e.g. Testcontainers Dynalite) don't have an incorrect value for the region. And any nonempty region value will be correct

In my case problem was that I couldn't save and load data from a table in tests with DynamoDB substituted by Testcontainers and Dynalite. I found out that in our project tables creates by Spring component marked with @Component annotation. And in tests, we are using a global setting for lazy loading components to test, so our component didn't load by default because no one call it in the test explicitly. ¯_(ツ)_/¯

score 7 · Answer 4 · answered Sep 22 '20 at 15:35

7

If DynamoDB table is in a different region, make sure to set it before initialising the DynamoDB by

AWS.config.update({region: "your-dynamoDB-region" });

This works for me:)

answered Sep 22 '20 at 15:35

RISHU GUPTA

493
6
8

That solved it for me, or check if you have created the table in the region you want. – Moha the almighty camel Dec 05 '21 at 22:06

score 3 · Answer 5 · answered Apr 18 '21 at 00:59

Always ensure that you do one of the following:

The right default region is set up in the AWS CLI configuration files on all the servers, development machines that you are working on.
The best choice is to always specify these constants explicitly in a separate class/config in your project. Always import this in code and use it in the boto3 calls. This will provide flexibility if you were to add or change based on the enterprise requirements.

score 1 · Answer 6 · answered Apr 18 '21 at 00:44

1

If your resources are like mine and all over the place, you can define the region_name when you're creating the resource.

I do this for all my instantiations as it forces me to think about what I'm putting/calling where.

boto3.resource("dynamodb", region_name='us-east-2')

answered Apr 18 '21 at 00:44

John Christian

85
4

I don't think that this answers the person's question. Would you consider writing a comment instead of a solution for your suggestion? – Yves Gurcan Apr 20 '21 at 14:30

score 0 · Answer 7 · edited Oct 06 '21 at 14:50

0

I was getting this issue in my .NetCore Application. Following fixed the issue for me in Startup class --> ConfigureServices method

        services.AddDefaultAWSOptions(
            new AWSOptions
            {
                Region = RegionEndpoint.GetBySystemName("eu-west-2")
            });

edited Oct 06 '21 at 14:50

Dharman

30,962
25
85
135

answered Oct 06 '21 at 14:45

Maverick HT

427
5
9

AWS DynamoDB resource not found exception

7 Answers7

Linked