> 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. # 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 | Setting | Value | | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Endpoint (also called Service URL, Server or Host) | `https://idr01.zata.ai` for **Indore**, `https://bom01.zata.ai` for **Mumbai**: the region your bucket is in | | Region | `us-east-1` | | Access key and secret key | From **Access Keys** in the Zata console. The key must be from the same region as the bucket. | | Addressing (URL style) | Path-style, if the tool asks | 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](/access/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](/sub-users/overview). ## 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: ```bash export AWS_REQUEST_CHECKSUM_CALCULATION=when_required export AWS_RESPONSE_CHECKSUM_VALIDATION=when_required ``` See [Large uploads](/help/troubleshooting/large-uploads) for details. ## Guides for each tool Guides marked **Tested** were tested end to end on Zata in October 2026. ### Command line #### [AWS CLI](/connect/command-line/aws-cli) Tested #### [rclone on Linux](/connect/command-line/rclone-linux) Tested #### [rclone on Windows](/connect/command-line/rclone-windows) Tested settings #### [rclone GUI](/connect/command-line/rclone-gui) rclone's web interface #### [s3cmd](/connect/command-line/s3cmd) Tested #### [MinIO Client (mc)](/connect/command-line/minio-mc) Tested #### [s5cmd](/connect/command-line/s5cmd) Tested ### Code and SDKs #### [Python (boto3)](/connect/code/python) Tested #### [JavaScript and Node.js](/connect/code/javascript) Tested #### [Java](/connect/code/java) Tested #### [Go](/connect/code/go) Partly tested ### Desktop apps #### [Cyberduck](/connect/desktop-apps/cyberduck) Windows and macOS #### [S3 Browser](/connect/desktop-apps/s3-browser) Windows #### [S3 Browser with a sub-user key](/connect/desktop-apps/s3-browser-sub-user) Open a bucket by name #### [WinSCP](/connect/desktop-apps/winscp) Windows #### [CrossFTP](/connect/desktop-apps/crossftp) Windows, macOS and Linux #### [SmartFTP](/connect/desktop-apps/smartftp) Windows #### [ForkLift](/connect/desktop-apps/forklift) macOS #### [S3Drive](/connect/desktop-apps/s3-drive) Desktop and mobile ### Mount as a drive #### [s3fs on Linux](/connect/mount/s3fs) Partly tested #### [TntDrive](/connect/mount/tntdrive) Windows #### [NetDrive 3](/connect/mount/netdrive) Windows and macOS #### [ExpanDrive](/connect/mount/expandrive) Windows, macOS and Linux #### [CloudMounter](/connect/mount/cloudmounter) macOS and Windows #### [odrive](/connect/mount/odrive) Sync folders #### [goofys](/connect/mount/goofys) Tested ### Backup software #### [Veeam](/connect/backup/veeam) #### [Acronis](/connect/backup/acronis) #### [MSP360](/connect/backup/msp360) #### [CloudBerry Explorer](/connect/backup/cloudberry) #### [Commvault](/connect/backup/commvault) #### [AhsayCBS](/connect/backup/ahsay) #### [Vembu](/connect/backup/vembu) #### [Iperius Backup](/connect/backup/iperius) #### [Handy Backup](/connect/backup/handy-backup) #### [Arq Backup](/connect/backup/arq) #### [qBackup](/connect/backup/qbackup) #### [GoodSync](/connect/backup/goodsync) #### [Syncovery](/connect/backup/syncovery) #### [restic](/connect/backup/restic) Tested #### [Duplicati](/connect/backup/duplicati) Tested ### Servers, NAS and websites #### [Proxmox Backup Server](/connect/servers/proxmox) #### [QNAP NAS](/connect/servers/qnap) #### [cPanel](/connect/servers/cpanel) #### [Plesk](/connect/servers/plesk) #### [WordPress (UpdraftPlus)](/connect/servers/wordpress) ## 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: | Setting | Value | | ------------------------------------------------------ | -------------------------------------------------------------------- | | Provider or storage type | S3-compatible, **Other** or **Custom S3**. Do not pick "Amazon S3". | | Endpoint, Service URL, Server or Host | `https://idr01.zata.ai` (Indore) or `https://bom01.zata.ai` (Mumbai) | | Region | `us-east-1` | | Access Key or Access Key ID | Your access key | | Secret Key or Secret Access Key | Your secret key | | Path-style, Force path style or Use path request style | On | | Signature version | V4 | | HTTPS, SSL or Secure connection | On | 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](#tools-built-on-the-aws-sdk). To check which S3 features the app may need, see [What works with Zata](/connect/s3-compatibility).