Buckets are the primary containers in Object Storage. Each bucket stores your files, that we refer to as "objects," and lets you access or share them.

📘

Object Storage may impose limits

For information about Object Storage product limits, including bucket rate limits, see Quotas and limits.

View your buckets

Log in to Cloud Manager and select Object Storage from the left menu. If you currently have buckets on your account, they're listed on this page.

You can also view your bucket using the Linode CLI, Cyberduck, s3cmd, and s4cmd.

Create a bucket

To get started in Object Storage, you need to create a bucket. Here's how to create a bucket using Cloud Manager, though you can also use the Linode CLI, s3cmd, and s4cmd.

1. Log in to Cloud Manager and select Object Storage from the left menu.

2. Click Create Bucket. If you haven't created an access key or a bucket on this account, you'll be prompted to enable Object Storage.

   📘

   Billing for Object Storage starts as soon as it's enabled on your account. See Object Storage Pricing for more detail on the minimum flat-rate and per GB charge. See Cancel Object Storage for instructions on cancelling this service.

3. Enter a Bucket Name for the new bucket. Consider these points when setting a name:

   • It needs to be between 3 and 63 characters in length.

   • It can only contain lower-case characters (a-z), numbers (0-9), periods (.), and dashes (-). It can't end with a dash or period, have consecutive periods, or use dashes adjacent to periods.

   • It needs to start with a lowercase letter or a number.

   • It needs to be completely unique in the Region, not just to your account. (If the name is already in use, an alert message will appear when you save your bucket.)

   • It can't be formatted as an IP address.

   • If you want to use an E2 or E3 Endpoint Type in the bucket, the name can't contain admin.

   • If you want to use this bucket with a custom domain, the name needs to be your fully qualified domain name, such as assets.example.com or any subdomain of *.your-domain.tld.

4. Choose a Region where you want the bucket to live. See the Availability section on the Object Storage OverviewObject Storage page for a list of available regions.

5. Review the Endpoint Type information.

   • Most regions only support one endpoint type. For these regions the endpoint type information is read only. There are, however, a few regions that support more than one endpoint type. You should select the highest option available to take advantage of the greater performance and capacity limits.

   • There's more information, Check out the Endpoint types guide for full details on the available types. Also see the Product limits guide to review the performance, capacity, and rate limits available for each endpoint type.

6. Click Submit to create the bucket.

You're now ready to upload files to the bucket.

Delete a bucket

Follow these steps to delete an Object Storage bucket from Cloud Manager. You can also use the Linode CLI, s3cmd, and s4cmd.

📘

You can only delete an empty bucket using Cloud Manager. To delete a bucket's objects, see Delete a File/Object. Alternatively, you can use an s3cmd command to delete a non-empty bucket, replacing example-bucket with the full Bucket Name:

s3cmd rb -r -f s3://example-bucket/

1. Log in to Cloud Manager and select Object Storage from the left menu.

2. Locate the bucket you want to delete and click Delete:

3. Enter the bucket's full name to confirm that you want to delete it and click Delete Bucket.

📘

Reusing the name of a deleted bucket

After you delete a bucket, the system needs time to release the resources it used. This typically takes less than 60 minutes.

• If you attempt to create a bucket with that same name in the same endpoint, you'll receive a 409 BucketAlreadyExists error if the name is not yet available.
• If you're using a common name, another account may create a bucket with the same name when it becomes available, preventing you from reusing that name.

As a best practice, don't delete a bucket if you need to use its specific name.