Question: Are DynamoDB table names unique?

Answer

Yes. A DynamoDB table name must be unique within the AWS account and Region where you create it. The same name can be used in a different account or Region, where it identifies a different resource.

For example, Orders in us-east-1 and Orders in eu-west-1 can coexist. They do not share data just because their names match. Replication requires a global-table configuration or an application-managed copy process.

Names are case-sensitive, so Orders and orders are different table names in the managed service. To identify a table across account and Region boundaries, use its ARN, which includes both. Cross-account API access still requires the appropriate identity and resource policies; knowing the ARN does not grant permission.

Choose environment names consistently and check the SDK client's Region when a table appears to be missing. A restore or copy into the same account and Region needs a name that is not already taken. Renaming an existing table requires creating another resource and migrating to it.

See naming conventions and copying a table for those workflows.

Source: AWS table creation rules.