What AWS Region is Mumbai in?

The AWS Mumbai Region code is ap-south-1. It launched in June 2016 and contains three Availability Zones: ap-south-1a, ap-south-1b, and ap-south-1c. Mumbai is the first commercial AWS Region in India and remains the largest by service breadth as of 2026. A second Indian Region, ap-south-2 (Hyderabad), launched in November 2022.

Region naming explained

AWS Region codes follow the pattern {geography}-{direction}-{number}. So ap-south-1 reads as Asia Pacific, southern grouping, first Region in that grouping. The three-letter code BOM often seen in dashboards and pricing pages is the IATA airport code for Chhatrapati Shivaji Maharaj International Airport, not an AWS Region identifier. Always use ap-south-1 in API calls, IAM policies, and infrastructure-as-code.

India AWS Regions at a glance

Both Regions are fully operated by AWS India Private Limited under Indian law, which simplifies invoicing in INR with GST. AWS also operates Local Zones and edge locations across additional Indian cities for latency-sensitive workloads.

Mumbai vs Hyderabad: which to pick

• Service breadth: Mumbai (ap-south-1) has more services in General Availability than Hyderabad as of 2026. New AWS services typically reach ap-south-1 before ap-south-2.
• Disaster recovery pairing: ap-south-1 and ap-south-2 are an obvious in-country DR pair, giving you cross-Region resilience without leaving Indian soil.
• Latency to user base: Mumbai favours western and central India and the Middle East. Hyderabad favours southern India.
• Data residency: Both keep data inside India, important for DPDP Act 2023 alignment and RBI / SEBI regulated workloads.

Practical guidance for Indian architects

For new workloads, default to ap-south-1 for primary deployment because of service maturity, and use ap-south-2 as the warm DR Region. Verify service availability per Region on the AWS Regional Services List before committing, since not every service has launched in every Indian Region. If you operate cross-border applications, peer ap-south-1 with ap-southeast-1 (Singapore) or eu-west-1 (Ireland) for global reach. For migration planning, see how to migrate to cloud computing and our comparison of AWS vs Azure vs GCP.

How Opsio helps

Opsio is an AWS Partner with a delivery footprint in India, building landing zones across ap-south-1 and ap-south-2 for enterprises that need data residency, RBI alignment, or in-country DR. Our Managed AWS Services team handles Region selection, Availability Zone design, and cost optimisation. For migration projects, our cloud architects design the target Region topology before any workload moves.

Frequently Asked Questions

Is Mumbai the same as BOM in AWS?

BOM is the IATA airport code that AWS uses informally in console labels and pricing pages, but the API and CLI Region code is ap-south-1. You should always use ap-south-1 in CloudFormation, Terraform, IAM, and SDK calls.

How many Availability Zones does ap-south-1 have?

ap-south-1 has three Availability Zones: ap-south-1a, ap-south-1b, and ap-south-1c. Multi-AZ deployments across all three are the standard pattern for production workloads requiring high availability.

Can I host data in India only?

Yes. AWS keeps customer data in the Region you select. By deploying exclusively in ap-south-1 and ap-south-2 and disabling Region replication for managed services, you keep data inside Indian borders, which supports DPDP Act 2023 and sector regulator requirements.

Does ap-south-2 (Hyderabad) have the same services as Mumbai?

No, not yet. Mumbai has a wider catalogue in General Availability as of 2026 because it launched six years earlier. Check the AWS Regional Services List for the specific services you depend on before standardising on Hyderabad.

How do I move workloads between Indian Regions?

For cross-Region replication, use AWS DataSync, S3 Cross-Region Replication, or database-native replication such as RDS read replicas. To migrate workloads between cloud providers entirely, see our guide on how to migrate from Azure to AWS.