How to Use ZATA's Mumbai Region: Setup Guide for S3-Compatible Storage

TL;DR

• ZATA Mumbai Region gives Western India teams S3-compatible object storage on Tier IV certified infrastructure, with data residency inside India.

• Setup is three steps: create an account, spin up a bucket in Mumbai, generate access keys.

• Any S3-compatible tool works out of the box: AWS CLI, boto3, rclone, Cyberduck, S3 Browser, Veeam, Restic. Only the endpoint changes.

Introduction

Where your storage lives now matters as much as what it costs. For teams running workloads in Mumbai, Pune, Ahmedabad, or Surat, sending every object read across the country (or offshore) adds latency, egress cost, and compliance friction you do not need. Regional object storage fixes that by putting your data next to your compute and your users. The Mumbai Region comes at no additional cost, maintaining the same ₹599/TB/month pricing as Indore.

Benefits of storing closer to your applications:

• Lower read and write latency for user-facing apps

• Cheaper, faster ingest from local pipelines

• Data residency alignment with Indian regulatory expectations

• Simpler disaster recovery when paired with a second region

What is ZATA Mumbai Region?

The Mumbai Region is ZATA's second Indian location for S3-compatible cloud storage, joining the existing Indore Region. Together they form a true multi-region object storage platform inside India.

Mumbai vs Indore at a glance:

Prerequisites Before You Begin

1. Sign up at zata.ai/signup.

2. Verify your email, verify your phone via OTP.

3. Log in to the ZATA Dashboard using your username or registered email.

Need more detail? Read the complete signup and activation guide.

Create a Storage Bucket in Mumbai Region

Inside the dashboard:

1. Go to Buckets → Create Bucket.

2. Enter a globally unique, lowercase bucket name (e.g., acme-media-prod).

3. Set Region to Mumbai (bom01).

4. Enable Versioning if you want object history, and enable Encryption for sensitive data.

5. Review and click Create.

Your bucket is now live in Mumbai and ready for S3 traffic.

Generate Access Keys

Go to Access Keys → Create New Key. Copy the Access Key ID and Secret Key immediately; the secret is shown only once.

Security basics that actually matter:

• Keep your Secret Key confidential and secure.

• One key per application or environment, so you can rotate independently.

Rotate every 90 days and revoke unused keys.

Connect Using S3-Compatible Tools

Endpoint: https://bom01.zata.ai | Region string: bom01

• AWS CLI

• bash

  aws configure --profile zata-mumbai
  aws --profile zata-mumbai \
      --endpoint-url https://bom01.zata.ai \
      s3 ls s3://acme-media-prod
  

Cyberduck / S3 Browser: choose the S3 profile, set server to bom01.zata.ai, paste your keys.

Backup tools (Veeam, Restic, Duplicati): configure a custom S3 endpoint at bom01.zata.ai, region bom01, and point at your bucket.

Upload and Manage Objects

Upload a file:

bash

aws --profile zata-mumbai --endpoint-url https://bom01.zata.ai \
    s3 cp video.mp4 s3://acme-media-prod/

Organize with prefixes (raw/, processed/, archive/) instead of deeply nested folders. Apply bucket policies for read-only public assets, and use scoped permissions for internal users.

Best Practices for Mumbai Region Deployments

• Enable versioning on any bucket holding source-of-truth data.

• Encrypt anything customer-related or subject to regulation.

• Automate backups with lifecycle rules that move cold data to archive tiers.

Design for multi-region from day one, even if you only deploy Mumbai first.

Common Use Cases

• AI & ML: dataset staging, model checkpoints, inference logs

• Enterprise backup: offsite backup target for on-prem and cloud workloads

• Media & content archives: ingest, archive, and CDN origin for video and image libraries

• SaaS storage: tenant data, uploads, and static assets served close to Indian users

Single Region or Multi-Region: Which Setup Fits You

Use Mumbai only if your users, compute, and compliance scope all sit in Western India and one region meets your RTO/RPO.

Use Mumbai + Indore when you need geographic redundancy, want a documented DR plan, or serve users nationally. Same API, same tools, no application rewrites required.

Troubleshooting Common Setup Issues

• SignatureDoesNotMatch: check the region is bom01 and keys have no trailing whitespace.

• AccessDenied: confirm the key belongs to the bucket's account.

• Virtual-host style errors: enable s3ForcePathStyle in your SDK.

Slow uploads from outside India: expected. Route through Indian compute or a CDN.

Conclusion

Getting started with the ZATA Mumbai Region takes minutes, not sprints. Create an account, spin up a bucket in bom01, generate keys, and point any S3-compatible tool at it. When you are ready for resilience, add Indore alongside it.

Ready to deploy?

Start at zata.ai or talk to the team about a multi-region architecture built for Indian workloads.

FAQs

1.What is the endpoint for the ZATA Mumbai Region?

https://bom01.zata.ai with region string bom01. Use it in any S3-compatible SDK or tool.

2.Do I need to change my code to use ZATA Mumbai?

No. Point your existing S3 client at the Mumbai endpoint and region; your SDK calls stay the same.

3.Is my data stored only in India?

Yes. Data in the Mumbai Region stays within Indian borders on MeitY-empanelled, Tier IV certified infrastructure.

4.Can I replicate data between Mumbai and Indore?

Yes. Use rclone sync, aws s3 sync, or scheduled jobs to mirror buckets across regions for DR.

5. Which S3 tools work with ZATA Mumbai?

AWS CLI, boto3, rclone, Cyberduck, S3 Browser, Veeam, Restic, Duplicati, MinIO client, and any other S3-compatible client.