AWS Certified Cloud Practitioner
AWS Regions and Availability Zones
Learn how AWS organizes its global infrastructure into Regions and Availability Zones, and the four factors that decide which Region you should run a workload in.
- Define an AWS Region and an Availability Zone
- Explain why each Region has at least three physically separate Availability Zones
- Describe how Availability Zones are isolated yet connected with low-latency networking
- Identify the four factors for choosing a Region: compliance, latency, pricing, and service availability
- Explain why most AWS resources are scoped to a single Region
Why this matters
Every resource you launch in AWS runs somewhere physical. AWS organizes all of that hardware into a global structure of Regions and Availability Zones, and almost every service decision starts with picking the right one. The exam tests this directly, and in real work the choice affects your latency, your costs, and whether you meet the law.
The structure is simple once you see the layers: the world is divided into Regions, each Region holds several Availability Zones, and each Availability Zone is built from one or more data centers.
What is a Region
An AWS Region is a physical location in the world where AWS clusters its data centers. Examples include US East (Ohio), Europe (Ireland), and Asia Pacific (Sydney). Each Region has a code you will see throughout AWS, such as us-east-2, eu-west-1, or ap-southeast-2.
Regions are isolated from one another by design. Resources you create in one Region are not automatically copied to another, and traffic stays within a Region unless you explicitly move it. This isolation is a feature: a problem in one Region does not spill into the others. It also means you choose a Region on purpose for each workload, rather than getting a single global pool of resources.
What is an Availability Zone
An Availability Zone (AZ) is one or more discrete data centers within a Region, each with its own redundant power, networking, and connectivity, housed in separate facilities. Each Region has at least three Availability Zones.
The zones in a Region are far enough apart that a single fire, flood, or power outage is unlikely to hit more than one of them. At the same time, they are close enough to be linked by high-bandwidth, low-latency, dedicated fiber, so data moves between them quickly. All traffic between Availability Zones is encrypted. This combination, separate enough to fail independently but connected enough to work together, is the foundation of high availability on AWS.
AZ codes are the Region code plus a letter, like us-east-2a, us-east-2b, and us-east-2c. There is also a stable AZ ID, such as use2-az1, that points to the same physical zone in every account, which is useful when you need to line up zones across accounts.
Choosing the right Region
You are not meant to spread a workload across every Region. You pick one (or a few) based on four main factors.
| Factor | Question it answers |
|---|---|
| Compliance | Does a law require the data to stay in a specific country or area? |
| Latency | Which Region is closest to your users, for the fastest response? |
| Pricing | Service prices differ by Region. Which fits your budget? |
| Service availability | Are the services and features you need offered in that Region? |
Compliance usually wins when it applies. If a data residency law says customer data must stay inside a country, you choose a Region in that country first, then weigh the rest. After that, latency and proximity to your users drive a better experience, pricing varies because the same service can cost more in one Region than another, and service availability matters because not every service launches in every Region at the same time.
Region versus Availability Zone in practice
Most AWS services are Regional or zonal, so it helps to know which scope you are working in.
- You launch an EC2 instance into a specific Availability Zone.
- You create an Amazon S3 bucket in a Region, and S3 spreads the data across zones for you.
- To survive the loss of one data center, you run across multiple Availability Zones in the same Region. This is the Multi-AZ pattern, covered later in this topic.
A few services are global rather than Regional, such as IAM and Amazon Route 53, but those are the exception. The default mental model is: a Region holds zones, and you place resources into zones inside the Region you chose.
Exam tips
- An AWS Region is a physical location that contains multiple Availability Zones; Regions are isolated from each other.
- Each Region has at least 3 Availability Zones.
- An Availability Zone is one or more discrete data centers with redundant power and networking, physically separated but linked by low-latency, encrypted, high-bandwidth fiber.
- Choose a Region using 4 factors: compliance (data residency), latency (proximity to users), pricing (varies by Region), and service availability (not every service is in every Region).
- Compliance and data residency requirements override the other factors when they apply.
- Running across multiple Availability Zones in a Region is how you build for high availability.