> 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.

# S3Drive

S3Drive is a desktop app that browses cloud storage and syncs local folders to it. It connects to Zata through an **Rclone** account. This page sets up the account and a folder sync on Windows.

## Before you start

* A bucket — see [Create a bucket](/buckets/create-a-bucket).
* An access key from the same region as the bucket — see [Access keys](/access/access-keys).
* S3Drive installed and signed in — [download S3Drive](https://s3drive.app).

## Connection settings

S3Drive takes the connection as an rclone config in JSON form:

| Setting                               | Value                                                                                         |
| ------------------------------------- | --------------------------------------------------------------------------------------------- |
| `type` / `provider`                   | `s3` / `Other`                                                                                |
| `endpoint`                            | `https://idr01.zata.ai` for Indore, `https://bom01.zata.ai` for Mumbai                        |
| `region`                              | `us-east-1`                                                                                   |
| `access_key_id` / `secret_access_key` | from **Access Keys** in the Zata console — the key must be from the same region as the bucket |
| `no_check_bucket`                     | `true` — needed for sub-user keys                                                             |
| `sign_accept_encoding`                | `false` — newer rclone versions get `SignatureDoesNotMatch` on Zata without it                |

## Set up S3Drive

#### Open Manage account

In S3Drive, select the **Manage account** button at the top right of the **Files** screen.

![The S3Drive Files screen with the Manage account button highlighted at the top right](/_fern-img/97a3ce5b9a51969f0d1e1b92bbcf555eae2bd5fbaf1025ee8ba1cb71fc041e61.webp)

#### Add an Rclone account

On **Accounts**, open the **Rclone** tab and select **+**.

![The Accounts screen with the Rclone tab and the plus button highlighted](/_fern-img/bfd0fcbef8d394d91cb04732c04d4c1fa81ff699d4db33add99f146f16969d27.webp)

Paste this config with your own keys, then add it. For Mumbai, use `https://bom01.zata.ai` as the endpoint.

**`Rclone config`**

```json Rclone config
"zata": {
    "type": "s3",
    "provider": "Other",
    "access_key_id": "YOUR_ACCESS_KEY",
    "secret_access_key": "YOUR_SECRET_KEY",
    "endpoint": "https://idr01.zata.ai",
    "region": "us-east-1",
    "no_check_bucket": "true",
    "sign_accept_encoding": "false"
},
```

#### Open the account

The new account appears on the **Rclone** tab. Select it to see your Zata buckets.

![The new Rclone account listed on the Rclone tab](/_fern-img/a97db7d0972a6cdb432f4cca236ee90f984734b8f99c920dfbd785f9c1afa062.webp)![The S3Drive Files screen listing three Zata buckets](/_fern-img/7a0a17c136f6f57a7a3c5c52e98df1b5240e9289be2ae436f8efc911cfc39f42.webp)

#### Add a sync

Open the menu, select **Sync**, then select **+**.

![The Sync screen with the plus button highlighted](/_fern-img/c14b343fb1fba4b2a9e6b8a992ef2b1d8b77befe42b7c5dcdf54242a1f430260.webp)

#### Configure the sync

In **Configure sync**:

| Field          | Value                                                                        |
| -------------- | ---------------------------------------------------------------------------- |
| **From**       | **Local** → pick the folder to back up                                       |
| **To**         | **Remote** → choose your Zata account and bucket (shown as `zata:my-bucket`) |
| **Mode**       | for example **Copy**                                                         |
| **Sync every** | how often to run, in minutes — `1440` is once a day                          |

Select **Save**.

![Configure sync with a local folder as source, a Zata bucket as destination, mode Copy and Sync every 1440 min](/_fern-img/df77db9d37d06acdbc012db321afa6df055c08ddd62b8ee4626f8aac1a0171d9.webp)

The sync now shows on the **Sync** screen with its source, destination, mode and schedule.

![A saved sync job from a local folder to a Zata bucket, mode Copy](/_fern-img/6c7aea3d1d7c78dbe674d690a169dfa3b84b42a45af41f5047b8393f8d0570e4.webp)

## Test it

Put a small file in the local folder and wait for the sync to run. Open the bucket in the Zata console under **Buckets** and check that the file is there. Then open the bucket in S3Drive and download the file.

## Troubleshooting

| Problem                                      | Fix                                                                                                                           |
| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| No buckets under the account                 | Check that the endpoint matches the region of your key. Sub-user keys never list buckets.                                     |
| `SignatureDoesNotMatch`                      | Make sure `"sign_accept_encoding": "false"` is in the config. See [Signature errors](/help/troubleshooting/signature-errors). |
| `AccessDenied` on upload with a sub-user key | Make sure `"no_check_bucket": "true"` is in the config.                                                                       |
| Access denied or invalid key                 | Copy the keys again from **Access Keys**, without extra spaces.                                                               |
| Files do not reach the bucket                | Check that **To** points to the right bucket and that the sync has run.                                                       |