---
title: "Create a bucket"
description: "Create a TIR Object Storage bucket with a name and an alias, and choose encryption, versioning, and object lock while you create it."
content_type: "how-to"
product: "tir-object-storage"
platform: "TIR"
url: "/tir/tir-object-storage/how-to/create-a-bucket/"
topic: ["create-and-connect"]
---

# Create a bucket

Create a bucket to hold data that many instances read, or that you reach with an S3 tool. The bucket
grows by itself with the data in it.

## Before you begin

- A TIR project in Delhi or Chennai. A bucket belongs to one project and one region.
- Permission to create datasets in the project. A Member gets it through a policy that allows creating datasets.
- A decision on object lock. You can turn it on only while you create the bucket; see
  [Set a default object lock on a bucket](/tir/tir-object-storage/how-to/set-a-default-object-lock/).

## Fill in the form

1. In TIR, open your project. In the side menu, under **Storage**, select **Object Storage (EOS
   Dataset)**, then select **Create Bucket**. The **Create Object Storage** form opens. This form
   always creates a new bucket.
2. Check **Bucket Name**. It starts with a suggestion, `tir-bkt-` followed by the date and time, and you can type your own. A name is 3 to 63 characters long and uses only lowercase letters, numbers, and hyphens. It starts and ends with a letter or number, and it does not look like an IP address such as `203.0.113.1`. The alias copies the name and stops at 50 characters, so keep the name to 50
   characters or fewer. Bucket names share one namespace across all of EOS, so the form refuses a name
   that another customer holds.
3. While you type, the form checks the name. It shows **Checking availability...**, then **This
   bucket name is available**. If the name is taken, the form says why, and **Create** becomes available once you
   choose a name that is free.
4. **Alias (Dataset Name)** copies the bucket name as you type and is read-only on this form. It
   must differ from the names of the project's other datasets, Shared File Systems, and Parallel
   File Systems. Workloads use the alias, so choose a name you want to keep: a bucket and its alias keep their names once you create the bucket.
5. (Optional) In Delhi, turn **Enable Encryption** on to encrypt the data in the bucket. The setting
   is permanent once you create the bucket. See
   [Create an encrypted bucket](/tir/tir-object-storage/how-to/create-an-encrypted-bucket/).
6. (Optional) Turn **Enable Object Versioning** on to keep previous versions of an object instead of
   overwriting it. You can also turn it on or suspend it later; see
   [Use object versioning](/tir/tir-object-storage/how-to/use-object-versioning/).
7. (Optional) Turn **Enable Object Lock** on to protect objects against deletion and overwriting for a fixed retention period. It turns versioning on permanently, and the versioning switch then
   stays on. Object lock supports the governance mode only.
8. Select **Create**.

If TIR refuses to create the bucket, it gives the reason EOS reports, for example the name problem. See
[Troubleshooting TIR Object Storage](/tir/tir-object-storage/troubleshooting/tir-object-storage/).

## Check the bucket

TIR creates the bucket and gives you its keys and the **Setup Minio CLI** and **Setup s3cmd** commands
under **Next Steps**. The new bucket is **Pending** in the list, and **Ready** when it is set up. The list
marks a bucket that has object lock.

Each new bucket gets its own access key pair, which works on that bucket only.

Next, [upload data to the bucket](/tir/tir-object-storage/how-to/upload-data-to-a-bucket/) or
[find its access keys and endpoint](/tir/tir-object-storage/how-to/find-a-buckets-access-keys-and-endpoint/).
For rates, see [E2E's pricing page](https://www.e2enetworks.com/pricing), and for an estimate across
services, use the [E2E pricing calculator](https://calculator.e2enetworks.com/estimate-pricing).