Create and Manage Buckets

You can use the Backblaze enterprise web console to create and manage Backblaze B2 Cloud Storage buckets.

Bucket creation and full bucket management require either:

• The Bucket Creator role scoped to the organization or a specific resource group, or
• The Administrator role.

Many tabs in the bucket details view—such as Users, User Groups, and Application Keys—are visible only to Administrators. Users with object-focused roles (Object Manager, Object Viewer, Object Writer) will typically see only the Objects and related tabs for buckets they have access to.

Create a Bucket

1. Sign in to your Backblaze organization.
2. In the left navigation menu, select Buckets.
3. Click Create Bucket.
4. Enter a unique bucket name.
5. Select a region (for example, US West).
6. Select whether the bucket’s contents are Public (accessible to anyone with the URL) or Private (restricted to users with permission).
7. Select a resource group to grant bucket access to all of the users who are assigned to the group.
8. (Optional) Enable a server-side encryption key.
9. (Optional) Enable Object Lock to restrict an object from being modified or deleted for a specified period of time.
   Configure lock features in Bucket Settings after you create the bucket. You cannot disable Object Lock after you create the bucket.
10. Click Create.

Bucket Names

Bucket names are globally unique across all Backblaze B2 accounts. When you create a bucket, you must enter a name that is not already in use.

B2 Native API Naming Rules

The following naming rules apply to all Backblaze B2 buckets:

• Bucket names must be at least 6 characters and no more than 63 characters long.
• Bucket names can consist of upper-case letters, lower-case letters, numbers, and hyphens (-).
• Bucket names are not case sensitive, even though they can include upper-case letters.
• Multi-byte characters are not supported. The underscore character (_) is not valid because it would limit DNS compatibility and the ability to create vanity URLs.
• Bucket names that start with b2- are reserved for Backblaze use.
• You cannot rename a bucket after it is created.

The following are valid bucket names:

• myBucket
• backblaze-images
• bucket-74358734

 For file naming rules, click here.

S3-Compatible API Naming Rules

If you access your buckets through the S3-Compatible API or connect third-party integrations—such as backup tools, media applications, or cloud sync services—your bucket names must also comply with AWS S3 general purpose bucket naming conventions.

Character and length requirements:

• 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).

Reserved prefixes:

Bucket names must not start with the following prefixes:

• xn--
• sthree-
• amzn-s3-demo-

Reserved suffixes:

Bucket names must not end with the following suffixes:

• -s3alias (reserved for access point alias names)
• --ol-s3 (reserved for Object Lambda Access Point alias names)
• .mrap (reserved for Multi-Region Access Point names)
• --x-s3 (reserved for directory buckets)
• --table-s3 (reserved for S3 Tables buckets)

Transfer Acceleration:

Buckets used with Amazon S3 Transfer Acceleration cannot have periods (.) in their names.

Recommendation

For maximum compatibility with partner integrations and the S3-Compatible API, Backblaze recommends following these combined guidelines for all new buckets:

• Use only lowercase letters, numbers, and hyphens (-)
• Use at least 6 characters (required by B2) and no more than 63 characters
• Begin and end with a lowercase letter or number
• Bucket names cannot contain periods (.)
• Avoid the reserved prefixes and suffixes listed above

Bucket Detail

After you create a bucket, you can click it from the Buckets page to see details in each tab.

• Overview: In this tab, you can configure bucket settings such as Object Lock, CORS rules, and Lifecycle Rules. You can also change settings such as object visibility.
• Objects: In this tab, you can view information about the objects in the bucket. You can also upload or delete objects and create folders.
• Users: In this tab, you can view a list of users in the organization, their privileges, and roles. You can also assign access to users.
• User Groups: In this tab, you can view a list of user groups in the organization. You can also assign access to user groups.
• App Keys: In this tab, you can view a list of application keys and their corresponding IDs and prefixes. You can also create application keys.

Delete a Bucket

Before you begin: Delete all objects that are in the bucket.

1. In the left navigation menu, select Buckets.
2. Click the bucket to delete.
3. Click Delete Bucket.
4. Click Yes, I’m sure.

Update Bucket Settings

You can update object visibility, encryption, and lock features after you create the bucket.

1. In the left navigation menu, select Buckets.
2. Click the bucket name, click Settings, and select the General tab.
3. Click Private or Public.
4. Select a new resource group to move the bucket.
   You can also move buckets from the Resource Groups page.
5. Enable or disable Encryption.
6. To configure Object Lock, enable Lock Features.
   1. Enable Object Lock.
   2. Select a lock mode:
      • Governance
      • Compliance
        After you save this setting, you cannot change the lock mode and duration.
   3. Enter the number of days (1–3,000) to prevent files in the bucket from being deleted or modified.

      You must enter a default bucket retention period before your files are immutable.

7. Click Save.

Locate an S3 Endpoint URL

You may need the S3 endpoint URL from your bucket for use in an integration.

1. In the left navigation menu, select Buckets.
2. Click the bucket name.
3. Select the Overview tab, and copy the value in the Endpoint field.