On the Wasabi Management Console, click CREATE BUCKET. If you are a new user, you may see a screen such as the one below. You can click the green CREATE BUCKET button in the bottom-middle of your screen. Any user can click the red CREATE BUCKET button available at the upper right of any screen.
In the “Bucket Name” area, enter a unique DNS-compliant name for your new bucket. A bucket name can consist of 3 to 63 lowercase letters, numbers, periods, and dashes. The name must begin with a lowercase letter or number. 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).
widget-project is used in the example below; but enter your own unique name.
Before naming a bucket, you should develop a naming strategy following these guidelines:
The name must be unique across all existing bucket names in Wasabi. The bucket name must:
Be a valid DNS name, which can include lowercase letters, numbers, and dashes,
Begin with a lowercase letter, and
Include between 3 and 63 characters.
Choose a bucket name that reflects the objects you will store in the bucket. The bucket name is visible in the URL that points to the objects you will put in the bucket.
Select the region (geographic location) where you want the bucket to reside.
At this point, you have three options:
Create the bucket without enabling bucket versioning or logging options. Simply click CREATE BUCKET to create the bucket and end this procedure.
If you have an existing bucket, a “Quick Setup” area is included on the Create Bucket panel. Optionally, you can copy the settings from an existing bucket. To do so, click in the “Quick Setup” area and select a bucket name from the drop-down list. For example:
A message indicates that any compliance settings (as described in Enabling Bucket Compliance) will not be copied.
Click CREATE BUCKET to create the new bucket and end this procedure.
Optionally, enable bucket versioning. Every version of every object in the bucket will be stored. You can then retrieve and restore any version of an object in the bucket. This provides protection against inadvertent removal of an object (such as by overwriting or expiration).
Note: Use versioning cautiously because when versioning is enabled, different versions of all the objects in the bucket are saved. This means the costs could be very high, eventually, as versions are stored.
Optionally, enable bucket logging. A text log will be maintained of all access to the bucket. This provides details about the types of access requests made, request resources, and the date/time of processed requests.
Note: Use logging cautiously because when logging is enabled, all log files are saved. This means the costs could be high, eventually, as log files are stored.
If you enable logging, you must enter:
A logging prefix to include in the log file name. Each log file will start with the characters you enter.
The name of a bucket in which to store log files. Click the down arrow to select from a list of target buckets.
In the following example, log file names will begin with “wdgt99” and the files will be stored in the “widget-logs” bucket.
The bucket properties are displayed for your review. You can click to change the bucket name (returning to ) or properties (returning to ). But, for this exercise, click CREATE BUCKET to accept the information and create the bucket.
A message is displayed at the bottom of your screen:
The new bucket is displayed on the Object Storage panel.
Each bucket is displayed with:
Bucket name that, when clicked, provides access to object information (see Storing Objects in a Bucket)
Owner name, which is the name of the person who created the bucket
Region in which the bucket was created
Date/time when the bucket was created
Public access status
Options accessed with the 3-dot icon in the Actions column to:
Change settings for versioning, logging, bucket privacy, bucket policy, compliance, and an access control list (ACL)
Rename the bucket
Delete the bucket