Infrastructure Design

Extending AWS to On-Premises with AWS Outposts - Hybrid Cloud Design and Operations

Extend AWS to on-premises for data residency and low-latency requirements. Learn about Outposts deployment models and Local Gateway design.

約 3 分で読めます

Outposts Use Cases

Outposts is a service that physically installs AWS infrastructure in your on-premises data center. There are three primary use cases. First, data residency requirements. When financial regulations or government requirements mandate that data be kept within a specific country or facility, Outposts lets you keep data on-premises while using AWS services. Second, low-latency requirements. It is effective when round-trip latency to the cloud is unacceptable for manufacturing line control or real-time data processing. Third, local data processing. It is used when large volumes of data are generated and need to be preprocessed locally before being transferred to the cloud.

Available Services and Network Design

AWS services available on Outposts include EC2, EBS, S3 (S3 on Outposts), RDS, ECS, EKS, EMR, and ElastiCache. These services are operated with the same APIs as Regional AWS and can be provisioned with CloudFormation or Terraform. The network communicates with Regional AWS via a service link connection and with the on-premises network via a Local Gateway. The service link is used for Outposts management traffic and access to Regional services, with a minimum bandwidth of 1 Gbps recommended. Since the configuration extends VPC subnets to Outposts, integration with existing VPC designs is straightforward.

Operational Model and Costs

For Outposts racks, AWS handles installation, maintenance, hardware replacement, and software patching. The customer provides data center power, cooling, physical security, and network connectivity. Pricing is a 3-year subscription with three payment options: all upfront, partial upfront, and no upfront. There are no additional charges for EC2 instances or EBS volumes; compute and storage capacity are included in the subscription fee. Deploying Outposts requires a lead time of several weeks, and pre-verification of site power, cooling, and network requirements is important. For more details on Outposts, related books on Amazon are also available.

Summary

Outposts extends AWS infrastructure to on-premises, enabling a hybrid environment with the same operational model as the cloud. Run AWS services including EC2, EBS, S3, RDS, and ECS on-premises, operated with the same APIs and management tools as the Region. It addresses data residency and ultra-low-latency requirements while maintaining a cloud-native development experience.

Related Services

AWS OutpostsA hybrid cloud service that extends AWS infrastructure and services to on-premises locationsAmazon EC2A compute service that provides virtual servers in the cloudAmazon S3A scalable object storage service

Related Articles

Operating Hybrid Cloud with Amazon EVS - DR Site Construction and Burst CapacityLearn how to operate a hybrid cloud with Amazon EVS, including DR site construction, on-demand capacity bursting, and integration patterns with AWS services.GPU-Based Machine Learning Training with AWS Batch - Cost-Efficient Large-Scale TrainingRun GPU training with your existing Docker containers, and cut costs by up to 90% using Spot Instances and checkpointing. Includes guidance on when to choose Batch over SageMaker.Amazon EBS Volume Design and Operations - Selection Criteria for gp3 and io2 with Snapshot StrategiesClarify the selection criteria for gp3 and io2 volume types, and learn practical IOPS/throughput design guidelines along with snapshot-based backup strategies.

More on This Topic

Why Auto Scaling Scales Out Fast but Scales In Cautiously - The Design Intent Behind Asymmetric Decision LogicThis article explains why EC2 Auto Scaling executes scale-out immediately while applying a cooldown period for scale-in, the flapping prevention mechanism, and the internal logic of target tracking scaling.Demand-Driven Infrastructure with AWS Auto Scaling - Designing and Optimizing Scaling PoliciesLearn how to use target tracking, predictive, and scheduled scaling policies effectively, and optimize costs with mixed instances policies that leverage Spot Instances.AWS Fault Domain Design - How the Three-Layer Structure of AZs, Regions, and Partitions Protects AvailabilityLearn why AWS infrastructure is designed with three layers of fault domains - AZs (fault isolation), Regions (geographic separation), and Partitions (political separation) - and how far failures propagate at each layer, with real-world examples.Distributed Systems Principles Learned from AWS Outages - How Past Major Incidents Reshaped ArchitectureUsing AWS's published incident reports as case studies - including the S3 outage (2017), Kinesis outage (2020), and the unique nature of us-east-1 - this article explains design principles such as Shuffle Sharding, Static Stability, and Cell-based Architecture.Why AWS Builds Regions Where It Does - The Hidden Criteria Behind Data Center Site SelectionWe explain the criteria AWS considers when deciding region locations, including power supply, geopolitical risk, data sovereignty legislation, network connectivity, and natural disaster risk, with concrete examples from specific regions.Why AWS Availability Zone IDs Differ Per Account - The Design Intent Behind AZ MappingExplains how us-east-1a maps to different physical AZs per account, why AZ IDs (use1-az1) were introduced, the design intent of even capacity distribution, and considerations for cross-account AZ specification.Batch Computing Infrastructure - Large-Scale Parallel Processing with AWS BatchLearn how to build large-scale batch processing with AWS Batch. Covers job queue design, auto-scaling compute environments, cost optimization with Spot Instances, and building batch infrastructure ideal for scientific computing and large-scale data processing.Automating Batch Computing with AWS Batch - Designing Job Queues and Compute EnvironmentsLearn about job scheduling with AWS Batch, choosing between Fargate and EC2 compute environments, and leveraging Spot Instances for cost optimization.

Similar Articles and Services

Hybrid Cloud Infrastructure - Integrating On-Premises and AWS with AWS OutpostsLearn how to extend AWS infrastructure to on-premises environments with AWS Outposts and build hybrid cloud architectures with EC2 integration. Covers design patterns for data residency and low-latency requirements.Hybrid Cloud with AWS Outposts - Extending AWS to On-PremisesCompare rack and server form factors, and learn about hybrid cloud design for running EC2, ECS, and RDS on-premises.AWS OutpostsA hybrid cloud service that physically installs AWS infrastructure and services in on-premises data centers, enabling operation with the same APIs and tools as the cloudAWS Edge Strategy - The Hybrid Future Shaped by Outposts, Local Zones, and WavelengthWe explain the hybrid and edge strategy AWS deploys through three edge services - Outposts, Local Zones, and Wavelength - comparing them with Azure Stack and GCP Distributed Cloud to highlight differences in breadth of options and design philosophy.