Amazon S3 table bucket, table, and namespace naming rules - Amazon Simple Storage Service

Amazon S3 table bucket, table, and namespace naming rules

When you create a table bucket, you choose a bucket name and AWS Region, the name must be unique for your account in the chosen Region. After you create a table bucket, you cannot change the bucket name or Region. Table bucket names must follow specific naming rules. For more information about naming rules for table buckets and the tables and namespaces within them, see the following topic.

Table bucket naming rules

When you create Amazon S3 table buckets, you specify a table bucket name. Like other bucket types, table buckets can't be renamed. Unlike other bucket types, table buckets aren't in a global namespace, so each bucket name in your account only needs to be unique in your current AWS Region.

The following naming rules apply for table buckets.

  • Bucket names must be between 3 and 63 characters long.

  • Bucket names can only consist of lowercase letters, numbers, and hyphens (-).

  • Bucket names must begin and end with a letter or number.

  • Bucket names must not contain any underscores (_) or periods(.).

  • Bucket names must not start with any of the following prefixes

    • xn--

    • sthree-

    • amzn-s3-demo-

  • Bucket names must not end with any of the following suffixes:

    • -s3alias

    • --ol-s3

    • --x-s3

Naming rules for tables and namespaces

The following naming rules apply to tables and namespaces within table buckets.

  • Names must be between 3 (min) and 63 (max) characters long.

  • Names can consist only of lowercase letters, numbers, and underscores (_).

  • Names must begin and end with a letter or number.

  • Names must not contain hyphens (-) or periods (.).

  • A table name must be unique within a namespace.

  • A namespace must be unique within a table bucket.

  • You can't use aws_s3_metadata as a namespace. aws_s3_metadata is a reserved for metadata tables. For more information, see Accelerating data discovery with S3 Metadata