# AWS Outposts

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-outposts

> AWS Outposts is a fully managed service from Amazon Web Services that extends AWS infrastructure, services, APIs, and tools to virtually any data center, co-location space, or on-premises facility for a truly consistent hybrid experience.

Practice exams covering AWS Outposts: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 8 key features of AWS Outposts

AWS Outposts offers a fully managed service that extends AWS infrastructure, services, APIs, and tools to virtually any data center, co-location space, or on-premises facility for a truly consistent hybrid experience.

1. **Fully managed service**: AWS delivers and installs Outposts racks. Outposts servers are delivered for installation by onsite personnel or a third-party vendor, after which AWS remotely provisions compute and storage resources once the servers are connected to the network.
2. **Hybrid Cloud Capabilities**: Outposts enable a truly consistent hybrid experience by allowing you to use the same AWS infrastructure, services, APIs, and tools on-premises just as in the cloud, making it easier to run and manage applications wherever they reside.
3. **Local Data Processing**: Offering local data processing capabilities, AWS Outposts is ideal for workloads that require low latency access to on-premises systems, localized data processing, or local data storage.
4. **Seamless Integration**: AWS Outposts integrate tightly with AWSâs broad range of services, allowing for seamless deployment and management of applications across the cloud and on-premises environments.
5. **Scalable Computing**: With Outposts, you can scale your computing, storage, and database needs seamlessly between your on-premises environments and the cloud, providing flexibility and elasticity for your workloads.
6. **Secure**: AWS Outposts are built with the same infrastructure and security standards as AWS's cloud environment, offering built-in AWS security, identity, compliance, and data privacy features for protecting sensitive data and applications.
7. **Fully compatible with AWS Regions**: Applications running on AWS Outposts are fully compatible with AWS services running in AWS Regions, allowing for a seamless operation and movement of workloads across on-premises and cloud environments.
8. **Self-Service Capacity Management**: Reconfigure capacity across all assets in an Outpost or for an individual asset, which can be a server within an Outposts rack or an Outposts server.

## Where AWS Outposts is used

AWS Outposts are ideal for workloads that require low latency access to on-premises systems, local data processing, data residency, and tightly integrated hybrid cloud architectures.

1. **Hybrid Cloud Setup**: AWS Outposts enables businesses to integrate their on-premises data center with AWS cloud services. This use case is ideal for companies requiring low-latency access to on-premises systems while benefiting from AWS services and scalability. It allows for seamless migration, development, and management of applications across both environments.
2. **Data Residency Compliance**: For organizations facing strict data residency requirements that mandate certain data to be stored within the country, AWS Outposts provides a solution. By deploying Outposts on-site, businesses can meet compliance and regulatory requirements, ensuring data is processed and stored locally, while still leveraging AWS services and tools.
3. **High Performance Computing (HPC)**: Companies involved in research, engineering, or financial analysis often require High Performance Computing capabilities to process large datasets and perform complex calculations. AWS Outposts brings AWS compute and storage services close to where the data is generated, minimizing latency and optimizing performance for HPC applications.
4. **Local Data Processing for IoT**: In scenarios where Internet of Things (IoT) devices generate a massive amount of data, AWS Outposts offers a way to process this data locally before sending it to the cloud. This is particularly useful for reducing latency and bandwidth requirements in sectors like manufacturing, healthcare, and smart cities, enhancing operational efficiency and data analysis.
5. **Content Creation and Media Processing**: Media and entertainment companies often handle large files and require significant processing power for content creation, rendering, and editing. AWS Outposts facilitates these tasks by providing AWS storage and computational capabilities on-premises, streamlining media workflows and enabling real-time collaboration for geographically dispersed teams.

## How AWS Outposts is priced

AWS Outposts pricing models include upfront and monthly pay-as-you-go options, based on the configuration and capacity selected, without additional data transfer costs for accessing other AWS services in the same region.

