Error: DynamoDB cannot do operations on a non-existent table

“Cannot do operations on a non-existent table” means the target table is not available in the environment reached by the client. Confirm the table name, account, Region, and endpoint before creating or deleting resources. A matching name in another environment is not the same table.

aws dynamodb describe-table --table-name Orders --region us-east-1
aws dynamodb wait table-exists --table-name Orders --region us-east-1

Use the same profile or role as the application. If creation is still in progress, wait for readiness before issuing data requests. The waiter does not create a missing table; first check deployment events and correct a failed or omitted creation step. A deleted table requires an intentional recovery or recreation workflow.

For DynamoDB Local, add the local endpoint and match the access key and Region used when creating the table, unless it was started with -sharedDb. Tests using Moto also need to create the table inside the active mock scope. Cloud table names are case-sensitive; Local differs, so do not depend on its case-insensitive behavior in production.

If DescribeTable returns AccessDeniedException, investigate authorization separately. Do not assume an inaccessible table is absent.

See table creation and AWS documentation.