AWS Global Infrastructure
AWS Global Infrastructure
Section titled “AWS Global Infrastructure”AWS operates one of the largest cloud infrastructures in the world, spread across geographic regions with built-in redundancy and low-latency connectivity.
Regions
Section titled “Regions”A Region is a separate geographic area where AWS clusters its data centers. Each region is fully independent — resources in one region do not automatically replicate to another.
- AWS has 35+ regions worldwide (and growing)
- Common regions:
us-east-1(N. Virginia),eu-west-1(Ireland),ap-southeast-1(Singapore) - Region codes follow the pattern:
<area>-<direction>-<number>(e.g.,us-east-1)
How to Choose a Region
Section titled “How to Choose a Region”| Factor | Guidance |
|---|---|
| Latency | Pick the region closest to your users |
| Compliance | Data residency laws may require a specific region |
| Service availability | Not all services are available in all regions |
| Cost | Prices vary slightly by region |
Availability Zones (AZs)
Section titled “Availability Zones (AZs)”Each AWS Region contains multiple Availability Zones. An AZ is one or more discrete data centers with independent power, cooling, and networking.
- Most regions have 3–6 AZs
- AZs in a region are interconnected with high-bandwidth, low-latency fiber
- AZ names:
us-east-1a,us-east-1b,us-east-1c
Why it matters: Distributing your resources across multiple AZs provides high availability and fault tolerance. If one AZ fails, your application continues running in the others.
In Azure terms: AZ ≈ Azure Availability Zone. Azure’s regions also have 3 zones in most regions.
Edge Locations
Section titled “Edge Locations”Edge Locations are data centers used by CloudFront (AWS CDN) and other services to cache content closer to end users. They are NOT full regions.
- 400+ edge locations globally
- Also used by: Route 53, AWS Shield, Lambda@Edge, AWS WAF
- Reduces latency for users by serving cached responses locally
Local Zones
Section titled “Local Zones”Local Zones extend an AWS Region to more geographic areas, placing compute, storage, and database services closer to large population centers.
- Useful for applications requiring single-digit millisecond latency
- Example:
us-east-1-bos-1(Boston Local Zone extending us-east-1)
Wavelength Zones
Section titled “Wavelength Zones”Wavelength Zones embed AWS compute and storage services within telecom providers’ 5G networks, enabling ultra-low latency for mobile applications.
AWS Outposts
Section titled “AWS Outposts”AWS Outposts brings AWS infrastructure, services, APIs, and tools to virtually any on-premises or edge location. Essentially AWS hardware deployed in your own data center.
Global Infrastructure Summary
Section titled “Global Infrastructure Summary”| Component | Description | Count (approx.) |
|---|---|---|
| Regions | Fully independent geographic areas | 35+ |
| Availability Zones | Isolated data centers within a region | 100+ |
| Edge Locations | CDN/Route53/WAF endpoints | 400+ |
| Local Zones | Extended compute near metro areas | 30+ |
| Wavelength Zones | 5G embedded compute | Multiple |
High Availability Design Principles
Section titled “High Availability Design Principles”- Deploy across multiple AZs — Use multi-AZ for databases, load balancers, and auto-scaling groups
- Use managed services — RDS Multi-AZ, S3 (11 nines durability), DynamoDB Global Tables
- Design for failure — Assume any single component can fail
- Use health checks and auto-healing — ELB health checks, ASG replacement
- Consider multi-region for disaster recovery if RTO/RPO requires it
Comparison: AWS vs Azure Global Infrastructure
Section titled “Comparison: AWS vs Azure Global Infrastructure”| Concept | AWS | Azure |
|---|---|---|
| Independent area | Region | Region |
| Isolated data centers | Availability Zone | Availability Zone |
| CDN endpoints | Edge Location | Azure CDN POP |
| On-prem extension | AWS Outposts | Azure Stack Hub |
| Metro low-latency extension | Local Zone | Azure Edge Zone |