Availability zone

Also known as: AZ

On this page 7

An availability zone (AZ) is a physically separate location within a cloud region, made up of one or more data centers with independent power, cooling and networking, and connected to the other zones of the same region by high-bandwidth, low-latency links. Among the cloud fundamentals, it is the basic unit of fault isolation that providers expose to customers.

Spreading workloads across several availability zones lets a system survive the failure of an entire facility without leaving the region. Amazon Web Services, Microsoft Azure and Google Cloud all use the concept, although the details of naming and guarantees differ between them.

How availability zones are built and connected

Availability zones are engineered so that a single physical event should not affect more than one zone. Providers place them kilometers apart, typically within roughly 100 kilometers of each other, far enough to avoid shared floods, fires or power grid faults, yet close enough to keep network latency low.

Inside a region, zones are linked by redundant private fiber with round-trip latency usually in the range of one to two milliseconds. This latency budget is what makes synchronous replication between zones practical, which is not usually the case between distant regions.

The table below summarizes the physical properties that define a zone and why each one matters.

PropertyTypical designWhy it matters
Power supplySeparate utility feeds and generatorsA grid fault stays local
CoolingIndependent cooling plantOverheating does not spread
NetworkOwn uplinks plus inter-zone fiberConnectivity loss stays local
Physical distanceSeveral to tens of kilometers apartLimits shared natural hazards
Inter-zone latencyAbout 1 to 2 ms round tripAllows synchronous replication
Defining properties of an availability zone

Availability zones compared with regions and edge locations

An availability zone sits in a hierarchy of cloud geography: a region contains several zones, and each zone contains one or more data centers. Confusing these levels leads to designs that are either less resilient or more expensive than intended.

LevelScopeProtects againstTypical latency between units
Data centerSingle buildingRack or host failuresSub-millisecond
Availability zoneOne or more data centersFacility-wide outagesAbout 1 to 2 ms
Cloud regionUsually three or more zonesZone failuresTens of milliseconds
Multi-regionSeveral geographic areasRegional disastersTens to hundreds of ms
Edge locationPoint of presence near usersNot a resilience unitClose to end users
Levels of cloud geography

Edge computing locations serve content and lightweight compute close to users, but they are not substitutes for availability zones. A zone hosts full infrastructure services, whereas an edge site mainly caches or terminates connections.

Zonal, regional and global cloud services

Cloud services differ in how they relate to availability zones, and this relationship determines who is responsible for resilience. Under the shared responsibility model, a customer who places a zonal resource in one zone owns the risk of that zone failing.

Service scopeTypical examplesWho handles zone failure
ZonalVirtual machines, block storage volumesThe customer, by deploying in several zones
Zone-redundantManaged databases in multi-zone modeThe provider, once the option is enabled
RegionalObject storage, serverless functionsThe provider, automatically
GlobalDNS, identity, content deliveryThe provider, across regions
Service scope and resilience responsibility

A frequent misunderstanding is that a managed database is automatically resilient. Many services offer a single-zone tier at lower cost, and only the multi-zone or zone-redundant option keeps a synchronized standby in a second zone.

Designing multi-zone architectures

The standard pattern is to run at least two, preferably three, copies of every tier in different zones behind a load balancer. With three zones, the loss of one still leaves two-thirds of capacity and keeps a majority for consensus systems that need a quorum.

  • Place application instances in an auto scaling group spanning several zones so that capacity is replaced automatically.
  • Use a zone-redundant load balancer that stops routing to unhealthy zones.
  • Replicate stateful data synchronously across zones for a recovery point objective near zero.
  • Provision headroom of about 50 percent in a two-zone design, because one zone must carry the full load.
  • Test resilience with zone failure exercises, not only with the loss of single instances.

The decision table below matches typical requirements with an appropriate placement strategy.

RequirementRecommended placementReason
Development or test systemSingle zoneLowest cost, outages acceptable
Production web applicationTwo or three zonesSurvives a facility outage
Quorum-based database clusterThree zonesKeeps a majority after one failure
Regulated critical serviceMulti-zone plus second regionCovers regional disasters as well
Choosing a zone placement strategy

Costs, limitations and common mistakes

Multi-zone designs are not free. Most providers charge for data transfer between zones, so chatty services split across zones can generate significant hidden network costs. Synchronous replication also adds a small write latency penalty to every transaction.

Zones also share regional control planes and some regional dependencies. Several historical cloud incidents affected multiple zones at once because a regional management service failed, which is why the most critical systems add a second region rather than relying on zones alone.

MistakeConsequenceRemedy
All instances in one zoneFull outage when the zone failsSpread instances across zones
Assuming zone names match across accountsMisaligned placement between teamsMap zones by provider zone IDs
No spare capacity per zoneOverload after a zone failurePlan for N+1 zone capacity
Ignoring inter-zone traffic chargesUnexpectedly high billsKeep chatty components zone-local
Typical mistakes and their remedies

The naming issue deserves attention: in some platforms, a label such as “zone a” is mapped differently for each account, so two teams referring to the same name may actually be in different physical zones.

Understanding it simply

Imagine a company that keeps its important files in three separate buildings across a city. Each building has its own power and its own internet line, and the buildings are connected by fast private cables.

If one building loses electricity, the other two keep working and nobody loses their files. An availability zone is one of those buildings, and a cloud region is the whole city. Using several zones means one local accident cannot stop the service.

Applied in practice

An online retailer runs its shop in a single cloud region with three availability zones. Web servers run in an auto scaling group with two instances per zone, a zone-redundant load balancer distributes traffic, and the order database uses a multi-zone configuration with a synchronous standby in a second zone.

During a busy sale weekend, a cooling failure takes one zone offline for about two hours. The load balancer stops sending requests there within seconds, the remaining zones absorb the traffic, and the auto scaling group adds instances to restore capacity. The database standby was not in the affected zone, so no failover was needed. Customers notice only slightly slower pages, and no orders are lost during the incident.