Chapters0/41 ▾
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
Chapter 6 · Lesson 3 of 4
Regions, Availability Zones and high availability
1 min read
AWS's infrastructure nests in a fixed order. A Region is a separate geographic area. Each Region contains multiple Availability Zones, and AWS defines an Availability Zone as one or more discrete data centers with redundant power, networking and connectivity, so it is not always a single building.
Availability Zones in a Region are physically separated and do not share single points of failure, so trouble in one is unlikely to spread to another. Edge locations sit outside this nesting: they are separate sites that deliver cached content close to users, and you do not launch instances or databases there.
High availability is the customer's design job. AWS does not spread your instances across zones by default.
A single instance is a single point of failure no matter how large it is. The standard answer for surviving the loss of one data center is to run instances in at least two Availability Zones of the same Region, which costs far less effort than a second Region.
Example: a booking site runs two web servers in one zone. If that zone has a power failure, both go down. Moving one server to a second zone in the same Region keeps the site up.
Check yourself
1. A company wants its web application to keep running if a single data center fails. It wants the lowest added cost and complexity that meets this requirement. What should it do?
2. A risk officer asks why a failure in one Availability Zone is unlikely to take down another Availability Zone in the same Region. Which explanation is accurate?
Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, AWS Global Infrastructure: Regions and Availability Zones, AWS CloudFormation User Guide
AWS Cloud Practitioner cheat sheet: every key fact on one page →