computeCLF-C02SAA-C03SAP-C02

AWS Wavelength: The Ultra-Low Latency 5G Edge Powerhouse

Embed AWS compute and storage at the edge of 5G networks for single-digit millisecond latency to mobile devices

Updated 2026-02-21

Overview

AWS Wavelength embeds AWS compute and storage services within telecommunications providers' 5G networks, placing infrastructure at the edge of the carrier network to minimize latency for mobile and connected-device applications. Traffic from 5G devices reaches application servers without leaving the telecom network, avoiding the round-trip to a traditional AWS Region. This enables ultra-low latency use cases like real-time gaming, live video streaming, AR/VR, autonomous vehicles, and industrial IoT that require single-digit millisecond response times.

Deliver ultra-low latency (single-digit milliseconds) to 5G-connected end users and devices by running AWS workloads physically inside telecom carrier facilities, eliminating the network hop back to an AWS Region

Use When

Real-time multiplayer gaming requiring sub-10ms latency for 5G mobile players
Augmented Reality (AR) and Virtual Reality (VR) applications that need rapid frame rendering close to the device
Autonomous vehicle data processing and V2X (vehicle-to-everything) communication requiring near-instant response
Live video transcoding and streaming at the network edge to reduce buffering for mobile 5G audiences
Industrial IoT and smart manufacturing where machine sensors require real-time analytics with minimal latency
Connected healthcare applications such as remote surgery assistance or real-time patient monitoring over 5G

Avoid When

Batch processing or asynchronous workloads — latency is irrelevant; use standard EC2 in an AWS Region for lower cost and full service availability
Applications without a 5G or mobile connectivity requirement — AWS Local Zones or standard Regions provide better service breadth and pricing
Workloads requiring the full catalog of AWS services — Wavelength Zones have a limited subset of services available compared to a full Region
Global or multi-region architectures without edge latency needs — CloudFront or Global Accelerator are more appropriate and cost-effective
Data-heavy workloads with large egress requirements — data transfer costs from Wavelength Zones can add up quickly compared to Region-based deployments

Key Features

Ultra-low latency 5G edge compute

Single-digit millisecond latency achieved by co-locating compute with carrier 5G infrastructure

Carrier IP addresses

Public IPs routable over the carrier 5G network, separate from standard AWS public IPs

VPC subnet extension into Wavelength Zones

Wavelength Zone subnets are part of the parent Region VPC, enabling seamless private connectivity

EC2 instance support

Limited instance family support; GPU instances available for edge ML inference

Amazon EBS volumes

Block storage available in Wavelength Zones for EC2 instances

Amazon ECS and EKS

Container orchestration supported for edge containerized workloads

AWS CloudTrail logging

API activity in Wavelength Zones is logged via CloudTrail in the parent Region

AWS Config

Resource configuration tracking available for Wavelength Zone resources

Amazon RDS

Not available in Wavelength Zones; must be hosted in the parent Region and accessed over private AWS backbone

AWS Lambda

Lambda is not directly deployable in Wavelength Zones; use EC2 or containers instead

Amazon S3

S3 is not natively in Wavelength Zones; access via parent Region over private AWS network

Amazon CloudFront integration

CloudFront can be used in front of Wavelength workloads for caching and content delivery to non-5G users

AWS Outposts comparison

Unlike Outposts, customers do NOT own or manage the physical hardware; AWS and the carrier manage it

Physical hardware management by customer

AWS and the carrier manage all physical infrastructure — this is a critical shared responsibility distinction

Integration Patterns

Edge Compute Deployment

high freq

AWS WavelengthAmazon EC2

Deploy EC2 instances in Wavelength Zone subnets to process 5G device requests at the carrier edge. Assign Carrier IPs to instances so 5G devices can reach them directly without traversing the public internet. Use GPU instances (g4dn) for ML inference at the edge.

VPC Subnet Extension

high freq

AWS WavelengthAmazon VPC

Create a Wavelength Zone subnet within an existing parent Region VPC. Resources in the Wavelength Zone subnet and the parent Region share the same VPC, enabling private IP communication over the AWS backbone. Security Groups and NACLs apply normally.

Hybrid Edge + CDN Architecture

high freq

AWS WavelengthAmazon CloudFront

