Cloud fundamentals

Regions, Zones & Edge Locations

The cloud isn't one giant computer somewhere — it's a hierarchy of physical locations, and where you place things changes latency, resilience, and compliance.

Region

A geographic area a provider operates in (e.g. “US East”), made up of multiple isolated locations. Most resources are created within a single region.

Availability Zone

One isolated location within a region — its own power, cooling, and networking — so a failure in one zone shouldn't take down the others.

Edge location

A smaller facility, in far more cities than regions exist, used to cache or serve content close to end users — the mechanism behind a CDN.

Same hierarchy, different names

AWS, Azure, and GCP all use a region → zone → edge hierarchy — the terms just don't line up one-to-one.

ConceptAWSAzureGCP
RegionRegion (e.g. us-east-1)Region (e.g. East US)Region (e.g. us-central1)
Isolated location within a regionAvailability Zone (AZ)Availability ZoneZone
Points close to end users for low-latency deliveryEdge Location / CloudFront PoPPoint of Presence (Azure Front Door)Edge Point of Presence (Cloud CDN)

Why the choice matters

Picking a region or spreading across zones isn't just an ops detail — it's a design decision with real tradeoffs.

Latency

Picking a region close to your users cuts round-trip time; edge locations push cacheable content even closer, without moving the origin.

Resilience

Spreading a workload across multiple AZs within a region means one data center failing (power, network, fire) doesn’t take the whole system down.

Data residency & compliance

Some regulations require customer data to stay within a specific country or region — the region you pick can be a compliance decision, not just a performance one.

Disaster recovery

Multi-region designs protect against a failure that takes out an entire region, not just a single zone — at the cost of more complexity and cross-region data sync.

Related

See region, availability zone, and edge location in the Glossary.