Contents x
Create and Manage Buckets
    • Print
    • Dark
      Light
    Contents

    Create and Manage Buckets

      • Print
      • Dark
        Light
      Article summary

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

      Create a Bucket

      Before you begin: You must enable a Backblaze B2 account.

      1. Sign in to the Backblaze web console.
      2. In the left navigation menu under B2 Cloud Storage, click Buckets.
      3. Click Create a Bucket.
      4. Enter a name for your bucket. Bucket names must be at least six characters and globally unique.
        A message is displayed if your bucket name is already in use.
      5. Select a privacy setting: Private or Public.
        Note
        You can change a bucket's privacy settings at any time.
        Files that are in a private bucket require authentication to perform an action, for example, downloading.
        Public buckets do not require authentication so you can easily access files. If this is your first time creating a public bucket, complete the following tasks to ensure that you have the correct permissions to create a public bucket:

        1. Verify your email address.
        2. Have a payment history on file, or use the credit card form to pay a small fee that is credited to your account balance.
      6. If applicable, enable a Backblaze B2 server-side encryption key.
      7. Enable Object Lock to restrict a file from being modified or deleted for a specified period of time.
      8. Click Create a Bucket, and copy the value that is in the Endpoint field; you may need this value later.
      9. Click Lifecycle Settings to control how long to keep the files in your new bucket.

      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.

      Note:
      If bucket names were only unique within an account, the account name would be required to make URLs and API calls unique. This could inadvertently expose your account name depending on how the URL or API is used. Backblaze uses globally unique bucket names to protect users from this risk.

      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

      Delete a Bucket

      Before you begin: You must delete all of the files that are in the bucket.

      1. Sign in to your Backblaze account.
      2. In the left navigation menu under B2 Cloud Storage, click Buckets.
      3. Click Bucket Settings.
      4. Click Delete Bucket, and click I'm Sure. Delete Bucket!

      Change Access Permissions

      1. Sign in to your Backblaze account.
      2. In the left navigation menu under B2 Cloud Storage, click Buckets.
      3. For the bucket that you want to change permissions, click Bucket Settings.
      4. Select Private or Public.
      5. Click Update Bucket.
        Changes can take up to ten minutes.

      Locate an S3 Endpoint URL

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

      1. Sign in to your Backblaze account.
      2. In the left navigation menu under B2 Cloud Storage, click Buckets.
      3. Scroll to the bucket that you want to use in an integration.
      4. Copy the value in the Endpoint field.
      Was this article helpful?
      Related articles
      What's Next