Create a bucket
Pick a name and a region, and switch on versioning or Object Lock if you need them.
A bucket holds your files. Each bucket lives in one region, Indore or Mumbai, and you reach it with an access key from that same region.
Only the account owner can create buckets. Sub-users work in the buckets the owner assigns to them.
Create a bucket
In the Zata console, open Buckets and select Create Bucket.
Type a name in Bucket Name and choose a Region, then select Next. The console checks that the name is still free.
The console adds a short prefix in front of your name: the first four letters of your username. The Review step shows the full name.
Your plan, or the free trial, covers both regions, so you can pick Indore or Mumbai.
Turn on Enable Versioning if you want to keep old versions of files. Turn on Enable Object Lock if files must not be deleted or changed for a set time. Object Lock needs versioning, so turn that on first. Both settings are explained below.
Enter a Key and a Value, and select Add Tag for more. You can add up to 10 tags. See Tags for the rules. To skip, leave the row empty. Select Next.
Check the summary and select Create Bucket.
The new bucket appears in the Bucket List. Select its name to upload files. The icons under ACTIONS open Tags, Bucket settings and Delete a bucket.
Bucket name rules
| Rule | Example |
|---|---|
| 3 to 63 characters | logs |
Only lowercase letters, numbers, dots (.) and hyphens (-) | backup-2026 |
| Starts and ends with a letter or a number | not -backup |
| No two dots in a row | not my..bucket |
| Not written like an IP address | not 192.168.1.10 |
| Not already used by anyone on Zata | the console tells you if the name is taken |
Keep the whole name, prefix included, within 63 characters, and use hyphens instead of dots. Names with dots fail the HTTPS certificate check in virtual-host style URLs.
You cannot rename a bucket or move it to the other region later. To move data, create a new bucket and copy the files.
Versioning and Object Lock
| Option | What it does | Can you change it later? |
|---|---|---|
| Enable Versioning | Keeps every version of a file when you overwrite or delete it, so you can restore it. Old versions use storage. | You can turn it off in Bucket settings. New versions then stop; existing versions stay. |
| Enable Object Lock | Locked file versions cannot be deleted or overwritten until their lock ends. See Object Lock. | No. You can only turn it on now, and it can never be turned off. Versioning then stays on for good. |
| Default Retention (optional) | Locks every new upload for the number of days you set, in Governance or Compliance mode. Without it, new files are not locked until you lock them. | Yes, in Bucket settings. |
The Review step also lists Encryption as SSE-S3 (Default). There is no encryption setting to choose. In S3 tools, leave server-side encryption options turned off: Zata rejects SSE requests.
Next steps
- Upload and manage files
- Create an access key to connect S3 tools
- Endpoints and regions