FAQ

Two regions in India: Indore (idr01, endpoint https://idr01.zata.ai) and Mumbai (bom01, endpoint https://bom01.zata.ai). Your plan covers both. See Endpoints and regions.

The endpoint of your bucket’s region, the region name us-east-1, and an access key and secret key from Access Keys. Use path-style URLs if the tool asks. See Settings for any S3 tool.

Use us-east-1. Zata doesn’t check the region name, so if a tool makes you pick from a list, any value works. What matters is the endpoint URL.

Each access key belongs to one region. An Indore key gets InvalidAccessKeyId or AccessDenied on the Mumbai endpoint, and the other way round. Create a key in each region you use. See Access keys.

Open Buckets in the Zata console and look at the Region column. S3 tools don’t show a bucket’s region. See Endpoints and regions.

Most tools that support Amazon S3 or “S3-compatible storage”: command-line tools, SDKs, desktop apps, drive-mount tools and backup software. See Settings for any S3 tool for tested guides. A few tools need extra settings: for example, rclone needs sign_accept_encoding = false. Velero doesn’t work with Zata today.

Buckets, objects, multipart uploads, versioning, Object Lock, lifecycle rules, bucket policies, ACLs, presigned URLs and S3 Select. There is one storage class only, and server-side encryption requests are not supported. See What works with Zata.

A single upload can be up to 5 GB. Larger files are uploaded in parts (multipart), up to 10,000 parts, and most tools do this for you. If large uploads fail with the AWS CLI or an AWS SDK, see Large uploads fail.

Data travels to and from Zata over HTTPS. Zata doesn’t accept server-side encryption requests (SSE-S3, SSE-C or SSE-KMS): they fail with InvalidRequest, so leave encryption options in your tool turned off. If you want your files encrypted with your own key, encrypt them before you upload, for example with restic or the encryption option of your backup software.

No. Zata has no STS, IAM roles or AssumeRole. To limit what a key can do, create a sub-user with access to only the buckets it needs. To give someone temporary access to one file, share a link that expires.

No. The account owner creates buckets and assigns them to sub-users. See Assign a bucket.

No. A sub-user’s bucket list is always empty, even for buckets they can use. They open a bucket by its name, for example aws s3 ls s3://my-bucket. See About sub-users.

No. You can turn on Object Lock only when you create a bucket. See Object Lock.

No. Use your tool’s debug output instead, for example aws ... --debug or rclone ... -vv. If you need more, raise a ticket: the support team can check the logs on Zata’s side.

15 days, with both regions included. You don’t need a credit card. See Create an account.

Zata is prepaid. You buy a storage plan for 30 days at a time, and one plan covers both regions. Prices don’t include GST, and 18% GST is added at checkout. See Billing.

Uploads are free. Downloads are free up to your plan’s storage size in each 30-day period. If you go over, your account is suspended until you upgrade. See Ingress and egress.

Your services keep working for 5 days after the end date. After that the account is suspended, but your data is kept until 90 days after the end date. When you renew, you also pay a fee for the days since the end date. After 90 days your data can be deleted. See When a plan expires.

Only after your current plan expires, and only to a plan that your stored data fits in. You can move to a larger plan at any time. See Billing.

Email solutions@zata.ai or call 1800-309-1433. For technical problems, raise a ticket.

See the Zata privacy policy (PDF).