SkarpChapter 2 of 10
Core Cloud Concepts and AWS Global Infrastructure
Peek under the hood of the AWS Cloud to see how Regions, Availability Zones, and edge locations work together to deliver global, resilient services—and why this matters for both your exam and real-world solutions.
Big Picture: Why Cloud and Why AWS Infrastructure Matters
Cloud + AWS Infrastructure
This module connects core cloud concepts with how AWS actually runs its global infrastructure, which is central for both the CLF-C02 exam and real-world solution design.
What Cloud Means
Cloud computing lets you access IT resources over the internet, on demand, with pay-as-you-go pricing. AWS owns and operates the hardware; you provision what you need when you need it.
Exam-Relevant Skills
For CLF-C02, you must explain key cloud benefits, describe Regions, AZs, and edge locations, and recognize basic AWS design principles like designing for failure and decoupling.
Why It Matters
Understanding AWS global infrastructure helps you choose where to deploy, how to survive outages, and when to use edge locations to reduce latency for your users.
Core Cloud Benefits: Elasticity, Agility, Pay-As-You-Go
Elasticity
Elasticity means you can quickly scale resources up or down based on demand. On AWS, services like EC2 Auto Scaling and load balancers help handle traffic spikes and drops automatically.
Agility
Agility is the ability to experiment and innovate faster by provisioning resources in minutes, not weeks. It lets teams test ideas and iterate quickly using AWS managed services.
Pay-As-You-Go
Pay-as-you-go pricing means you pay only for what you use, for as long as you use it, instead of investing in large upfront hardware costs. Examples include S3 storage and Lambda invocations.
Related Benefits
Cloud also offers global reach, high availability, and strong security foundations. These are enabled by AWS Regions, AZs, and edge locations, which you will explore next.
AWS Global Infrastructure: Regions, AZs, Edge Locations
Regions
An AWS Region is a physical geographic area, such as us-east-1 or eu-west-1. Each Region is isolated from others and contains multiple Availability Zones for resilience and data locality.
Availability Zones
An Availability Zone is one or more data centers with independent power, cooling, and networking. AZs in a Region are physically separated but linked by high-speed, low-latency networks.
Edge Locations
Edge locations are sites used by services like CloudFront and Route 53 to deliver content and DNS responses with low latency, by being geographically close to end users.
Hierarchy Recap
Think of the structure as Region → multiple AZs inside that Region → many edge locations worldwide that sit at the network edge for fast content delivery.
Visualizing Regions, AZs, and Edge Locations
World Map Mental Model
Picture a world map with big circles for Regions, smaller circles inside for AZs, and many small dots scattered globally for edge locations that serve content close to users.
Berlin User Scenario
A user in Berlin accesses an app in eu-central-1 (Frankfurt). The app runs across two AZs, while CloudFront caches static content in a nearby Berlin edge location.
Flow of a Request
The browser hits the nearest edge location. Cached static content is served from the edge, while dynamic API calls are forwarded to EC2 instances spread across multiple AZs.
Failure Scenario
If one AZ in the Region fails, the load balancer routes traffic to healthy instances in the other AZ. Edge locations keep serving cached content, improving resilience and user experience.
Thought Exercise: Choosing a Region and Using AZs
Work through this scenario to apply what you learned.
Scenario
You are designing a simple web application for a startup. Most users are in Southeast Asia, especially Singapore and Indonesia. The app must:
- Have low latency for these users.
- Survive a single data center failure.
- Keep costs reasonable (no need for multi-Region disaster recovery yet).
Your tasks
- Pick a Region (write down your choice):
- Which AWS Region would you choose first for these users, and why?
- Hint: Look for Regions geographically close to Singapore and Indonesia.
- Decide how many AZs to use:
- Would you deploy your EC2 instances in 1 AZ or 2+ AZs within that Region?
- Explain how your choice affects availability and cost.
- Edge locations:
- Would you use CloudFront edge locations in this design? If yes, what content would you cache?
- How would this affect user-perceived latency?
Write a short answer (3–5 sentences) covering:
- The Region you chose and your reasoning.
- How many AZs you use and why.
- Whether you use edge locations and for what.
After writing, compare your answer to this checklist:
- Region is close to users.
- At least 2 AZs for high availability.
- Optional but recommended: CloudFront for static assets and possibly API acceleration.
Basic AWS Design Principles: Design for Failure and Decoupling
Design for Failure
Assume servers, AZs, and networks can fail. Use multiple AZs, load balancers, and backups so your system keeps working even when individual components break.
Patterns for Resilience
Spread workloads across AZs, use Multi-AZ databases like RDS, and route traffic only to healthy instances. Regularly back up data to durable storage such as Amazon S3.
Decoupling Components
Decoupling means breaking systems into smaller parts that communicate via queues or events, so one part can fail or slow down without taking down everything else.
AWS Tools for Decoupling
Services like Amazon SQS, SNS, and EventBridge support asynchronous, loosely coupled architectures, enabling independent scaling and improved fault isolation.
Example Architecture: A Simple Highly Available Web App
Region and Network
For North American users, choose a Region like us-east-1 or us-west-2. Create a VPC with public subnets for the load balancer and private subnets in two AZs for EC2 instances.
Compute and Database
Place EC2 instances behind an Application Load Balancer and use Amazon RDS with Multi-AZ deployment so the database automatically fails over to a standby in another AZ.
Static Content and Edge
Store static assets in Amazon S3 and deliver them via CloudFront. Edge locations near users cache content to reduce latency and offload traffic from your origin.
Decoupled Background Work
Use an SQS queue between the web tier and background workers. Web servers enqueue image-processing tasks, and workers consume them asynchronously to avoid coupling.
Quick Check: Regions, AZs, and Edge Locations
Test your understanding of AWS global infrastructure concepts.
Which statement best describes the relationship between Regions, Availability Zones, and edge locations?
- Each Availability Zone contains multiple Regions, and Regions are connected to edge locations.
- Each Region contains multiple Availability Zones, and edge locations are separate sites that cache content closer to users.
- Each edge location contains multiple Availability Zones, and Regions only manage billing.
- Edge locations and Availability Zones are the same thing but used by different services.
Show Answer
Answer: B) Each Region contains multiple Availability Zones, and edge locations are separate sites that cache content closer to users.
A Region is a geographic area that contains multiple Availability Zones. Edge locations are separate sites used mainly by services like CloudFront to cache and deliver content close to end users.
Quick Check: Design Principles
Apply design for failure and decoupling to a scenario.
Your web app runs all EC2 instances in a single AZ and calls a background service synchronously over HTTP. Which change most directly applies AWS design principles?
- Move EC2 instances to a larger instance type in the same AZ.
- Add an SQS queue between the web app and background service, and run EC2 instances in at least two AZs.
- Change the Region to one closer to your development team.
- Use more on-premises servers instead of AWS.
Show Answer
Answer: B) Add an SQS queue between the web app and background service, and run EC2 instances in at least two AZs.
Using multiple AZs implements 'design for failure', while inserting an SQS queue between services decouples them. Together, these changes directly apply core AWS design principles.
Key Term Flashcards: Cloud and Infrastructure
Flip through these cards to reinforce core terms before moving on.
- Elasticity
- The ability to automatically or quickly scale IT resources up or down based on demand so you only use (and pay for) what you need at any given time.
- Agility
- The ability to provision and deprovision cloud resources rapidly, enabling faster experimentation, iteration, and innovation.
- AWS Region
- A physical geographic area containing multiple, isolated Availability Zones. Regions are isolated from each other for fault tolerance and data sovereignty.
- Availability Zone (AZ)
- One or more discrete data centers with independent power, cooling, and networking within an AWS Region, connected to other AZs by low-latency links.
- Edge Location
- A site used by services like Amazon CloudFront and Route 53 to cache and deliver content or DNS responses closer to end users, reducing latency.
- Design for failure
- An AWS design principle that assumes components will fail and builds redundancy, monitoring, and automatic recovery so the system continues to operate.
- Decoupling
- Designing systems as smaller, loosely connected components that interact via asynchronous mechanisms (such as SQS queues or SNS topics) to improve resilience and scalability.
- Pay-as-you-go pricing
- A cloud billing model where you pay only for the resources you consume, without large upfront capital expenses for hardware.
Key Terms
- Agility
- The capacity to provision and adjust cloud resources rapidly, enabling faster experimentation and delivery of new features.
- AWS Region
- A physical geographic area that contains multiple Availability Zones and is isolated from other Regions for fault tolerance and data residency.
- Amazon SQS
- Amazon Simple Queue Service, a fully managed message queuing service used to decouple and scale microservices, distributed systems, and serverless applications.
- Decoupling
- Architectural practice of splitting systems into smaller, loosely connected components that communicate asynchronously, improving resilience and scalability.
- Elasticity
- The ability to automatically or quickly scale cloud resources up or down based on real-time demand, so you use and pay for only what you need.
- Edge Location
- A site in the AWS global network used primarily by CloudFront and other edge services to cache and deliver content closer to users.
- Amazon CloudFront
- AWS content delivery network (CDN) service that uses edge locations to cache and deliver content with low latency.
- Design for failure
- An AWS design principle that assumes components can fail and uses redundancy, automatic failover, and recovery mechanisms to maintain service.
- Pay-as-you-go pricing
- A billing model where customers are charged only for the cloud resources they actually consume, with no large upfront hardware costs.
- Availability Zone (AZ)
- One or more discrete data centers with independent power, cooling, and networking within a Region, connected to other AZs with low-latency links.