- **No Upfront**: Purchase Outposts rack capacity for a three-year term with no upfront payment and monthly charges due over the term.
- **All Upfront**: Purchase Outposts rack capacity for a three-year term with full upfront payment.
- **Partial Upfront**: Purchase Outposts rack capacity for a three-year term with a partial upfront payment and monthly charges over the term.
- **Monthly Term-End Renewal**: If you do not notify AWS whether to renew or return your racks before the term ends, the racks renew monthly at the No Upfront rate for their configuration.
- **Operating System Charges**: Operating system charges are excluded from rack prices and are applied based on usage per instance.
- **AWS Service Usage**: AWS services running on Outposts racks are charged by the hour per instance, excluding underlying EC2 instance and EBS storage charges to avoid double billing those resources.
- **AWS Marketplace Software**: AWS Marketplace AMIs are charged at the same price as in the parent AWS Region.
- **Data Transfer**: Transfer from an Outpost to its parent AWS Region is free, as is transfer between the Outpost and the local network or internet through the Local Gateway. Transfer from the parent Availability Zone to the Outpost follows AWS Region data-transfer-out pricing; regional intra-AZ, inter-AZ, and VPC transfer charges remain unchanged.
- **Enterprise Support Subscription**: An AWS Enterprise Support subscription is required to order an Outpost.

