# AWS global infrastructure

AWS global infrastructure is the worldwide arrangement of Regions, Availability Zones, and edge locations that provides the physical foundation for deploying and delivering cloud workloads.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/aws-global-infrastructure

> This infrastructure lets engineers choose where applications run, how they tolerate failures, and how closely they serve users. Understanding its geographic and operational boundaries is essential for designing availability, latency, disaster recovery, and data residency controls.

Practice exams covering AWS global infrastructure: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of AWS global infrastructure

AWS global infrastructure provides geographic placement, isolated failure boundaries, and edge delivery options whose benefits depend on deliberate workload architecture.

1. **Geographic placement through Regions**: Choose a Region according to latency, legal requirements, service availability, and cost. Treat deployment into another Region as an explicit architectural decision rather than an automatic platform behavior.
2. **Availability Zone failure isolation**: Spread critical components across Availability Zones to reduce exposure to a localized failure. Verify that routing, data access, network dependencies, and surviving capacity support continued operation.
3. **Edge-based delivery and connectivity**: Use edge infrastructure to cache eligible content or improve traffic paths for distributed users. Edge delivery complements an origin deployment; it does not automatically replace or replicate the application.
4. **Resource scope and placement boundaries**: Identify whether each resource is zonal, regional, or global before designing dependencies. A globally accessible endpoint does not imply that its backend resources operate across multiple Regions.
5. **Explicit cross-Region recovery**: Plan replication, failover, capacity, and recovery procedures when regional disruption must be covered. Test recovery against defined recovery time and recovery point objectives.
6. **Latency, cost, and residency trade-offs**: Evaluate network distance, data transfer charges, duplicate capacity, and operational complexity together. Include replicas, backups, logs, and caching behavior when assessing data location requirements.

## Cloud services for AWS global infrastructure

