> 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. # FAQ Short answers to common questions, with links to the full guides. Can't find your answer? See [Get support](/help/support). ## Regions and connecting #### Which regions does Zata have? 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](/get-started/endpoints-and-regions). #### What do I enter in my S3 tool? 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](/connect/overview). #### Which region name should I use? 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. #### My access key works in one region but not the other. Why? 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](/access/access-keys). #### How do I find which region a bucket is in? 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](/get-started/endpoints-and-regions). #### Which tools work with Zata? 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](/connect/overview) for tested guides. A few tools need extra settings: for example, rclone needs `sign_accept_encoding = false`. Velero doesn't work with Zata today. #### Which S3 features are supported? 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](/connect/s3-compatibility). #### How large can a file be? 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](/help/troubleshooting/large-uploads). ## Security and access #### Is my data encrypted? 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](/connect/backup/restic) or the encryption option of your backup software. #### Can I use IAM roles or temporary credentials? No. Zata has no STS, IAM roles or AssumeRole. To limit what a key can do, create a [sub-user](/sub-users/overview) with access to only the buckets it needs. To give someone temporary access to one file, [share a link](/buckets/share-a-file) that expires. #### Can sub-users create buckets? No. The account owner creates buckets and assigns them to sub-users. See [Assign a bucket](/sub-users/assign-a-bucket). #### A sub-user lists buckets and sees none. Is something wrong? 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](/sub-users/overview). #### Can I turn on Object Lock for an existing bucket? No. You can turn on Object Lock only when you create a bucket. See [Object Lock](/buckets/object-lock/overview). #### Can I see the server logs for my requests? No. Use your tool's debug output instead, for example `aws ... --debug` or `rclone ... -vv`. If you need more, [raise a ticket](/help/support): the support team can check the logs on Zata's side. ## Account and billing #### How long is the free trial? 15 days, with both regions included. You don't need a credit card. See [Create an account](/get-started/create-an-account). #### How does billing work? 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](/account/billing). #### Do I pay for uploads or downloads? 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](/account/ingress-and-egress). #### What happens if I miss a payment? 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](/account/billing#when-a-plan-expires). #### Can I change to a smaller plan? 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](/account/billing). #### Who do I contact about billing? Email [solutions@zata.ai](mailto:solutions@zata.ai) or call 1800-309-1433. For technical problems, [raise a ticket](/help/support). #### Where are the terms and privacy policy? See the [Zata privacy policy](https://zata.ai/zataprivacypolicies.pdf) (PDF).