AWS Outposts
AWS hardware installed in your own building, run by AWS as part of a Region.
AWS Outposts brings a piece of AWS into your own data center, factory or office. AWS delivers and installs the equipment, either a full 42U Outposts rack or a smaller 1U or 2U Outposts server, and then operates, monitors and replaces it. On that hardware you run familiar services such as EC2 instances, EBS volumes, ECS clusters or RDS databases, using the same console, APIs and tools as in the cloud.
Each Outpost is anchored to a parent AWS Region through a network connection called the service link, and it appears in your VPC as one more subnet. Instances on the Outpost talk to instances in the Region over private IP addresses. The control plane, the part that decides what runs where, stays in the Region; the data and the computing can stay on your premises.
Why not just use the Region? Three usual reasons: latency, when a machine on a factory floor needs answers in a few milliseconds; data residency, when rules require data to stay in a specific building or country without a nearby Region; and local processing, when moving huge volumes of data to the cloud is impractical. It is a form of hybrid cloud with one big difference from running your own servers: the hardware is AWS's, and so is the job of keeping it alive. The site still has to meet AWS's power, space and network requirements.
Keep in mind
- AWS-owned and AWS-managed racks or servers in your own facility.
- Runs EC2, EBS, ECS, RDS and more with the same APIs as the cloud.
- Connected to a parent Region by a service link; it extends your VPC.
- Chosen for low latency, data residency or local data processing.
