ResourceNotFoundException (DynamoDB) ☁️ AWS

DynamoDB ResourceNotFoundException: Requested resource not found (table)

The table (or index) doesn’t exist in the region/account the client is using.

Seen on: AWS

Meaning

Tables are regional. A client defaulting to us-east-1, a table name with an environment suffix (orders-dev), or a table still being created all produce this.

Common causes

  • Wrong region
  • Table name differs per environment
  • Table not yet ACTIVE / deleted
  • Wrong account/profile

⚡ Quick fix

  1. List tables in the region: aws dynamodb list-tables
  2. Set region and table name from config
  3. Wait for TableStatus ACTIVE

Detailed fix by platform

AWS CLI

  1. bash
    aws dynamodb list-tables --region eu-west-1
aws dynamodb wait table-exists --table-name orders-dev

How to diagnose

  1. Region — Client region
  2. Name — Exact table name
  3. Status — describe-table TableStatus

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.