This chapter covers AWS Wavelength and Local Zones — edge infrastructure that extends AWS Regions closer to end users and devices. For the SAA-C03 exam, these services appear in questions about low-latency, high-bandwidth applications, especially those involving 5G, IoT, and real-time media processing. While not a major topic area (likely 1-2 questions), understanding the architectural differences, use cases, and limitations is critical to avoid wrong answers that confuse these with other edge services like Outposts or CloudFront.
Jump to a section
Imagine a nationwide retail chain with a central distribution center (the AWS Region) and hundreds of local warehouses (Wavelength Zones and Local Zones). Without local warehouses, every customer order must be shipped from the central center, taking days and costing more. With local warehouses, high-demand items are pre-stocked close to customers — orders from nearby customers are fulfilled in hours instead of days. However, the local warehouse is still connected to the central center for inventory management, restocking, and rare items. The local warehouse doesn't replace the central center; it complements it by reducing latency and bandwidth costs for time-sensitive, high-volume items. Similarly, AWS Wavelength Zones and Local Zones bring compute and storage closer to end users, reducing latency for applications like 5G, IoT, and real-time gaming. They are physically separate but logically connected to the parent Region via AWS backbone, enabling low-latency local processing while still leveraging central services for management and less latency-sensitive workloads.
What AWS Wavelength and Local Zones Are and Why They Exist
AWS Wavelength and Local Zones are two distinct edge computing services that extend AWS infrastructure closer to end users. The core problem they solve is latency: for applications requiring single-digit millisecond response times, the physical distance between the user and the AWS Region introduces unacceptable delay. Light travels about 1 millisecond per 200 km in fiber, so a user 1000 km from a Region experiences at least 5 ms of one-way latency, plus processing and queuing delays. For 5G applications (e.g., autonomous vehicle coordination, industrial robotics), sub-10ms round-trip latency is mandatory.
Wavelength Zones are AWS infrastructure deployments embedded within telecommunications providers' data centers at the edge of 5G networks. They are designed specifically for mobile 5G applications. Each Wavelength Zone is connected to the parent AWS Region via the AWS backbone and is logically part of the Region's VPC. The key differentiator is that Wavelength Zones provide ultra-low latency to 5G devices by placing compute and storage right at the carrier's aggregation point — often within 1-2 ms of the radio access network (RAN).
Local Zones are AWS infrastructure deployments in metropolitan areas that are not served by a full AWS Region. They are designed for a broader set of latency-sensitive applications, including media and entertainment, real-time gaming, and enterprise migration. Local Zones are typically 100-200 km from the parent Region and provide single-digit millisecond latency for end users in that metro area. They support a wider range of AWS services than Wavelength Zones (e.g., EC2, EBS, RDS, EKS, ELB) and are managed as extensions of the parent Region's VPC.
How They Work Internally
Both Wavelength and Local Zones are connected to the parent Region via redundant, high-bandwidth AWS backbone links. They are not independent Regions; they are extensions of the Region. Resources created in a Wavelength or Local Zone use the same VPC, subnets, security groups, and IAM policies as the parent Region. However, the physical infrastructure is located in a separate facility.
For Wavelength Zones, the carrier's 5G core network routes traffic to the Wavelength Zone via a local breakout. When a 5G device sends a packet, the carrier's user plane function (UPF) intercepts it and forwards it to the Wavelength Zone's compute instances if the destination IP is within the Wavelength Zone's subnet. This avoids backhauling traffic to the carrier's central data center or the public internet, achieving sub-10ms round-trip latency. The Wavelength Zone runs a specific set of services: EC2, EBS, VPC, and Elastic Load Balancing. Services like S3, DynamoDB, or Lambda are not available directly in the Wavelength Zone; they must be accessed via the parent Region, which adds latency.
For Local Zones, the architecture is similar but not tied to a carrier's 5G network. Local Zones are connected to the parent Region via AWS Direct Connect or the AWS backbone. Traffic from end users (e.g., over the internet) enters the Local Zone via an internet gateway attached to the Local Zone's subnet. The Local Zone supports a broader set of services, including EC2, EBS, RDS, EKS, ELB, and even some container services. However, services like S3, DynamoDB, Lambda, and API Gateway are not available locally; they must be accessed from the parent Region, incurring cross-AZ latency.
Key Components, Values, Defaults, and Timers
Latency targets: Wavelength Zones aim for sub-10ms round-trip from 5G devices; Local Zones aim for single-digit milliseconds from the metro area.
Service availability: Wavelength Zones support a limited subset: EC2 (C5, M5, R5, G4dn instances), EBS (gp2, io1), VPC (subnets, security groups, network ACLs), ELB (NLB, ALB). Local Zones support: EC2 (C5, M5, R5, T3, G4dn, I3en), EBS (gp2, gp3, io1, io2, sc1, st1), RDS (Aurora, MySQL, PostgreSQL, Oracle, SQL Server), EKS, ELB (NLB, ALB), and others. Always check the latest documentation for current service lists.
Parent Region: Each Wavelength/Local Zone is associated with exactly one parent Region. For example, the Wavelength Zone in Boston is associated with the us-east-1 Region. Resources in the zone are billed as part of that Region.
Subnet isolation: Subnets in a Wavelength/Local Zone cannot span across zones; they are tied to that specific zone. You must create separate subnets for the edge zone.
Pricing: Data transfer between the edge zone and the parent Region is billed at inter-AZ rates (typically $0.01-$0.02/GB each way). Data transfer from the edge zone to the internet is billed at internet egress rates of the parent Region.
Capacity: Wavelength and Local Zones have limited capacity compared to full Regions. You may need to request capacity increases via AWS Support.
Limitations: Not all instance types are available. Some services (e.g., S3, DynamoDB, Lambda) are not available in the edge zone itself; you must access them from the parent Region, which adds latency. Also, edge zones do not support all features of the parent Region, such as VPC endpoints, Transit Gateway, or VPN connections directly to the edge zone (though you can connect via the parent Region).
Configuration and Verification Commands
To create resources in a Wavelength or Local Zone, you first need to enable the zone in your account via the AWS Management Console or CLI. Then, you create a VPC and subnets specifying the zone ID.
Example: Enable a Local Zone (us-east-1-nyc-1) via CLI:
aws ec2 modify-availability-zone-group --group-name us-east-1-nyc-1 --opt-in-status opted-inCreate a subnet in the Local Zone:
aws ec2 create-subnet --vpc-id vpc-12345678 --cidr-block 10.0.1.0/24 --availability-zone us-east-1-nyc-1Launch an EC2 instance in the Local Zone:
aws ec2 run-instances --image-id ami-0abcdef1234567890 --instance-type t3.micro --subnet-id subnet-12345678Verification: List subnets and their availability zones:
aws ec2 describe-subnets --filters "Name=vpc-id,Values=vpc-12345678" --query "Subnets[*].{SubnetId:SubnetId, AZ:AvailabilityZone, CIDR:CidrBlock}"Interaction with Related Technologies
VPC: Edge zones are part of your VPC. You can route traffic between the edge zone and other AZs via the VPC router. However, traffic between an edge zone and the parent Region may traverse the AWS backbone, incurring inter-AZ data transfer costs.
Elastic Load Balancing: You can deploy ALB or NLB in an edge zone to load balance traffic across instances in that zone. Cross-zone load balancing does not work across edge zones and regular AZs.
Auto Scaling: You can create Auto Scaling groups that launch instances in edge zones, but the group must be configured with the specific zone.
EBS: EBS volumes in edge zones are local to that zone. Snapshots are stored in the parent Region and incur data transfer costs.
RDS: RDS instances can be deployed in Local Zones (not Wavelength). Multi-AZ deployments are not supported within a Local Zone; you can only have a single instance. For high availability, you can use a standby in a different AZ in the parent Region, but this introduces latency.
EKS: Clusters can have worker nodes in Local Zones, but the control plane remains in the parent Region. This adds latency for control plane operations.
Direct Connect: You can use Direct Connect to connect your on-premises network to the parent Region, and then route traffic to the edge zone via the VPC. Direct Connect is not available directly in the edge zone.
VPN: VPN connections terminate at the parent Region's virtual private gateway; you cannot create a VPN directly to an edge zone.
CloudFront: CloudFront is a separate CDN service and does not use Wavelength or Local Zones. However, you can use CloudFront to cache content closer to users, while Wavelength/Local Zones provide compute near the edge.
Identify Latency Requirements
Determine the application's round-trip latency requirement. If sub-10ms is required for 5G devices, Wavelength Zones are necessary. If single-digit ms is needed for metro-area users (e.g., real-time gaming, live video processing), Local Zones may suffice. If latency tolerance is higher (10-50ms), standard AWS Regions with multiple AZs may be adequate. This step involves analyzing the physical distance to the nearest Region and the network path. For 5G, the carrier's UPF must be co-located with the Wavelength Zone.
Choose Zone and Enable
Select the appropriate Wavelength or Local Zone based on user location. For Wavelength, you must partner with a carrier that has Wavelength Zones (e.g., Verizon in the US). For Local Zones, AWS publishes a list of available zones (e.g., us-east-1-nyc-1). Enable the zone in your AWS account via the console or CLI (modify-availability-zone-group). This is a one-time operation per zone. After enabling, the zone appears as an additional availability zone in the parent Region.
Design VPC and Subnets
Create a VPC in the parent Region (or use an existing one). Add subnets specifically for the edge zone, using the zone's identifier (e.g., us-east-1-nyc-1). These subnets must have unique CIDR blocks. Configure route tables: traffic destined for the edge zone's subnets is routed locally; traffic to the parent Region or internet goes via the VPC's internet gateway or NAT gateway (which must be in the parent Region). Note that you cannot create an internet gateway directly in an edge zone; you must use the parent Region's IGW.
Deploy Resources Locally
Launch EC2 instances, create EBS volumes, set up ELB, and configure Auto Scaling groups within the edge zone subnets. Ensure you select the correct availability zone when launching. For RDS in Local Zones, create the DB subnet group including the edge zone subnet. For EKS, add node groups in the edge zone. Note that some services (e.g., Lambda, S3) are not available locally; plan to access them from the parent Region, accepting higher latency.
Configure Networking and Security
Set up security groups and network ACLs for the edge zone resources. Since the edge zone is part of the VPC, you can use the same security groups. However, be aware that traffic between the edge zone and the parent Region traverses the AWS backbone and is subject to inter-AZ data transfer costs. For high availability, consider deploying in multiple edge zones (if available) or combine with a parent Region AZ. Note that cross-zone load balancing does not work between edge zones and regular AZs.
Test Latency and Performance
After deployment, measure latency from end users to the edge zone. Use tools like ping, traceroute, or application-level metrics. Verify that latency meets requirements. If using Wavelength, test from a 5G device on the carrier's network. If using Local Zones, test from the metro area. Monitor data transfer costs between the edge zone and parent Region, as these can add up if there is heavy cross-zone traffic. Adjust architecture if latency is higher than expected (e.g., move more processing to the edge).
Scenario 1: 5G Autonomous Vehicle Fleet Management A company develops an autonomous vehicle fleet management system that requires real-time decision-making with sub-10ms latency. The vehicles are connected via a 5G carrier. The company deploys the control logic and sensor fusion algorithms on EC2 instances in a Wavelength Zone (e.g., us-east-1-wl1-bos-wlz-1) co-located with the carrier's 5G core. Each vehicle sends sensor data to the Wavelength Zone, where it is processed and commands are sent back. The system uses an NLB for load balancing across instances. EBS volumes store session data temporarily, and aggregated telemetry is periodically sent to the parent Region (us-east-1) for storage in S3 and analysis. Common issues: misconfiguration of security groups blocking traffic from the 5G network, or forgetting that S3 is not local and must be accessed via the parent Region, which adds latency. Production scale: hundreds of vehicles, each generating 10 Mbps of data. The Wavelength Zone must handle 10 Gbps aggregate throughput, requiring careful instance selection and monitoring of EBS performance.
Scenario 2: Real-Time Video Processing for a Live Sports Event A media company needs to process and transcode live video streams from a stadium for near-real-time delivery to viewers. The stadium is in a metro area with a Local Zone (e.g., us-west-2-lax-1a in Los Angeles). The company deploys EC2 G4dn instances with GPU acceleration in the Local Zone to perform transcoding. The raw video feeds are ingested via AWS Direct Connect from the stadium to the parent Region (us-west-2), then routed to the Local Zone for processing. The processed streams are then sent to CloudFront for distribution. The Local Zone provides sub-5ms latency from the stadium, enabling real-time adjustments. Challenges: ensuring sufficient EBS throughput for multiple concurrent streams, and managing data transfer costs between the Local Zone and parent Region. Production scale: 50 concurrent 4K streams, each requiring 40 Mbps. The Local Zone must support high-bandwidth network and compute. Misconfiguration: using a single instance type that does not support GPU encoding, or forgetting to enable the Local Zone in the account before deployment.
Scenario 3: Industrial IoT with Edge Analytics A manufacturing company uses IoT sensors on factory equipment to monitor vibration and temperature. The factory is in a metro area with a Local Zone. The company deploys EC2 instances running AWS IoT Greengrass in the Local Zone to process sensor data locally, sending only alerts and aggregated metrics to the parent Region. This reduces bandwidth costs and latency for time-critical decisions (e.g., shutting down a machine to prevent failure). The Local Zone also hosts a local database (RDS for MySQL) for historical data. The parent Region hosts a dashboard and long-term storage. Common mistakes: not enabling the Local Zone, or using a service not available locally (e.g., Lambda) and assuming it runs in the edge zone. Production scale: 10,000 sensors, each sending 1 KB every second. The Local Zone must handle 10 MB/s ingestion. Misconfiguration: incorrect subnet routing causing traffic to go through the parent Region, defeating the purpose.
What SAA-C03 Tests on This Topic The exam covers Wavelength and Local Zones under Domain 3 (High Performance), Objective 3.1: 'Determine high-performing and/or scalable storage and compute solutions.' You will see scenario-based questions where you must select the appropriate edge service to meet latency requirements. Key differentiators tested:
Wavelength Zones are for 5G applications with sub-10ms latency; Local Zones are for metro-area applications with single-digit ms latency.
Wavelength Zones support only EC2, EBS, VPC, and ELB; Local Zones support more services (EC2, EBS, RDS, EKS, ELB).
Both are extensions of a parent Region and cannot exist independently.
Data transfer between edge zone and parent Region incurs inter-AZ costs.
Neither supports S3, DynamoDB, Lambda, or API Gateway natively.
Common Wrong Answers and Why Candidates Choose Them 1. Choosing AWS Outposts instead of Wavelength/Local Zones. Outposts are customer-owned hardware in your data center, not carrier or metro locations. Candidates pick Outposts because they think 'edge' means on-premises. The exam tests that Outposts require you to own and manage the hardware, while Wavelength/Local Zones are AWS-managed. 2. Selecting CloudFront for compute latency. CloudFront is a CDN for content caching, not for running compute at the edge (except Lambda@Edge, which is limited). Candidates confuse 'edge caching' with 'edge compute.' The correct answer is Wavelength or Local Zones for compute-intensive latency-sensitive tasks. 3. Assuming all AWS services are available in edge zones. Candidates often pick an answer that uses S3 or Lambda in the edge zone, which is not supported. The exam explicitly tests knowledge of service limitations. 4. Thinking Wavelength and Local Zones are independent regions. Candidates may assume they have their own console or billing. In reality, they are managed from the parent Region.
Specific Numbers and Terms Appearing on the Exam - Sub-10ms latency requirement -> Wavelength Zone. - Single-digit ms latency in a metro area -> Local Zone. - Services supported in Wavelength: EC2, EBS, VPC, ELB. - Services not supported in either: S3, DynamoDB, Lambda, API Gateway. - Parent Region association: each edge zone is tied to one Region. - Data transfer costs: inter-AZ rates.
Edge Cases and Exceptions - Multi-AZ: RDS in Local Zone does not support Multi-AZ within the zone; you can have a standby in a different AZ in the parent Region, but with higher latency. - Auto Scaling: can use edge zones, but cross-zone load balancing does not work between edge and regular AZs. - Direct Connect: not available directly in edge zones; must use parent Region. - Capacity: edge zones have limited capacity; you may need to request limits.
How to Eliminate Wrong Answers - If the scenario mentions 5G, eliminate Local Zones and Outposts; Wavelength is the only option. - If the scenario requires compute and storage at the edge with a broader set of services, eliminate Wavelength (limited services). - If the scenario mentions 'on-premises data center,' eliminate both Wavelength and Local Zones; consider Outposts or Storage Gateway. - If the scenario mentions 'content delivery' or 'caching,' consider CloudFront, not edge compute. - Always check the latency requirement: if it's below 10ms, Wavelength or Local Zone; if higher, standard Region may suffice.
Wavelength Zones provide sub-10ms latency for 5G applications by embedding AWS infrastructure in carrier data centers.
Local Zones provide single-digit ms latency in metro areas, supporting a wider range of services than Wavelength.
Both are extensions of a parent AWS Region and share the same VPC, security groups, and IAM policies.
Neither Wavelength nor Local Zones natively support S3, DynamoDB, Lambda, or API Gateway.
Data transfer between an edge zone and its parent Region incurs inter-AZ data transfer costs.
You must enable Wavelength/Local Zones in your account before you can create resources in them.
Cross-zone load balancing does not work between edge zones and regular Availability Zones.
For high availability in Local Zones, consider deploying in multiple edge zones or use a standby in a parent Region AZ.
Direct Connect and VPN connections terminate at the parent Region, not directly in the edge zone.
Always verify the latest service availability for each edge zone, as the list may change.
These come up on the exam all the time. Here's how to tell them apart.
AWS Wavelength
Embedded in telecom 5G network infrastructure.
Designed for sub-10ms latency from 5G devices.
Supports only EC2, EBS, VPC, and ELB.
Traffic routed via carrier's UPF local breakout.
Ideal for mobile applications like autonomous vehicles, AR/VR.
AWS Local Zones
Located in metropolitan areas without a full Region.
Designed for single-digit ms latency from metro users.
Supports EC2, EBS, RDS, EKS, ELB, and more.
Traffic routed via standard internet or Direct Connect.
Ideal for real-time gaming, media processing, enterprise migration.
Mistake
Wavelength and Local Zones are independent AWS regions.
Correct
They are extensions of a parent AWS Region. Resources are created in the same VPC as the parent Region and share the same account, billing, and management console. They are not separate regions.
Mistake
All AWS services are available in Wavelength and Local Zones.
Correct
Only a subset of services are available. Wavelength Zones support EC2, EBS, VPC, and ELB. Local Zones support more (EC2, EBS, RDS, EKS, ELB, etc.), but services like S3, DynamoDB, Lambda, and API Gateway are not available locally.
Mistake
Data transfer between edge zones and the parent Region is free.
Correct
Data transfer between an edge zone and the parent Region is billed at inter-AZ rates (typically $0.01-$0.02 per GB in each direction). This can become significant if there is heavy cross-zone traffic.
Mistake
You can create an internet gateway directly in a Wavelength or Local Zone.
Correct
Internet gateways are created in the parent Region and attached to the VPC. Edge zones use the parent Region's IGW for internet access. You cannot create an IGW in an edge zone.
Mistake
Wavelength Zones are available in every city and for any carrier.
Correct
Wavelength Zones are available only in select cities and with specific carrier partners (e.g., Verizon in the US, SK Telecom in South Korea). You must check AWS documentation for current availability.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Wavelength Zones are embedded within telecom providers' 5G networks to provide ultra-low latency (sub-10ms) to mobile devices. They support only EC2, EBS, VPC, and ELB. Local Zones are located in metro areas without a full Region, providing single-digit ms latency to end users via the internet or Direct Connect. They support a broader set of services including EC2, EBS, RDS, EKS, and ELB. Both are extensions of a parent Region.
No. AWS Lambda is not available in Wavelength or Local Zones. Lambda functions run in the parent Region. If you need serverless compute at the edge, consider AWS Outposts (with Lambda on Outposts) or use EC2 instances in the edge zone. For the exam, remember that Lambda is not supported in these edge zones.
You cannot establish a Direct Connect or VPN connection directly to an edge zone. Instead, you connect to the parent Region via Direct Connect or VPN, and then route traffic to the edge zone through the VPC. This adds latency, so plan accordingly. For ultra-low latency, ensure that the edge zone's resources are accessed directly by end users, not via your on-premises network.
No. Wavelength Zones are available only in select cities with specific carrier partners (e.g., Boston with Verizon, Tokyo with KDDI). Local Zones are available in many metropolitan areas (e.g., New York City, Los Angeles, London). Check the AWS documentation for the current list. They are always associated with a parent Region (e.g., us-east-1).
Data transfer between a Wavelength or Local Zone and its parent Region is billed at inter-AZ data transfer rates. As of 2025, this is typically $0.01 per GB for both inbound and outbound. Data transfer from the edge zone to the internet is billed at the parent Region's internet egress rates. These costs can accumulate if there is heavy cross-zone traffic.
Yes, you can create Auto Scaling groups that launch instances in edge zones. However, you must specify the edge zone as the availability zone. Cross-zone load balancing does not work between edge zones and regular AZs. Also, note that the Auto Scaling group's launch configuration must use an AMI available in the edge zone.
No, RDS in a Local Zone does not support Multi-AZ within the same Local Zone. You can configure a standby instance in a different Availability Zone in the parent Region, but this will introduce latency for failover and synchronous replication. For the exam, remember that Multi-AZ is not available in Local Zones.
You've just covered AWS Wavelength and Local Zones — now see how well it sticks with free SAA-C03 practice questions. Full explanations included, no account needed.
Done with this chapter?