Bucket naming conventions

Myota object storage is S3-compatible, so bucket names follow the same conventions as the S3 API. When you create a bucket, consider the length, valid characters, formatting, and uniqueness of the name.

Naming rules

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

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

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

  • Bucket names must not contain two adjacent periods.

  • Bucket names must not be formatted as an IP address (for example, 192.168.5.4).

  • Bucket names must be unique within your Myota object storage namespace.

Example bucket names

The following names show the characters allowed in a bucket name: lowercase letters, numbers, and hyphens (-).

  • my-bucket

  • project-logs-2026

  • data-a1b2c3d4-5678-90ab-cdef-111122223333

The following names are valid but not recommended, because they contain periods (.), which prevent virtual-hosted-style access over HTTPS:

  • example.com

  • www.example.com

  • my.example.bucket

The following names are not valid:

  • my_bucket (contains underscores)

  • MyBucket (contains uppercase letters)

  • my-bucket- (ends with a hyphen)

  • example..com (contains two periods in a row)

  • 192.168.5.4 (matches the format of an IP address)

Best practices

  • Choose a naming scheme that is unlikely to cause conflicts. If your application creates buckets automatically, make sure its logic picks a different name when one is already taken.

  • Append a unique identifier to bucket names so they are not predictable. Do not assume a name is available until you have created the bucket; appending a globally unique identifier (GUID) is one way to do this.

  • Avoid periods (.) in bucket names. If a name contains periods, you cannot use virtual-hosted-style addressing over HTTPS unless you handle your own certificate validation, because the TLS certificate used for virtual-hosted-style access will not match a bucket name that contains periods.

  • For the widest compatibility with S3 client tools, avoid bucket names that begin with xn-- or end with -s3alias, --ol-s3, --x-s3, --table-s3, or .mrap. Some AWS-oriented tools treat these as special.