AWS Overview & Global Infrastructure
Amazon Web Services (AWS) is a comprehensive, evolving cloud computing platform provided by Amazon. It provides a mix of infrastructure as a service (IaaS), platform as a service (PaaS) and packaged software as a service (SaaS) offerings.
Core Concepts: The Six Advantages of Cloud
- Trade capital expense for variable expense: Pay only when you consume resources.
- Benefit from massive economies of scale: Lower pay-as-you-go prices due to AWS’s size.
- Stop guessing capacity: Eliminate idle resources or limited capacity.
- Increase speed and agility: Reduce time to provision resources from weeks to minutes.
- Stop spending money running data centers: Focus on your customers, not infrastructure.
- Go global in minutes: Deploy apps in multiple regions around the world with a few clicks.
AWS Global Infrastructure Components
Regions
A Region is a physical location in the world where AWS has multiple Availability Zones. Regions are geographically isolated to ensure fault tolerance and stability.
Availability Zones (AZs)
An AZ consists of one or more discrete data centers, each with redundant power, networking, and connectivity, housed in separate facilities. AZs are connected via high-speed, low-latency private fiber optic networking.
Edge Locations
Edge Locations are endpoints for AWS used for caching content. Typically, this relates to CloudFront (CDN) and Route 53 (DNS) to reduce latency to end-users.
| Feature | Region | Availability Zone (AZ) | Edge Location |
|---|---|---|---|
| Primary Purpose | Data Sovereignty & Latency | High Availability & Fault Tolerance | Content Delivery & Low Latency |
| Composition | Cluster of AZs | One or more Data Centers | Points of Presence (PoP) |
| Scope | Global/Geographic | Regional/Local | Global/User-proximate |
The Shared Responsibility Model
This is a foundational concept for the SAA-C03 exam. It defines what AWS manages vs. what the Customer manages.
- AWS (Security OF the Cloud): Infrastructure, hardware, software, networking, and facilities.
- Customer (Security IN the Cloud): Data encryption, OS patching (EC2), IAM, Network traffic security (Security Groups).
Decision Matrix / If–Then Guide
- IF you need to comply with legal data residency requirements… THEN choose a specific Region.
- IF you need protection against a single data center failure… THEN deploy across multiple AZs.
- IF you need to serve static assets to global users with minimum latency… THEN use Edge Locations (CloudFront).
- IF you want to manage AWS resources via scripts… THEN use the AWS CLI or SDKs.
Exam Tips and Gotchas
- Distractor Alert: An AZ is NOT a single data center; it is one or more data centers.
- Region Selection: Always choose a region based on 1. Compliance, 2. Proximity (Latency), 3. Feature Availability, and 4. Cost.
- IAM is Global: Remember that IAM users, groups, and roles are global, not region-specific.
- S3 is Global: S3 has a global namespace, but the buckets themselves are created within a specific region.
Topics covered :
Summary of key subtopics covered in this guide:
- Cloud Computing Advantages
- AWS Regions vs. Availability Zones
- Edge Locations and Content Delivery
- Shared Responsibility Model
- AWS Management Tools (Console, CLI, SDK)
- Selection criteria for Regions
AWS Global Infrastructure Visualization
Shared Responsibility
AWS: Physical security, Host OS, Hypervisor.
You: Guest OS, App code, Data encryption, IAM policies.
Global Reach
Leverage CloudFront at Edge Locations to cache static/dynamic content closer to your users, reducing TTFB (Time to First Byte).
Pay-As-You-Go
Avoid over-provisioning. Use Auto Scaling to match supply with demand and use Cost Explorer to monitor trends.
Production Use Case
Scenario: A streaming service needs to deliver video globally with 99.99% availability.
Solution: Store master files in S3 (Regional), use EC2 in an Auto Scaling Group across 3 AZs for processing, and use CloudFront (Edge Locations) to cache video segments for users worldwide.