## Services AWS Outposts works with

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Provides scalable compute capacity in the AWS cloud and on Outposts, making it easy to deploy and manage applications in a hybrid environment.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: AWS Outposts publishes capacity and connectivity metrics to CloudWatch. You can use dashboards and alarms to monitor available instance capacity and detect service-link connectivity problems.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: AWS Outposts supports Auto Scaling groups that launch EC2 instances into Outpost subnets. Scaling is constrained by the compatible instance capacity available on the Outpost.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: AWS Outposts racks provide local EBS volumes for EC2 instances, keeping block storage close to on-premises workloads. EBS snapshots can be stored in the parent AWS Region or, with supported configurations, locally on an Outpost.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: Container workloads on AWS Outposts can pull images from ECR through their ECS or EKS container runtime. The registry remains in the AWS Region while the containers execute on the Outpost.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: AWS Outposts supports ECS clusters with EC2 container instances running on Outposts racks or servers. ECS manages container placement and deployment while application processing stays on premises.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: AWS Outposts racks support EKS worker nodes connected to a regional Kubernetes control plane. EKS local clusters can also place both the control plane and worker nodes on an Outpost.
- **[Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache)**: AWS Outposts racks support ElastiCache nodes for Redis and Memcached. Applications can use these local caches to reduce latency to cached data without placing the cache in the parent Region.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: AWS Outposts racks support EMR clusters running on local EC2 capacity. This lets Hadoop and Spark workloads process on-premises data close to where it resides.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: AWS Outposts API activity recorded by CloudTrail can be matched by EventBridge rules. For example, a rule can trigger automation when an Outpost resource is created or changed.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: AWS Outposts racks support local RDS DB instances for supported database engines. RDS manages database operations while the database runs on premises, close to applications with low-latency or data-residency requirements.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: AWS Outposts racks support Route 53 Resolver on Outposts, which provides local DNS resolution for resources on the rack. Its local cache helps workloads continue resolving previously cached names during temporary disconnections from the parent Region.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: S3 on Outposts stores objects in buckets on an Outposts rack and exposes them through local S3 on Outposts endpoints and access points. This keeps object data on premises for local processing and data-residency requirements.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: AWS Outposts extends a regional VPC through subnets placed on the Outpost. Local gateways on racks and local network interfaces on servers connect supported workloads to the on-premises network, while VPC Flow Logs and Traffic Mirroring support traffic monitoring.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: AWS Outposts supports AWS Backup protection for supported EC2 and EBS resources running on Outposts racks. Backup policies can schedule backups and retain recovery points in the parent AWS Region.
- **[AWS Certificate Manager (ACM)](https://blowstack.com/tools/cloud-services-hub/aws-certificate-manager-(acm))**: Application Load Balancers on AWS Outposts use ACM certificates for HTTPS listeners. This provides TLS termination for applications served through a load balancer running locally on the rack.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: AWS Outposts sites and Outposts can be provisioned and managed with CloudFormation resource types. Templates can also place supported resources, such as EC2 instances and VPC subnets, on a specified Outpost.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: AWS Outposts records its API activity in CloudTrail, including the caller, request time, and source IP address. CloudTrail also records supported API activity for services running on the Outpost.
- **[AWS CodeDeploy](https://blowstack.com/tools/cloud-services-hub/aws-codedeploy)**: EC2 instances on AWS Outposts can run the CodeDeploy agent to receive application deployments. Deployment groups can target these instances for controlled software rollouts on premises.
- **[AWS DataSync](https://blowstack.com/tools/cloud-services-hub/aws-datasync)**: AWS Outposts can host an EC2-based DataSync agent for transferring data between local storage and supported AWS storage destinations. Running the agent on the Outpost places the transfer component close to on-premises file systems.
- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: AWS Outposts can use Direct Connect for service-link connectivity to its parent AWS Region. Supported private-connectivity configurations carry service-link traffic through private networking rather than requiring public internet connectivity.
- **[AWS Elastic Disaster Recovery](https://blowstack.com/tools/cloud-services-hub/aws-elastic-disaster-recovery)**: AWS Outposts can serve as a recovery destination for AWS Elastic Disaster Recovery. Replicated workloads can be recovered onto compatible EC2 capacity on an Outposts rack to meet on-premises recovery requirements.
- **[AWS Health Dashboard](https://blowstack.com/tools/cloud-services-hub/aws-health-dashboard)**: AWS Outposts reports operational events through AWS Health Dashboard. Events such as service-link connectivity problems help identify infrastructure issues affecting an Outpost.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: AWS Outposts uses IAM to control access to its management APIs and resources. Policies can restrict actions such as creating Outposts, viewing sites, or managing capacity, including through resource-level permissions and tags.
- **[AWS IoT Greengrass](https://blowstack.com/tools/cloud-services-hub/aws-iot-greengrass)**: AWS Outposts can run IoT Greengrass on local EC2 instances on racks or servers. Greengrass components can process device data and run edge applications close to on-premises equipment.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: EBS volumes on AWS Outposts use AWS KMS keys for encryption. KMS manages the encryption keys in the parent Region while encrypted volume data resides on the Outpost.
- **[AWS License Manager](https://blowstack.com/tools/cloud-services-hub/aws-license-manager)**: EC2 workloads on AWS Outposts can use License Manager configurations to track software-license consumption. This helps manage bring-your-own-license software running on local AWS compute capacity.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: AWS Outposts can run compatible EC2-based software purchased through AWS Marketplace. Marketplace AMIs can be launched on suitable Outposts capacity to deploy products such as network appliances or business applications on premises.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: AWS Outposts private connectivity uses interface VPC endpoints powered by PrivateLink for communication with regional service infrastructure. This supports a private service-link path through a VPC and Direct Connect.
- **[AWS Resource Access Manager (AWS RAM)](https://blowstack.com/tools/cloud-services-hub/aws-resource-access-manager-(aws-ram))**: AWS Outposts owners can use AWS RAM to share supported Outposts resources with other AWS accounts. Recipient accounts can use shared capacity and networking resources without owning the physical Outpost.
- **[AWS Storage Gateway](https://blowstack.com/tools/cloud-services-hub/aws-storage-gateway)**: AWS Outposts can host a Storage Gateway appliance on a local EC2 instance. This places the gateway and its local cache on premises while providing supported file, volume, or tape access backed by AWS storage.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: EC2 instances on AWS Outposts can be managed through Systems Manager using SSM Agent. Operators can run commands, apply patches, collect inventory, and open Session Manager sessions without deploying a separate on-premises management platform.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: AWS Outposts racks support Application Load Balancers that distribute HTTP and HTTPS traffic locally. Their targets can include application instances running on the Outpost.
- **[VMware Cloud on AWS](https://blowstack.com/tools/cloud-services-hub/vmware-cloud-on-aws)**: VMware Cloud on AWS Outposts uses AWS Outposts infrastructure to run a VMware software-defined data center on premises. It combines local AWS hardware with VMware compute, storage, and networking software.

## What is AWS Outposts

Amazon Web Services (AWS) Outposts bridges the gap between cloud computing and on-premises deployment, offering businesses a seamless integration of AWS cloud services directly within their local data centers. This innovative solution caters to organizations that require low-latency access to on-premises systems, have to adhere to strict data residency policies, or are in stages of a gradual migration to the cloud.

AWS Outposts effectively brings the robustness, agility, and innovation of AWS services into the physical premises of an organization, thereby enabling a truly consistent hybrid experience. At the heart of AWS Outposts is the concept of extending AWS infrastructure, services, APIs, and tools to virtually any data center, co-location space, or on-premises facility. It involves the deployment of AWS-designed hardware that is fully managed, maintained, and supported by AWS, ensuring that customers can focus on their applications instead of infrastructure management.

This solution is particularly attractive for industries such as healthcare, financial services, and telecommunications, where data sensitivity, regulatory compliance, and latency are critical considerations.

AWS Outposts offers a variety of configurations, including compute and storage options, which customers can tailor to their specific requirements. Once installed, the Outposts seamlessly integrate with the broader AWS ecosystem, allowing applications running on-premises to leverage a broad spectrum of AWS cloud services. This enables scenarios such as local data processing, complex data analysis on-premises, and the flexibility to store and process sensitive data locally while still taking advantage of the global AWS infrastructure.

You can create subnets on an Outpost for resources such as EC2 instances, EBS volumes, ECS clusters, and RDS instances; instances in these subnets communicate with instances in the AWS Region using private IP addresses within the same VPC.

You cannot connect an Outpost to another Outpost or Local Zone within the same VPC.

Outposts is available as 1U and 2U servers, 42U racks, and multiple-rack deployments, allowing deployment at on-premises or edge locations.

Connectivity to the on-premises network uses a local gateway for Outposts racks and a local network interface (LNI) for Outposts servers.

Second-generation racks offer two configurations: Single-rack Outposts integrates compute and networking in one self-contained rack, while Multi-rack Outposts pairs one or more compute racks with a separate network rack.

Single-rack Outposts cannot be expanded by adding racks.

The management of AWS Outposts is streamlined through the AWS Management Console, where users can create and manage resources on their Outpost just as they would in the cloud. This unified management approach means developers can deploy applications with the same AWS APIs, control plane, tools, and hardware across on-premises and cloud environments, fostering productivity and innovation.

Outposts depends on a resilient connection to its anchor Availability Zone for management, monitoring, and service operations to function properly.

The default quota is 10 Outposts per site, and this adjustable quota applies to Outpost virtual resources.

AWS provides encryption at rest and in transit, granular security controls, and auditing mechanisms for Outposts racks. Under the shared responsibility model, customers are responsible for physical security and access controls around the rack, as well as the facility, networking, and power requirements.

By effectively extending the reach of the AWS cloud to on-premises environments, AWS Outposts represents a significant leap forward in hybrid cloud computing. It not only addresses the inherent challenges associated with managing disparate on-premises and cloud environments but also unlocks new opportunities for innovation, efficiency, and scalability. Whether businesses are looking to migrate to the cloud gradually, require low-latency processing capabilities, or must comply with strict data residency regulations, AWS Outposts provides a powerful, flexible, and secure platform to meet these diverse needs.

## Concepts related to AWS Outposts

- [Edge Computing](https://blowstack.com/tools/cloud-concepts-hub/edge-computing): Edge computing places processing near data sources or users instead of relying exclusively on centralized cloud infrastructure.
- [Hybrid Cloud](https://blowstack.com/tools/cloud-concepts-hub/hybrid-cloud): Hybrid cloud is a deployment model that integrates public cloud services with on-premises or private cloud infrastructure to support connected workloads, data, and operations.
- [On-Premises Infrastructure](https://blowstack.com/tools/cloud-concepts-hub/on-premises-infrastructure): On-premises infrastructure is computing, storage, and networking equipment deployed in facilities controlled by an organization rather than in a public cloud provider’s data centers.