Use CloudFront to serve static assets and cached content to non-5G users globally, while routing latency-sensitive 5G traffic directly to Wavelength Zones via Carrier IPs. Combines CDN caching benefits with ultra-low latency edge compute.

Latency Tiering Architecture

high freq

AWS WavelengthAWS Local Zones

Use Wavelength Zones for 5G mobile device workloads requiring single-digit ms latency, and Local Zones for on-premises proximity workloads (single-digit to tens of ms). These are complementary, not competing services — different use cases and connectivity models.

Edge Audit and Compliance

medium freq

AWS WavelengthAWS CloudTrail

CloudTrail automatically captures all API calls made to Wavelength Zone resources and logs them in the parent Region. Use for compliance, security auditing, and operational troubleshooting of edge deployments.

Edge Resource Configuration Tracking

medium freq

AWS WavelengthAWS Config

AWS Config tracks configuration changes for EC2 instances and other supported resources in Wavelength Zones, enabling compliance rules and configuration history for edge resources from the parent Region.

Containerized Edge Workloads

medium freq

AWS WavelengthAmazon ECS

Run containerized microservices in ECS on EC2 launch type within Wavelength Zones for scalable, low-latency edge processing. Ideal for real-time video processing pipelines or gaming backend services at the 5G edge.

Service Limits & Quotas

LimitValueNote

Wavelength Zone availability

Available in select Wavelength Zones tied to specific carrier partners (e.g., Verizon in the US, Vodafone in Europe, KDDI in Japan, SK Telecom in South Korea) zones

The list of Wavelength Zones expands over time as new carrier deals are signed; exam questions reflect general availability, not specific zone counts

Supported compute instance types

Limited subset of EC2 instance types (e.g., t3, r5, g4dn families); not all instance families available in standard Regions are supported instance types

Instance type availability varies by Wavelength Zone and carrier; always check current zone-specific availability

VPC architecture requirement

A Wavelength Zone must be explicitly enabled in your AWS account and a subnet must be created within the Wavelength Zone inside an existing VPC in the parent Region configuration

You cannot create a standalone VPC in a Wavelength Zone; it must be a subnet within a parent Region VPC

Carrier IP (CIP) addresses

Each EC2 instance in a Wavelength Zone can be assigned a Carrier IP address — a public IP routable over the carrier's 5G network, separate from standard AWS public IPs per instance

Carrier IPs are NOT standard AWS Elastic IPs; they are allocated from the carrier's address space and are specific to Wavelength Zones

Service availability in Wavelength Zones

Limited to a subset of AWS services — primarily EC2, EBS, ECS, EKS, and select managed services; most AWS services (RDS, DynamoDB, Lambda, etc.) are NOT directly available in Wavelength Zones services

This is a critical exam trap: candidates assume all AWS services are available in Wavelength Zones just as in Local Zones

Network traffic path

Traffic from 5G devices to Wavelength Zone resources travels through the carrier's network only; traffic to the parent Region travels over the private AWS backbone (not the public internet) architectural constraint

Confusing the traffic path is a common exam mistake — traffic does NOT traverse the public internet between the device and the Wavelength Zone

Pricing Model

Pay-as-you-go based on EC2 instance hours, EBS storage, and data transfer — similar to standard AWS pricing but with Wavelength-specific rates

EC2 instances in Wavelength Zones are priced similarly to equivalent instances in the parent Region, but rates may differ by zone and carrier — check the pricing page for each specific Wavelength Zone
Data transfer INTO Wavelength Zones (ingress from the carrier network) is typically free; egress charges apply for data leaving the Wavelength Zone to the parent Region or internet
Carrier IP address allocation may incur additional charges similar to Elastic IP pricing in standard Regions
EBS volume pricing in Wavelength Zones follows a similar model to parent Region EBS but may have zone-specific rates
No upfront commitment required — all resources are billed on-demand; Reserved Instances and Savings Plans may apply to EC2 in Wavelength Zones for cost optimization
There is no charge simply for enabling a Wavelength Zone in your account — you only pay for resources you provision and use

Exam Tips

criticalVPC architecture and zone types

Wavelength Zones are EXTENSIONS of the parent AWS Region — they use the same VPC, same IAM, same APIs. You opt-in to enable them, then create subnets. They are NOT separate Regions or standalone environments.

