Skip to navigation
Get started

Endpoints and regions

The endpoint URL and settings to type into any S3 tool.

Zata has two regions, both in India. Each region has its own endpoint. Point your tool at the endpoint of the region where your bucket is.

Region (as the console shows it)CodeEndpointLocation
Indoreidr01https://idr01.zata.aiIndore, Madhya Pradesh
Mumbaibom01https://bom01.zata.aiMumbai, Maharashtra

Settings for any S3 tool

SettingValue
Endpoint (also called service URL or server)https://idr01.zata.ai or https://bom01.zata.ai, the region of your bucket. If an app asks for a host name only, enter idr01.zata.ai or bom01.zata.ai and turn HTTPS on.
Regionus-east-1. Zata does not check the region name, so if a tool makes you pick one, any value works.
Access key and secret keyFrom Access Keys in the Zata console. The key must be from the same region as the bucket.
URL stylePath-style (recommended). Virtual-host style also works.
SignatureV4 (recommended). V2 also works.

Always use https://. A request to http:// is redirected to https://, and many tools fail after the redirect.

One region per bucket, one region per key

  • A bucket is in one region, the one you chose when you created it. You can’t move a bucket to the other region. To move data, copy it into a bucket in the other region, for example with rclone.
  • An access key works in one region only. An Indore key gets InvalidAccessKeyId or AccessDenied on the Mumbai endpoint, and the other way round. If you use both regions, create a key in each. See Access keys.

To see a bucket’s region, open Buckets in the console and look at the Region column. S3 tools don’t show it: aws s3 ls lists names and dates only.

To check from the command line, run head-bucket with a profile set up for one region. No output means the bucket is in that region. A 404 error means it isn’t there, or the name is wrong.

aws s3api head-bucket --bucket my-bucket --profile zata

Path-style and virtual-host style

StyleExample URL
Path-style (recommended)https://idr01.zata.ai/my-bucket/myfile.txt
Virtual-host stylehttps://my-bucket.idr01.zata.ai/myfile.txt

Both work. Use path-style when a bucket name contains a dot (.): in virtual-host style such names fail the certificate check.

Zata uses public Let’s Encrypt certificates for idr01.zata.ai, bom01.zata.ai and their subdomains. Every operating system trusts them, so you never need a custom certificate. Don’t turn off certificate checks in your tool.

Differences between the regions

Both regions offer the same features with one exception: in lifecycle rules, the options to keep only the newest versions and to filter by object size are available only in Mumbai.

Your plan covers both regions. Storage you use in Indore and Mumbai counts towards the same plan. See Billing.

If something doesn’t connect

See Wrong endpoint or region for NoSuchBucket, InvalidAccessKeyId and redirect errors.