> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.zata.prathamchopde.site/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.zata.prathamchopde.site/_mcp/server.

# Your first bucket

This quickstart takes you from a new account to a file stored in Zata. You create a bucket in the Zata console, create an access key for the same region, and upload a file with the AWS CLI.

## 1. Create a bucket

#### Open Buckets

In the Zata console, open **Buckets** and select **Create Bucket**.

#### Name the bucket and choose a region

Enter a **Bucket Name** and choose a **Region**: **Indore** or **Mumbai**. Then select **Next**.

The console puts the first four letters of your username in front of the name. For example, `shiv` + `image` makes the bucket `shivimage`. Use this full name in your tools.

![Step 1 of Create Bucket: the username prefix shiv, the name image and the Region drop-down set to Indore](/_fern-img/cb9796d4eb65311cd3f58a5ff423af3e30358509cb9b5bc39a3b7309b6b0f515.webp)

#### Versioning (optional)

Turn on **Enable Versioning** if you want Zata to keep old versions of a file when you change or delete it. **Enable Object Lock** works only when versioning is on. Leave both off for a simple first bucket, then select **Next**.

![Step 2 of Create Bucket: the Enable Versioning and Enable Object Lock switches, both off](/_fern-img/bfaa67fb9a2b1c33d4070a1c67956ca961eebc7ea2db86b94cc1c8c7b002dfe1.webp)

#### Tagging (optional)

Tags are key and value labels that help you sort buckets. Type a **Key** and a **Value**, or select **Add Tag** for more. To skip, leave the row empty and select **Next**.

![Step 3 of Create Bucket: an empty Key and Value row and the Add Tag button](/_fern-img/eaf9613b25c67d7d2a39eb8b8bc18b3929a1ea53272e0c8d6f6a266f4896028f.webp)

#### Review and create

Check the bucket name, region and settings, then select **Create Bucket**. The new bucket appears in your bucket list.

![Step 4 of Create Bucket: the Review list with the bucket name shivimage, region Indore and versioning disabled, and the Create Bucket button](/_fern-img/3ab23c9d9a862aad0880fea8182ab08ea0f35fa455bbcd62cbcc3aa606d7c906.webp)

> **Note**
>
> You can turn on Object Lock only while you create a bucket, in the **Versioning** step. See [Object Lock](/buckets/object-lock/overview). For naming rules and all options, see [Create a bucket](/buckets/create-a-bucket).

## 2. Create an access key

An access key works in one region only, so create it in the region of your bucket.

#### Open Access Keys

Open **Access Keys** and select **Generate Key**.

#### Choose the user and region

Select **Root User**. Under **Select Region**, choose the region of your bucket, then select **Continue**.

![The Create Access Key dialog with Root User selected and the region set to Indore](/_fern-img/cce8a66f45b31fafd8114d1523bfcc0f87bf534ebbd17f55f28e24d20a06e25e.webp)

#### Download the key file

Select **Generate Key**. A `.txt` file downloads with the service URL, your access key and your secret key.

![The Important Note dialog asking you to download the key file, with the Generate Key button](/_fern-img/32a315c9b82aa6e86b9406a150120d685e2b806c1cba2e5aba55913a8b12cb06.webp)

> **Warning**
>
> Keep the key file safe. You can't see the secret key again. If you lose it, delete the key and create a new one. See [Access keys](/access/access-keys).

## 3. Upload a file

These steps use the AWS CLI. If you don't have it yet, see [AWS CLI](/connect/command-line/aws-cli) for how to install it.

#### Create a Zata profile

```bash
aws configure --profile zata
```

| When it asks          | Type            |
| --------------------- | --------------- |
| AWS Access Key ID     | your access key |
| AWS Secret Access Key | your secret key |
| Default region name   | `us-east-1`     |
| Default output format | `json`          |

#### Point the profile at Zata

For a bucket in Mumbai, use `https://bom01.zata.ai` instead.

```bash
aws configure set endpoint_url https://idr01.zata.ai --profile zata
aws configure set s3.addressing_style path --profile zata
aws configure set request_checksum_calculation when_required --profile zata
aws configure set response_checksum_validation when_required --profile zata
```

The last two lines stop large uploads from failing on new AWS CLI versions.

#### Upload and list

Replace `my-bucket` with your full bucket name.

```bash
aws s3 cp myfile.txt s3://my-bucket/ --profile zata
aws s3 ls s3://my-bucket --profile zata
```

The file also shows in the console when you open the bucket under **Buckets**.

If a command fails, see [Wrong endpoint or region](/help/troubleshooting/endpoint-and-region) and [Access denied](/help/troubleshooting/access-denied).

## Use another tool

Every S3 tool needs the same four things: the endpoint of your bucket's region, the region name `us-east-1`, and your access key and secret key. See [Settings for any S3 tool](/connect/overview) for step-by-step guides for rclone, Cyberduck, S3 Browser, backup software and more.

## Next steps

* [Endpoints and regions](/get-started/endpoints-and-regions): all connection settings in one place.
* [Share a file](/buckets/share-a-file): send someone a download link.
* [Sub-users](/sub-users/overview): give a team member access to only some buckets.