Error: dynamodb table not exists

“Table not exists” usually means the requested table is absent from the account, Region, or endpoint used by the client. Verify those settings before creating a new table; a table with the same name elsewhere is a different resource.

aws sts get-caller-identity --profile dev
aws dynamodb describe-table --table-name Orders --region us-east-1 --profile dev

Use the application’s profile or role for these checks. For DynamoDB Local, add its endpoint to the DynamoDB command and keep the access key and Region consistent unless the server uses -sharedDb. STS checks an AWS identity, not a local database namespace.

A new table must finish creation before data operations begin. DescribeTable can briefly return ResourceNotFoundException immediately after creation because table metadata is eventually consistent. Use a bounded table-exists waiter. If the response is AccessDeniedException, fix the permission problem rather than concluding the table is absent.

See table creation and AWS documentation.