Arkinu
AWS service comparison

AWS Outposts vs AWS Wavelength: differences and when to use each

AWS Outposts
AWS Wavelength

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Compute

AWS Outposts

Fully managed service that brings AWS infrastructure, services, and APIs to customer premises, with capacity that AWS operates as part of a Region. It lets you run applications on premises with the same interfaces as in AWS when you need low latency or local data processing.

Exam phrases that point here

  • «run AWS services in your own data center with the same APIs, console, and tools»

    An Outpost is hardware that AWS installs and manages at the customer's premises and that works as an extension of a Region: you create VPC subnets on it and launch EC2 instances and EBS volumes with the same APIs.

    When not: If all you need is to connect the data center to a VPC, AWS Site-to-Site VPN or AWS Direct Connect is enough. And if the site has no stable connection to the Region, Outposts is not designed for that: it depends on the service link.

  • «data must stay on premises or in a country where there is no AWS Region»

    With Amazon EBS and Amazon S3 on Outposts, data is stored in the local rack, which helps meet data residency requirements.

    When not: Some metadata (for example instance IDs, metrics, tags, or bucket names) does travel to the Region, so you should validate the requirement with compliance. If the country has an AWS Region and the requirement is only about the country, deploying in that Region is normally enough.

  • «low latency to local systems, such as equipment on a manufacturing floor or in a hospital»

    The application runs in the same place as the equipment it talks to, without a round trip to the Region; local traffic goes out through the local gateway to the on-premises network.

    When not: If the users are in a city and you do not need to own hardware, AWS Local Zones gives low latency without operating a data center. If the users are mobile devices on a carrier's 5G network, AWS Wavelength fits.

  • «process large volumes of data locally that would be expensive to send to the Region»

    Data is generated and processed on the Outpost, and only what is necessary is sent to the Region.

    When not: If the problem is only moving a large amount of data to AWS once, the answer is in data transfer services (for example AWS DataSync, or AWS Data Transfer Terminal for bringing disks in person; AWS Snow Family is no longer offered to new customers), not a permanent rack.

  • «keep local workloads running even if the connection to AWS is lost»

    If the connection drops, the running instances and their EBS volumes keep working and can be reached from the local network.

    When not: While there is no connection, control plane operations (for example launching new instances) do not work. For environments that are routinely disconnected, AWS does not recommend Outposts and suggests options such as Amazon EKS Anywhere.

Study AWS Outposts →

Compute

AWS Wavelength

Deploys AWS compute and storage services at the edge of communications service providers' networks (Wavelength Zones), extending your VPC there. It is suited to applications that need low latency to mobile devices and end users.

Exam phrases that point here

  • «ultra-low latency for users of mobile devices connected to a carrier's 5G network»

    Wavelength Zones are AWS infrastructure installed in the telecommunications carrier's data centers: traffic from 4G/LTE or 5G devices on its network enters the instances through the carrier gateway.

    When not: If users do not depend on a carrier's network and being close to a city is enough, AWS Local Zones fits; if the application must run in your own data center, AWS Outposts. And for static or cacheable content, Amazon CloudFront.

  • «deploy compute at the edge of the telecommunications carrier's network»

    A Wavelength Zone extends a Region: you create a VPC subnet in it and launch EC2 instances or containers with the same tools.

    When not: A Wavelength Zone is a single zone and does not offer all the services of the Region (for example, it has no Amazon S3 or Amazon RDS); for high availability you have to combine it with other infrastructure.

  • «game streaming, live video, or machine learning inference for mobile devices»

    These are workloads that AWS cites as typical for Wavelength because they need compute close to the device and must respond very quickly.

    When not: The clue is the mobile device on the carrier's network. If users are spread around the world on the internet, think of Amazon CloudFront or AWS Global Accelerator, not Wavelength.

  • «connect instances to devices on the carrier network through a carrier gateway»

    The carrier gateway is the Wavelength component that lets traffic in from the carrier network and out to it and to the internet, translating the private IP address to a Carrier IP.

    When not: It generally does not support inbound connections initiated from the internet (only some carriers allow them): if the application must receive internet traffic in general, that part goes in the Region, behind an internet gateway.

Study AWS Wavelength →