criticalShared Responsibility Model for edge computing

The shared responsibility model does NOT change for Wavelength — AWS and the carrier manage ALL physical infrastructure. Customers are responsible for their applications, data, OS configuration, and network/security group settings. Customers have ZERO physical hardware responsibility.

criticalCarrier IP vs Elastic IP

Carrier IP addresses are the KEY differentiator — they allow 5G devices to reach Wavelength resources directly through the carrier network without touching the public internet. Standard Elastic IPs do NOT work for this purpose in Wavelength Zones.

criticalWavelength Zones vs Local Zones vs Outposts

Wavelength vs Local Zones exam trap: Local Zones extend AWS to metropolitan areas for low-latency access to on-premises users (any connectivity type). Wavelength Zones are specifically for 5G carrier network integration. Local Zones do NOT provide 5G integration.

criticalNetwork traffic paths and latency

Traffic from 5G devices to Wavelength Zones NEVER leaves the carrier network. Traffic between the Wavelength Zone and parent Region travels over the PRIVATE AWS network backbone — not the public internet. This two-path traffic model is frequently tested.

critical

Shared responsibility model does NOT change at the edge — AWS and the carrier manage ALL physical infrastructure in Wavelength Zones. Customers manage ONLY their applications, data, OS, and security configurations. Zero customer hardware responsibility.

critical

Wavelength = 5G carrier network embedded compute with Carrier IPs. Local Zones = metro proximity compute for any connectivity type. These are NOT interchangeable — '5G' keyword on exams always means Wavelength.

critical

Wavelength Zone is an EXTENSION of the parent Region VPC (subnet model). 5G traffic stays in carrier network; Region traffic uses private AWS backbone. Most managed services (RDS, Lambda, S3) are NOT available in Wavelength Zones and must stay in the parent Region.

importantService availability in Wavelength Zones

Most AWS managed services (RDS, Lambda, S3, DynamoDB) are NOT available directly in Wavelength Zones. Architecture must place these in the parent Region and connect via private AWS backbone. This is a key architectural constraint to understand for SAA-C03 and SAP-C02.

importantService selection for CLF-C02

For CLF-C02: Wavelength is about 5G + ultra-low latency + edge compute. If a question mentions 5G mobile devices needing sub-10ms latency, Wavelength is almost certainly the answer. Distinguish it from CloudFront (CDN/caching) and Local Zones (metro proximity).

importantAccount configuration and zone enablement

Wavelength Zones must be explicitly OPTED INTO per AWS account and per Region. They are not enabled by default. This is similar to how Local Zones require opt-in, and is different from Availability Zones which are available by default.

importantMigration and modernization patterns

For SAP-C02 migration scenarios: Wavelength is appropriate when migrating latency-sensitive mobile applications to 5G. The architecture pattern involves keeping databases/stateful services in the parent Region while moving compute to the Wavelength Zone — a 'split-tier' edge architecture.

Good to KnowGovernance and compliance at the edge

CloudTrail and AWS Config both work with Wavelength Zones and log/track resources from the parent Region. This means your existing governance and compliance tooling extends to edge resources without additional setup.

Common Misconceptions & Traps

Common Mistake

Customers are responsible for the physical infrastructure in Wavelength Zones, similar to how they manage servers in a colocation facility

Correct

AWS and the carrier partner manage ALL physical infrastructure in Wavelength Zones. Customers have zero physical hardware responsibility. The shared responsibility model is identical to standard AWS Regions — AWS manages security OF the cloud (hardware, facilities, network), customers manage security IN the cloud (applications, data, OS, security groups).

This is the #1 exam trap for edge computing services. Wavelength is NOT like Outposts-at-customer-site or a colo arrangement. The infrastructure sits inside the carrier's facility but is fully managed by AWS. Exam questions will try to trick you into thinking edge = customer-managed hardware.

Common Mistake

AWS Local Zones provide the same 5G carrier network integration as AWS Wavelength Zones

Correct

Local Zones and Wavelength Zones are fundamentally different. Local Zones extend AWS compute to metropolitan areas for low-latency access via any network connection (fiber, broadband, etc.) and support a broader set of AWS services. Wavelength Zones are specifically embedded inside 5G carrier networks and use Carrier IPs — they are designed exclusively for 5G mobile device use cases. Local Zones have NO special 5G integration.

