This chapter covers AWS Wavelength and AWS Local Zones — two services that extend AWS infrastructure closer to end users to reduce latency. For the CLF-C02 exam, this objective falls under Cloud Technology Services (Domain 3, approximately 24% of the exam). Understanding when to use Wavelength vs. Local Zones, and how they differ from standard AWS Regions and edge locations, is essential for scenario-based questions. You will learn the architecture, use cases, and key distinctions that the exam tests.
Jump to a section
Imagine you run a chain of coffee shops. Your main roasting facility is in a large city center, serving all your shops. For a big music festival in a remote park, you want to sell fresh coffee. Shipping from your city roastery takes too long, and the coffee gets cold. So you set up a small, temporary roasting unit inside a food truck parked right at the festival. This truck connects to the festival's power grid (local infrastructure) and uses your central supply chain for beans (core network). The coffee is freshly roasted within milliseconds of the order. That's AWS Wavelength: embedding compute and storage at the edge of a 5G carrier network to serve ultra-low-latency applications. Now, for customers who live just outside the city but still far from your roastery, you open a small permanent satellite roastery in their suburb. It's not as fast as the truck at the festival, but it's much faster than shipping from the city. That's AWS Local Zones: placing AWS infrastructure closer to a population center to reduce latency for latency-sensitive workloads that don't need 5G edge. Both extend your reach, but one is for extreme low latency at the carrier edge, the other for moderate latency reduction in a metro area.
What Are AWS Wavelength and Local Zones?
AWS Wavelength and AWS Local Zones are both AWS infrastructure deployment options that bring compute and storage closer to end users. They address the problem of latency — the time it takes for data to travel between a user and the cloud. Standard AWS Regions can be hundreds or thousands of miles away, causing delays that break real-time applications like gaming, live video, and IoT control.
AWS Wavelength embeds AWS compute and storage services at the edge of 5G telecommunications networks, inside or adjacent to carrier data centers. This allows application traffic to reach AWS services from a mobile device over the 5G network with single-digit millisecond latency, without leaving the carrier's network.
AWS Local Zones are small, geographically isolated extensions of an AWS Region placed in or near large metropolitan areas. They provide low-latency access to a subset of AWS services for workloads that need to be close to a specific population center, but not necessarily at the 5G edge.
How They Work — Mechanism
Wavelength Zones - AWS installs compute and storage hardware inside a telecommunications provider's data center (e.g., Verizon, Vodafone). - The Wavelength Zone is logically part of an AWS Region — you can create VPCs that extend into the zone, but the physical hardware is at the carrier edge. - Traffic from a 5G device goes to the carrier's network, hits the Wavelength Zone directly (no backhaul to the Region), and returns — all within 1-5 ms. - Services available: Amazon EC2, Amazon EBS, Amazon VPC, AWS Lambda, Amazon ECS, Amazon EKS, and others. Not all AWS services are available. - You must use a carrier partner that supports Wavelength in that location.
Local Zones - AWS builds a small data center facility in a metro area, connected to the parent Region via a dedicated, high-bandwidth link. - The Local Zone is an extension of the VPC in the parent Region. You launch resources (EC2, EBS, RDS, etc.) directly in the Local Zone subnet. - Traffic between the Local Zone and the parent Region incurs standard inter-AZ data transfer charges. - Services available: a broader set than Wavelength, including EC2, EBS, RDS, ELB, ECS, EKS, Lambda, and more. Still not all services. - No carrier partnership required — any internet user can use Local Zones.
Key Tiers, Configurations, and Pricing
Wavelength - Pricing: You pay for the AWS resources you use (EC2 instances, EBS volumes, data transfer) plus any carrier charges for 5G connectivity. - Data transfer: Data within the Wavelength Zone is free; data transferred to the parent Region or internet is charged at standard rates. - Limits: You must request a quota increase for Wavelength Zone resources. Default limits are low (e.g., 5 instances per zone). - Availability: As of 2025, Wavelength Zones are available in select US cities (e.g., Boston, Dallas, Las Vegas) and internationally (e.g., London, Tokyo, Seoul).
Local Zones - Pricing: Standard EC2, EBS, and data transfer rates apply. No additional fee for the Local Zone itself. - Data transfer: Data transfer between Local Zone and parent Region is charged at inter-AZ rates (currently $0.01/GB). - Limits: You must opt-in to Local Zones. Default VPC and resource limits apply. - Availability: Over 30 Local Zones worldwide, including Los Angeles, Miami, New York City, Paris, Sydney, and more.
Comparison to On-Premises or Competing Approaches
On-premises edge - You could deploy your own servers at a carrier facility or metro colo. This gives full control but requires capital expenditure, operational overhead, and long procurement cycles. - AWS Wavelength and Local Zones shift the burden to AWS — you pay only for what you use and can scale instantly.
Content Delivery Networks (CDN) - Amazon CloudFront caches static and dynamic content at edge locations (400+ points of presence). This is great for web content but does not allow running compute logic at the edge. - Wavelength and Local Zones allow you to run full application logic (e.g., game servers, inference models) at the edge.
Standard Regions with multiple AZs - Using multiple Availability Zones within a Region reduces latency for users near the Region but does not help users far away. - Wavelength and Local Zones place compute physically closer to users, reducing latency beyond what AZs can achieve.
When to Use Wavelength vs. Local Zones
Use Wavelength when: - Your application requires single-digit millisecond latency over a 5G network. - Use cases: real-time gaming, live video processing, autonomous vehicle control, industrial IoT, AR/VR. - Your end users are mobile and connect via a 5G carrier partner.
Use Local Zones when: - Your application requires low latency (10-20 ms) but does not need 5G edge. - Use cases: media and entertainment (live streaming), real-time analytics, database workloads, machine learning inference. - Your users are concentrated in a metro area far from the nearest Region.
Exam tip: The CLF-C02 exam will test the primary difference: Wavelength is for 5G edge (carrier network), Local Zones are for metro edge (closer to population centers but not carrier-integrated).
Identify Latency Requirements
First, determine the latency tolerance of your application. If your application needs end-to-end latency under 10 milliseconds and your users are on 5G mobile networks, Wavelength is the candidate. If latency tolerance is 10-20 ms and users are in a specific metro area, consider Local Zones. For standard cloud workloads, a regular Region with multiple AZs suffices. Document the user location and network type — this drives the decision.
Check Service Availability
Not all AWS services are available in Wavelength Zones or Local Zones. For Wavelength, available services include EC2, EBS, VPC, Lambda, ECS, and EKS, but not RDS, DynamoDB, or S3. For Local Zones, a broader set is available including RDS, but still not all (e.g., S3 is not available in Local Zones as of 2025). Check the AWS Regional Services list for the specific zone. If your application requires a service not available, you may need to architect with the parent Region for those components.
Opt-In and Provision Infrastructure
For Wavelength, you must work with a carrier partner (e.g., Verizon, Vodafone) to get access to the Wavelength Zone. For Local Zones, you opt-in via the AWS Management Console (EC2 > Settings > Zones). Once opted in, you create a VPC subnet in the zone. For Wavelength, you create a subnet in the Wavelength Zone and configure carrier gateway for 5G traffic. For Local Zones, you create a subnet and route traffic as usual. Launch your EC2 instances, EBS volumes, and other resources into the subnet.
Deploy and Test Application
Deploy your application (e.g., game server, video transcoder) onto the EC2 instances in the zone. For Wavelength, ensure your application is reachable via the 5G carrier network — you may need to configure security groups and network ACLs to allow traffic from the carrier gateway. For Local Zones, test latency from end-user devices using tools like ping or traceroute. Monitor CloudWatch metrics for latency and resource utilization. Adjust instance types and scaling as needed.
Manage Data Transfer Costs
Data transfer between Wavelength/Local Zone and the parent Region incurs charges. For Wavelength, data transfer to the internet via the carrier gateway may have carrier charges. For Local Zones, inter-zone transfer costs apply. Use CloudWatch and Cost Explorer to monitor data transfer. Consider caching frequently accessed data in the zone to reduce cross-region traffic. For Wavelength, minimize egress to the internet by processing data locally.
Scenario 1: Real-Time Mobile Gaming A game developer creates a multiplayer first-person shooter for mobile phones. Players are on 5G networks in major cities. The game requires sub-10ms latency for a smooth experience. The team deploys game server logic on EC2 instances in a Wavelength Zone co-located with Verizon's 5G network in New York City. Player traffic from 5G devices hits the Wavelength Zone directly, bypassing the internet. The game uses Amazon EBS for state persistence and Lambda for matchmaking. Cost: EC2 instance costs are standard, plus Verizon data charges. Misconfiguration: If the team mistakenly deploys in a Local Zone instead, latency increases by 10-15ms because traffic must traverse the internet to the Local Zone, causing lag and player churn.
Scenario 2: Live Video Production A media company produces live sports events from a stadium in Los Angeles. They need to ingest camera feeds, apply real-time graphics, and stream to viewers with under 20ms latency. The nearest AWS Region (us-west-2) is in Oregon, ~900 miles away. They deploy video processing pipelines on EC2 G4dn instances in the Los Angeles Local Zone. AWS Elemental MediaLive runs in the Local Zone for low-latency encoding. The processed stream is sent to CloudFront for distribution. Cost: Local Zone instance pricing is the same as us-west-2, but inter-zone data transfer to the parent Region for backup adds cost. Failure: If they use a standard Region, latency exceeds 50ms, causing noticeable delay between action and broadcast.
Scenario 3: Autonomous Vehicle Fleet An autonomous vehicle company operates a fleet of taxis in a city. Each car generates terabytes of sensor data daily and needs near-real-time inference for obstacle detection. They deploy machine learning inference models on EC2 Inf1 instances in a Wavelength Zone. The 5G link from the car to the zone provides sub-5ms latency, enabling real-time decision-making. AWS IoT Greengrass runs on the vehicle for local processing, with Wavelength as a fallback. Cost: High data transfer costs if raw data is sent to the parent Region. Optimization: Process data in the Wavelength Zone, send only metadata to the Region. Pitfall: If the Wavelength Zone is not available in the city, they must rely on on-premises servers or a Local Zone, increasing latency and complexity.
What CLF-C02 Tests The exam tests your understanding of the purpose and differences between AWS Wavelength and AWS Local Zones under Domain 3 (Cloud Technology Services). You will not be asked to configure them, but you must know:
The primary use case for each (Wavelength = 5G ultra-low latency; Local Zones = metro low latency).
Which services are available (not all, and the exam may list services that are NOT available in these zones).
The relationship to AWS Regions (both are extensions of a parent Region).
The difference between these and edge locations (CloudFront) or standard AZs.
Common Wrong Answers and Why 1. "Wavelength is for any application that needs low latency." — Wrong: Wavelength specifically requires a 5G carrier network. For non-5G users, Local Zones or CloudFront are more appropriate. 2. "Local Zones are the same as Availability Zones." — Wrong: AZs are within a Region and provide high availability, not geographic proximity to users. Local Zones are separate facilities in metro areas. 3. "You can use any AWS service in Wavelength Zones." — Wrong: Only a subset is available; the exam may list S3 or DynamoDB as distractors. 4. "Wavelength and Local Zones are independent of Regions." — Wrong: They are extensions of a parent Region and rely on it for control plane and some services.
Specific Terms and Values - "Single-digit millisecond latency" is the key phrase for Wavelength. - "5G carrier edge" vs. "metro area" distinction. - "Carrier gateway" is the VPC component for Wavelength traffic. - "Opt-in" is required for Local Zones.
Tricky Distinctions - AWS Outposts: a fully managed, customer-owned hardware rack that runs AWS services on-premises. Unlike Wavelength/Local Zones, Outposts are physically on customer premises. - CloudFront edge locations: cache content, do not run compute (unless using Lambda@Edge).
Decision Rule If the question mentions "5G" or "mobile carrier network," choose Wavelength. If it mentions "metro area" or "population center" without 5G, choose Local Zones. If it mentions "on-premises" or "customer data center," choose Outposts.
AWS Wavelength embeds compute and storage at the edge of 5G carrier networks for single-digit millisecond latency.
AWS Local Zones extend a Region to metro areas for low-latency workloads that do not require 5G.
Both Wavelength and Local Zones are extensions of a parent Region, not standalone Regions.
Only a subset of AWS services is available in Wavelength and Local Zones; always verify service availability.
Wavelength requires a carrier partnership and is used for real-time gaming, AR/VR, and IoT.
Local Zones are used for media processing, real-time analytics, and database workloads in metro areas.
Data transfer between Wavelength/Local Zone and parent Region incurs standard inter-AZ charges.
These come up on the exam all the time. Here's how to tell them apart.
AWS Wavelength
Designed for ultra-low latency over 5G (1-5 ms)
Compute and storage inside carrier 5G data centers
Requires carrier partnership (e.g., Verizon, Vodafone)
Subset of services: EC2, EBS, VPC, Lambda, ECS, EKS
Traffic stays within carrier network, no internet backhaul
AWS Local Zones
Designed for low latency in metro areas (10-20 ms)
Compute and storage in AWS-managed metro facilities
No carrier required, any internet user can access
Broader service set: EC2, EBS, RDS, ELB, Lambda, etc.
Traffic may traverse internet or dedicated link to parent Region
AWS Local Zones
AWS-owned infrastructure in metro areas
Extension of a parent Region, managed by AWS
No upfront cost, pay-as-you-go
Subset of services, but growing
Ideal for latency-sensitive workloads near users
AWS Outposts
Customer-owned hardware in customer data center
Fully managed by AWS but physically on customer premises
Upfront hardware cost or long-term commitment
Supports a broad set of services, including some that require local data residency
Ideal for on-premises workloads that need low latency to on-prem systems
Mistake
Wavelength Zones are just like Availability Zones but closer to users.
Correct
Wavelength Zones are physically located inside carrier 5G data centers, not in AWS data centers. They are extensions of a parent Region but have different connectivity and service availability.
Mistake
Local Zones provide the same latency as Wavelength Zones.
Correct
Local Zones reduce latency compared to a standard Region but still involve internet or dedicated link latency (10-20 ms). Wavelength achieves sub-10 ms by staying within the carrier 5G network.
Mistake
All AWS services are available in Wavelength and Local Zones.
Correct
Only a subset of services is available. For example, S3, DynamoDB, and RDS are not available in Wavelength Zones. Local Zones have a broader set but still miss some services.
Mistake
Wavelength and Local Zones are standalone Regions.
Correct
They are not Regions. They are extensions of a parent AWS Region and depend on it for management and some services. You cannot create an independent account in a Wavelength or Local Zone.
Mistake
You can use Wavelength without a 5G carrier partnership.
Correct
Wavelength requires a carrier partner (e.g., Verizon, Vodafone). Without a carrier, you cannot access the Wavelength Zone. Local Zones do not require a carrier.
AWS Wavelength is designed for ultra-low latency applications that require single-digit millisecond latency over a 5G network. It places compute and storage inside a carrier's 5G data center. AWS Local Zones are for low-latency workloads in metro areas, reducing latency compared to a standard Region but not to the same extreme. Wavelength requires a 5G carrier partnership; Local Zones do not. For the exam, remember: Wavelength = 5G edge; Local Zones = metro edge.
No, Amazon S3 is not available in Wavelength Zones as of 2025. Wavelength Zones support a limited set of services: EC2, EBS, VPC, Lambda, ECS, EKS, and a few others. For storage, you can use EBS volumes attached to EC2 instances. If you need object storage, you must use the parent Region's S3, which will incur higher latency. The exam may test this limitation.
Yes, to use AWS Wavelength, you must have a partnership or subscription with a supported carrier (e.g., Verizon in the US, Vodafone in Europe). The carrier provides the 5G network connectivity. AWS does not directly provide the 5G link. This is a key distinction from Local Zones, which require no carrier involvement.
Data transfer between a Local Zone and its parent Region is charged at the same rate as inter-Availability Zone data transfer within a Region (currently $0.01/GB for most Regions). This is important for cost management if your application frequently moves data between the Local Zone and the Region. For Wavelength, data transfer to the parent Region is also charged at standard rates.
Yes, Amazon RDS is available in many Local Zones. This allows you to run databases with low latency for applications in that metro area. However, not all Local Zones support RDS; check the AWS documentation for the specific zone. RDS is not available in Wavelength Zones.
You must route traffic to the parent Region for those services. This will increase latency. For example, if you need DynamoDB, you would call the DynamoDB endpoint in the parent Region. The extra latency may defeat the purpose of using Wavelength. The exam may ask you to identify which services are available locally.
Yes, both are part of the AWS Global Infrastructure. They are categorized under 'Edge' locations, but they are distinct from CloudFront edge locations. AWS defines three types of edge: CloudFront (content delivery), Wavelength (5G edge), and Local Zones (metro edge). The exam may ask you to categorize them.
You've just covered AWS Wavelength and Local Zones — now see how well it sticks with free CLF-C02 practice questions. Full explanations included, no account needed.
Done with this chapter?