Let's get some help!

Is there a limitation in the bucket name?

Bucket names must be unique and comply with the following:

  • Must not contain uppercase characters or underscores.
  • Must not be formatted as an IP address.
  • Can contain lowercase letters, numbers, and hyphens.
  • Can contain a set of the 63 alphabetic characters, a to z, and the 10 Arabic numerals, 0 to 9.

For buckets with a name containing a dot (.), users must use the canonical path. The subdomain form, for instance, https://toto.tata.s3.nl-ams.scw.cloud will not work as the SSL certificate *.s3.nl-ams.scw.cloud is not recursive.

In addition, when using buckets with Secure Sockets Layer (SSL), the SSL wildcard certificate only matches buckets that do not contain periods. Therefore, it is not recommended to use bucket names with multiple dots, as it will have an impact on accessing your bucket via HTTPS. To avoid this, it is recommended to use dashes in your bucket names.

Bucket names are unique in relation to our whole platform. This means if a bucket exists already in one region, the name cannot be reused in another.
The “Bucket already exists” error message is triggered when the name you intended to use for your bucket is already reserved by another user (or yourself).
When deleting a bucket, its name becomes available again. Anybody can reuse it on a first-come, first-served principle.

Important: Bucket ownership is not transferable. A bucket is owned by the account which created it.


Was this helpful?

Great, thank you!
Tell us what you are looking for?
Contact us