Both services reduce latency by placing compute closer to users, which causes candidates to conflate them. The key differentiator is the 5G carrier network embedding and Carrier IP mechanism in Wavelength. On exams, '5G' or 'carrier network' keywords always point to Wavelength, not Local Zones.

Common Mistake

Carrier connectivity and network management in Wavelength is solely the customer's responsibility

Correct

The carrier (e.g., Verizon, Vodafone) manages the 5G network infrastructure and its connectivity to the Wavelength Zone. AWS manages the compute and storage hardware inside the Wavelength Zone. Customers manage their applications, EC2 configurations, security groups, and data — not the carrier network or physical hardware.

Exam questions attempt to blur the lines of responsibility at the carrier-AWS boundary. The answer is always: physical infrastructure (both AWS hardware AND carrier network infrastructure) is managed by AWS/carrier, not the customer. Customers only manage what they deploy on top.

Common Mistake

Resources in a Wavelength Zone are isolated from the parent AWS Region and cannot communicate with Region-based services

Correct

Wavelength Zone subnets are part of the parent Region's VPC. Resources in the Wavelength Zone can communicate with resources in the parent Region over the private AWS backbone network. The Wavelength Zone is an EXTENSION of the Region, not an isolated environment.

This misconception leads to incorrect architecture designs where candidates think they must duplicate all services in the Wavelength Zone. Understanding the VPC extension model is critical for SAA-C03 architecture questions — databases stay in the Region, compute goes to the Wavelength Zone.

Common Mistake

Amazon CloudFront and AWS Wavelength serve the same purpose and are interchangeable for low-latency use cases

Correct

CloudFront is a Content Delivery Network (CDN) that caches and distributes static/dynamic content from edge locations globally — it does not run custom application compute. Wavelength runs actual EC2 compute inside 5G carrier networks for ultra-low latency processing of 5G device requests. CloudFront reduces latency through caching; Wavelength reduces latency through proximity of compute to 5G devices.

Both services mention 'edge' and 'low latency' which confuses candidates. The distinction: CloudFront = content caching + delivery; Wavelength = application compute at 5G carrier edge. They can be used together in the same architecture (CloudFront for non-5G users, Wavelength for 5G users).

Common Mistake

All AWS services are available in Wavelength Zones just as they are in standard AWS Regions

Correct

Wavelength Zones support only a limited subset of AWS services — primarily EC2, EBS, ECS, and EKS. Major managed services like RDS, Lambda, S3, DynamoDB, and most others are NOT directly available in Wavelength Zones. Applications must be architected to use these services from the parent Region via the private AWS backbone.

Candidates familiar with AWS Regions assume full service parity. This leads to incorrect architecture designs on SAA-C03 and SAP-C02 exams. Always remember: Wavelength Zones = compute and storage only; everything else stays in the parent Region.

Memory Tricks

🧠

WAVE = Wireless (5G) Access at the Very Edge — Wavelength puts AWS inside the carrier's 5G network

🧠

Remember the two traffic paths: '5G IN stays in carrier, Region traffic stays private' — 5G device traffic never leaves the carrier network; Region communication uses private AWS backbone

🧠

Wavelength vs Local Zones: 'W for Wireless (5G)' vs 'L for Location (metro proximity)' — Wavelength is for 5G wireless, Local Zones are for location-based proximity

🧠

Carrier IP ≠ Elastic IP: 'CIP = Carrier's IP' — Carrier IPs are from the carrier's address space, not AWS's, and are the gateway for 5G devices to reach your Wavelength resources

🧠

Shared responsibility at the edge: 'Edge doesn't change the pledge' — the shared responsibility model is identical at the edge as in the Region; AWS still owns the hardware

CertAI Tutor · CLF-C02, SAA-C03, SAP-C02 · 2026-02-21

Ready to test your knowledge?

Practice CLF-C02, SAA-C03, SAP-C02 exam questions with AI-powered explanations — free to start.

AWS Wavelength: The Ultra-Low Latency 5G Edge Powerhouse

Overview

Key Features

Integration Patterns

Service Limits & Quotas

Pricing Model

Exam Tips

Common Misconceptions & Traps

Memory Tricks

Ready to test your knowledge?

Related Cheat Sheets