Cloud Region

A region is the top-level location unit in every major cloud. AWS, Google Cloud, and Azure all divide the world into a few dozen regions, and each one is a separate physical footprint in a specific part of the world. AWS calls them things like us-east-1 (Northern Virginia), eu-west-1 (Ireland), and ap-south-1 (Mumbai). Azure uses names like East US and West Europe. Google uses asia-southeast1, us-central1, and so on.

Inside a region there are multiple availability zones. An availability zone is one or more physically separate data centers with their own power, cooling, and network. AWS regions usually have 3 to 6 zones. The zones in a region are close enough to talk over a fast private network with single-digit millisecond latency, but far enough apart that a fire, flood, or power failure in one zone does not take down the others.

The key mental model: a region is where your stuff lives on the map, and availability zones are the independent failure domains inside that map location. When you launch a server or create a database, you almost always pick a region first, then a zone.

Most cloud services are regional, meaning the resource exists only in the region you created it in and is invisible from other regions unless you set up replication. An S3 bucket created in eu-west-1 stores its objects in Ireland. A database in ap-south-1 keeps its data in Mumbai. Networking is also regional: a virtual private network (a VPC in AWS) spans the zones of one region but does not stretch across regions on its own.

Regions are deliberately isolated from each other so that a problem in one cannot cascade into another. They run on separate control planes, and the provider routes traffic between them over its own backbone. The famous us-east-1 outages at AWS stayed mostly contained to that region precisely because of this design, though some global services that depend on us-east-1 have been dragged down with it.

To go cross-region you replicate on purpose. You enable S3 cross-region replication, set up a database read replica in a second region, or front everything with a global DNS service like Route 53 or a CDN like CloudFront that steers each user to the nearest healthy region.

Three forces decide the region. Latency: put compute near your users, because the speed of light means a request from Mumbai to a server in Virginia adds roughly 200 milliseconds of round trip before any work happens. Data residency and compliance: rules like the EU GDPR, India's data localization requirements, and various banking regulations force certain data to physically stay inside a country, so you must use a region in that country. Cost: prices vary by region, and the same instance can cost 10 to 30 percent more in places like Sao Paulo or some Asia Pacific regions than in us-east-1.

The trade-offs are real. A single region is simpler and cheaper but means a regional outage takes you fully offline. Going multi-region buys you resilience and lower global latency, but cross-region data transfer is billed per gigabyte, replication adds lag, and keeping data consistent across regions is genuinely hard. Most teams start in one region close to their main users and add a second region only when uptime or latency demands it.

A common default is to launch in us-east-1 because it is the oldest, cheapest, and has the widest service support, but that is also the busiest region and the one most affected by large AWS incidents.

Say you run a payments app for Indian users. You pick ap-south-1 (Mumbai) as your primary region so latency to users stays under 50 milliseconds and customer data stays in India to satisfy RBI localization rules. You spread your servers across the three Mumbai availability zones so a single data center failure does not take you down.

For disaster recovery you keep an asynchronous database replica in ap-south-2 (Hyderabad) and store backups in another region. If all of Mumbai goes dark, you can promote the Hyderabad replica and redirect traffic. Netflix runs this pattern at scale across three AWS regions and can evacuate an entire region in under an hour by shifting traffic to the others.