Region & Availability Zone

A region is a geographic area where a cloud provider operates data centres, AWS us-east-1 (Virginia), Azure Canada Central, Google Cloud europe-west1. An availability zone (AZ) is one or more physically isolated data centres inside that region, each with independent power, cooling, and networking, linked to its siblings by fast private fibre.

In plain terms

The region is the city; the AZs are separate buildings across it, far enough apart that a fire, flood, or grid failure in one leaves the others untouched, close enough that traffic between them takes a millisecond or two. All three major providers use the same model, and the standard production pattern is identical everywhere: run your app across two or three AZs so that when one building goes dark, the others keep serving and nobody outside the ops channel notices.

Why it matters when you migrate

• Region choice is latency, price, and law in one decision. Pick close to your users, but check data-residency rules first, Canadian and EU data often must stay in-region, and the shared responsibility model puts that obligation on you, not the provider.
• Multi-AZ is the uptime baseline, not the premium tier. A single-AZ deployment is cheaper and has zero protection against a data-centre outage. Production databases and anything behind a load balancer should span AZs from day one.
• Traffic between AZs is billable. Cross-zone data transfer is a real line item chatty architectures feel, put it in your cost estimate, not your first invoice surprise.