EC2 and RDS place application compute and relational data within regional and zonal boundaries, while S3 provides regional object storage with storage-class-specific resilience. CloudFront adds edge caching and delivery for suitable content. Route 53 directs clients through DNS, while Global Accelerator offers a global network entry point for supported endpoints. Together, these services can support a Multi-AZ application or a multi-Region design, but geographic reach alone does not establish resilience. Engineers must coordinate data replication, endpoint health, surviving capacity, and recovery procedures, then test the behavior of the complete application during failures.

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: EC2 instances are placed in a specific Availability Zone within a Region. Deploying instances across zones supports availability, but sufficient capacity and resilient application dependencies remain necessary.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Supported RDS Multi-AZ configurations use multiple Availability Zones for database availability and failover. Cross-Region replication or recovery requires separate supported mechanisms; Multi-AZ alone does not protect against a regional disruption.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: S3 general purpose buckets are created in a selected Region, and most S3 storage classes store data across multiple Availability Zones. Single-zone storage classes have different resilience characteristics, while Cross-Region Replication must be configured explicitly.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: CloudFront uses globally distributed edge locations to deliver content and cache eligible responses closer to viewers. Origin placement, cache policy, and origin failover configuration determine how it contributes to latency and availability.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Route 53 provides DNS routing policies that can direct clients toward regional application endpoints. Health-check-based routing can support failover, but DNS caching and application readiness affect recovery behavior.
- **[AWS Global Accelerator](https://blowstack.com/tools/cloud-services-hub/aws-global-accelerator)**: Global Accelerator provides static anycast IP addresses and routes supported application traffic through the AWS global network to regional endpoints. It can direct traffic according to endpoint health, but does not replicate application state or create recovery capacity.

## AWS global infrastructure exam questions

Real practice exam questions on AWS global infrastructure, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

An online publisher operates its website in one AWS Region and uses Amazon CloudFront. When the publisher expands into new countries, readers receive website images from nearby AWS edge locations. The publisher does not deploy additional copies of its application in those countries. Which AWS Cloud benefit does this scenario demonstrate MOST directly?

**Correct answer:** Global reach that brings content closer to users without deploying application servers in each market

**Explanation:** CloudFront uses the AWS global network of edge locations to deliver content near users. This helps organizations serve international audiences with lower latency without deploying their application in every country.

### Question 2 (SAA-C03)

**Question:**

A company runs a data-serving application on Amazon EC2 in Account A. Processing workers in Account B exchange several terabytes of data each day with this application over private IP addresses through an existing same-Region VPC peering connection. The data-serving instances must remain in their current Availability Zone. The workers can be recreated after an Availability Zone outage and do not require Multi-AZ availability.

The accounts have the following Availability Zone mappings:

| Account | Availability Zone name | Availability Zone ID |
|---|---|---|
| A | us-east-1a | use1-az2 |
| B | us-east-1a | use1-az4 |
| B | us-east-1b | use1-az2 |
| B | us-east-1c | use1-az6 |

The data-serving instances run in Account A's us-east-1a. All candidate worker deployments use the same number and type of EC2 instances at identical hourly prices. No NAT gateways or other network appliances are involved.

Which worker placement will minimize EC2 data transfer costs?

**Correct answer:** Place all workers in Account B's us-east-1b to match the Availability Zone ID used by the data-serving instances.

**Explanation:** Availability Zone IDs identify the same physical zone across accounts. Both deployments would be in use1-az2. EC2 traffic over private IP addresses through same-Region VPC peering has no data transfer charge when the instances are in the same Availability Zone, even across accounts.

### Question 3 (DOP-C02)

**Question:**

A company operates a stateless HTTPS calculation API in us-west-2. An Application Load Balancer (ALB) routes requests to EC2 instances across three Availability Zones. Each instance contains all application code and reference data needed to process requests without external dependencies.

The company requires service to resume within 5 minutes after a complete outage of us-west-2, without provisioning resources during the outage. All processing must remain in the United States. Clients retry failed requests, refresh DNS within 60 seconds, and establish new connections after refreshing DNS. Regional readiness checks and traffic redirection have been tested to complete within the remaining recovery budget.

A DevOps engineer must select a deployment topology that provides the required failure isolation. Which design meets these requirements?

**Correct answer:** Deploy a full-capacity EC2 pool across multiple Availability Zones in us-east-2 behind a separate ALB in us-east-2. Configure Amazon Route 53 failover records with readiness health checks for the two regional endpoints.

**Explanation:** The second deployment has its own regional application capacity and ingress endpoint in a separate US Region. It does not require us-west-2 to serve requests or provision recovery resources. Given the validated readiness checks, DNS refresh behavior, and connection retries, this topology supports the 5-minute recovery requirement.

## Practice AWS global infrastructure in a full exam

Questions on AWS global infrastructure in each practice exam, with every answer option and an explanation for each:

- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 45 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 28 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 4 questions

## What is AWS global infrastructure

AWS global infrastructure organizes cloud resources into geographic deployment areas and distinct failure boundaries. Its main building blocks are Regions, Availability Zones, and edge locations. These are not interchangeable: Regions establish geographic placement, Availability Zones support isolation within a Region, and edge locations bring selected delivery and networking functions closer to users.

A Region is a separate geographic area containing multiple Availability Zones. Engineers select Regions based on user proximity, service availability, pricing, regulatory requirements, and recovery objectives. Most workload resources are regional or zonal rather than automatically worldwide. Launching an application in one Region does not create a working copy in another Region, and service capabilities can differ between Regions.

An Availability Zone consists of one or more discrete data centers with redundant power, networking, and connectivity. Availability Zones within a Region are physically separated and connected through low-latency networking. This arrangement supports architectures that remain available when one zone becomes unavailable. However, placing resources in multiple zones is only useful when application routing, capacity, storage, and dependencies can also withstand a zone failure.

For example, a regional web application might use a load balancer with application instances in two Availability Zones and a database configured for supported Multi-AZ operation. If one zone fails, the surviving application tier must have enough capacity to handle traffic, and database failover must fit the application's recovery requirements. Two instances in different zones do not provide complete resilience if both depend on a single zonal database or outbound networking component.

Edge locations support services such as content delivery and traffic acceleration. A content delivery network can cache eligible content near users, reducing latency and requests to the origin. An edge location is not an Availability Zone and does not provide the same general-purpose deployment environment. Local Zones are another distinct extension: they place selected resources closer to particular population or industry centers while remaining associated with a parent Region.

Multi-Region architecture addresses broader disruptions and can improve proximity to geographically distributed users. A disaster recovery design might replicate data to a second Region and maintain infrastructure definitions that can recreate the application there. Recovery depends on replication lag, available capacity, routing changes, credentials, and operational readiness. Active-active deployment can reduce reliance on a single Region, but it introduces harder problems involving concurrent writes, consistency, conflict resolution, and coordinated releases.

The trade-offs are practical rather than purely geographic. Cross-zone and cross-Region communication can introduce transfer charges, while longer network distances increase latency. Additional deployment locations increase operational complexity and can require duplicate capacity. Teams should define recovery time and recovery point objectives before choosing between a single-Region Multi-AZ design, standby recovery, and active-active deployment.

Common misconceptions include assuming that every AWS service is regional, that all storage automatically replicates across Regions, or that using a global endpoint makes an application resilient to regional failures. Some services have global scope or global entry points, but their dependencies and recovery behavior still require inspection. For data residency, selecting a Region is only part of the design: backups, replicas, logs, edge caching, and service-specific data handling must also match the applicable requirements.

## Learn AWS global infrastructure in lessons

5 short lessons on AWS global infrastructure in 3 certification courses.

- CLF-C02: AWS global infrastructure: Regions, Availability Zones, and edge locations (Premium), https://app.blowstack.com/lessons/aws-global-infrastructure-regions-availability-zones-and-edge-locations-clf-c02
- SAA-C03: AWS global infrastructure: deployment scope (Premium), https://app.blowstack.com/lessons/aws-global-infrastructure-deployment-scope-saa-c03
- DOP-C02: AWS global infrastructure: zonal and regional failure boundaries (free), https://app.blowstack.com/lessons/aws-global-infrastructure-zonal-and-regional-failure-boundaries-dop-c02
- CLF-C02: AWS global infrastructure: Regional workload placement (Premium), https://app.blowstack.com/lessons/aws-global-infrastructure-regional-workload-placement-clf-c02
- CLF-C02: AWS global infrastructure: Availability Zone isolation (Premium), https://app.blowstack.com/lessons/aws-global-infrastructure-availability-zone-isolation-clf-c02
