AWS Outposts instantiate native AWS services, infrastructure, and operating models within an enterprise, on-premises data center environment. Outposts uses the same AWS APIs, tools, and infrastructure across a hybrid, on premises/AWS cloud environment. Outposts is designed to offer native AWS services and the same SDK for workloads that need to remain on-premises due to low latency or local data processing needs.
AWS Outposts come in two variants:
AWS Outposts infrastructure is the same AWS-designed infrastructure as is used in AWS data centers. It is built, owned and fully managed, maintained, and supported by AWS as if it was part of an AWS region. Outposts Native is deployed outside the enterprise firewall. Secure connectivity to AWS via AWS Direct Connect or VPN is required. (VMware Cloud on AWS Outposts is offered for deployment inside the enterprise firewall.)
Many AWS services will not run locally on Outposts, but instead, will be accessed remotely over the network from an Outpost. However, the services to be supported upon General Availability (GA) include:
Outposts is currently available in the following US AWS regions meaning that customers can connect their Outposts to these regions:
Additional regions in EMEA, APAC, and the Middle East are also supported.
AWS is not trying to replicate its public cloud on-premises. Rather, it is trying to help customers address use cases that are not good candidates for the public cloud, while offering the standard AWS tools and management APIs as an integrated control plane across both environments. As such, an outpost is an extension of an AWS public cloud region into a customer’s data center that offers a limited set of the most popular AWS services. However, like the AWS public cloud, Outposts will support a customer’s SaaS applications.
Product Brief Includes:
Download the full Product Brief now!