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.