Settings for any S3 tool

Zata works with tools and code libraries that speak the Amazon S3 API. Every one of them asks for the same few values. Enter the values below, and the tool connects to your buckets.

The four settings

Good to know:

• Region name. Zata does not check the region name, so any value works. Use us-east-1 when the tool asks for one, or when it forces you to pick an AWS region from a list.
• Keys belong to one region. An Indore key does not work on the Mumbai endpoint (you get InvalidAccessKeyId or AccessDenied), and the other way round. Create a key in each region you use. See Access keys.
• Path-style means https://idr01.zata.ai/my-bucket. Virtual-host style (https://my-bucket.idr01.zata.ai) also works, except for bucket names that contain a dot: those fail the certificate check, so use path-style.
• Signature. Use Signature V4. V2 also works.
• HTTPS. Always use https://. The endpoints use normal public certificates, so you never need to install a certificate or turn certificate checks off.
• Sub-user keys. A sub-user’s key cannot create buckets, and its bucket list is empty even for buckets it can use. Type the bucket name directly in the tool. See Sub-users.

Tools built on the AWS SDK

AWS SDKs and the AWS CLI released from January 2025 add checksums to uploads by default. Zata does not accept them on large (multipart) uploads, which then fail with XAmzContentSHA256Mismatch. Small files still upload, so the problem shows up only later. With the AWS SDK for Java 2.30 and newer, every upload fails.

Set checksums to “when required”. Each tool page shows where to set it. For any other app built on an AWS SDK, set these two environment variables before you start it:

export AWS_REQUEST_CHECKSUM_CALCULATION=when_required
export AWS_RESPONSE_CHECKSUM_VALIDATION=when_required

See Large uploads for details.

Guides for each tool

Guides marked Tested were tested end to end on Zata in October 2026.

Command line

Code and SDKs

Desktop apps

Mount as a drive

Backup software

Servers, NAS and websites

Other S3 apps

Your app is not in the list? Any app that supports S3-compatible storage can use Zata. The field names differ from app to app. The usual names are:

If the app asks for a host name without https://, enter idr01.zata.ai (or bom01.zata.ai) and turn HTTPS on.

If the app is built on an AWS SDK and large uploads fail, set the checksum variables. To check which S3 features the app may need, see What works with Zata.