Although your storage buckets are completely private and partitioned from all other users on the Wasabi service, the Amazon S3 standard for storage bucket naming requires unique storage bucket names across an S3-style object storage service such as Wasabi. This means that if someone else on the service has already named their storage bucket “test,” the name will not be available to other users. You may want to name your storage buckets with a unique identifier.
For naming syntax, Wasabi follows the S3 standard naming rules described in the S3 documentation.
Buckets with a naming convention of all numbers (for example, 12345678) will fail to list contents with some applications, such as CyberDuck and Wasabi Explorer. We recommend that you do not use an all-numbers naming schema for your buckets.
Bucket Names
A bucket name is visible in the URL that points to the objects you will put in the bucket. Use a unique DNS-compliant name for a bucket. You should develop a naming strategy following these guidelines:
The name must be unique across all existing bucket names in Wasabi. A bucket name must:
Be a valid DNS-compliant name
Begin with a lowercase letter or number, and
Consist of 3 to 63 lowercase letters, numbers, periods, and/or dashes.
The name cannot contain underscores, end with a dash, have consecutive periods, or use dashes adjacent to periods. And, the name cannot be formatted as an IP address (123.45.678.90).
Choose a bucket name that reflects the objects you will store in the bucket.
File Names
Avoid the use of the following special characters in a file name:
% (percent)
< (less than symbol)
> (greater than symbol)
\ (backslash) # (pound sign)
? (question mark)
Certain file names may have non-ASCII characters that are 4 byte UTF8 characters (such as emojis). Wasabi does not support these characters and will return a 400 error message to an application that tries to write a file with 4 byte UTF characters in the file name. We recommend renaming the affected files, if possible.