AWS Outposts and Hybrid Cloud: Pricing and Contract Guide

AWS Outposts is AWS's fully managed hybrid cloud infrastructure solution, delivering AWS compute, storage, networking, and services in your on-premises data centre or co-location facility. Unlike most AWS services — which follow a pure pay-as-you-go model — Outposts uses a capacity reservation model with 3-year commitment terms that require careful evaluation before signing.

This article is part of our AWS Enterprise Negotiation Guide. For organisations considering Outposts as part of a broader hybrid cloud strategy, it is worth reading alongside our multi-cloud cost optimisation guide and our cloud commitment strategy guide, which covers how Outposts commitments interact with your overall AWS commercial portfolio.

AWS Outposts Product Families

AWS offers two distinct Outposts product families, each targeting different deployment scenarios and scale requirements.

Outposts Rack

Outposts Rack is a full-size (42U) rack of AWS hardware delivered to your data centre or co-location facility. It is the flagship Outposts product and supports the widest range of AWS services: EC2, EBS, S3 on Outposts, ECS, EKS, RDS, and more. Outposts Rack is designed for organisations with high compute and storage requirements that need a substantial AWS-consistent footprint on-premises.

Outposts Rack pricing is based on the specific compute and storage configuration chosen. Configurations are defined by EC2 instance type (e.g., M5, C5, R5, i3) and storage capacity. AWS quotes Outposts Rack on a per-rack, per-configuration, 3-year basis. Pricing is not published publicly and varies by configuration — pricing typically starts at $250K–$350K for a base configuration on a 3-year basis for the capacity fee alone.

Outposts Servers

Outposts Servers are 1U or 2U servers designed for locations with limited space or power — retail stores, branch offices, manufacturing floors, and edge computing environments. They support a more limited set of AWS services (primarily EC2, ECS, and limited EBS) compared to the full Rack, but are priced more accessibly. Outposts Servers pricing starts at approximately $10K–$15K per server for a 3-year capacity reservation.

AWS Outposts Pricing Structure

Understanding Outposts pricing requires distinguishing between the different cost components, which are billed separately and have different negotiation characteristics.

1. Capacity Reservation Fee (Infrastructure)

The primary Outposts cost is the 3-year capacity reservation — the equivalent of a 3-year "all-upfront" Reserved Instance for the on-premises hardware. This covers the hardware, its delivery, installation, ongoing maintenance, and AWS's management of the infrastructure. The capacity fee is paid either upfront (lower total cost) or as monthly installments.

2. EC2 Instance Charges on Outposts

Running EC2 instances on Outposts incurs per-instance charges on top of the capacity fee — similar to the charges for Reserved Instance utilisation on-demand. These charges are typically lower than equivalent public-region on-demand pricing but are subject to EDP discount (where applicable).

3. Service Charges

Additional AWS services running on Outposts (S3 on Outposts, RDS on Outposts, EKS on Outposts) incur standard service charges based on consumption — storage volumes, API calls, and so on. These charges follow the standard AWS pricing model and are EDP-eligible.

4. Data Transfer

Data transferred between Outposts and the parent AWS region incurs standard data transfer charges. For S3 on Outposts to a public S3 bucket, inter-region transfer fees apply. Planning data transfer patterns between your Outposts deployment and the parent region is important for accurate total cost modelling. See our AWS data transfer cost optimisation guide for relevant context.

Outposts Pricing Reference (Indicative)

Note: AWS Outposts pricing is quote-based and not publicly published. The figures above are indicative only. Actual pricing varies significantly based on configuration, region, and commercial negotiation. Always request a formal quote from your AWS account team.

Outposts vs Alternative Hybrid Approaches: Total Cost Comparison

Before committing to Outposts, a rigorous alternative comparison is essential. The key alternatives to Outposts for hybrid workloads are AWS Local Zones, AWS Direct Connect to existing on-premises infrastructure, or hardware refresh with managed hosting.

Outposts and Your EDP: Commercial Interaction

AWS Outposts has a specific interaction with Enterprise Discount Programs that differs from standard EC2 usage. Understanding this interaction is important for organisations managing both Outposts deployments and an EDP commitment.

Does Outposts Spend Count Toward EDP?

Outposts capacity reservation fees (the infrastructure component) do not count toward EDP minimum spend commitments in the standard AWS pricing model. However, service charges incurred on Outposts instances (EC2 instance charges, service consumption charges) are typically EDP-eligible. This means the infrastructure commitment is an additional cost outside your EDP, while consumption charges benefit from your EDP discount.

This structure can create tension in your AWS commercial portfolio: an Outposts commitment represents significant locked spend that doesn't reduce your EDP pressure, while consumption charges on Outposts do attract EDP discounts. When modelling your AWS commercial position including Outposts, work with your account team to confirm precisely which Outposts charges are EDP-eligible under your specific agreement.

Outposts as an EDP Negotiation Tool

Conversely, if you are considering an Outposts deployment, this represents significant long-term spend commitment that AWS's account team will value. Use your Outposts interest as leverage in broader EDP negotiations — an organisation committing to both a multi-year EDP and an Outposts deployment is a high-value commercial customer for AWS, and account teams have discretion to improve terms across the portfolio to secure both commitments.

Outposts Contract Terms: What to Review

Outposts contracts have several terms that warrant careful review before signing. Unlike standard AWS service terms — which are largely governed by the AWS Customer Agreement — Outposts involves specific hardware commitment terms with different flexibility provisions.

Cancellation and Exit Rights

Outposts capacity reservations typically do not include cancellation rights after a short initial window. The 3-year commitment is generally treated as a non-cancellable infrastructure order. Before signing, clarify whether there are any early termination provisions and what penalties apply.

Hardware Refresh and Upgrade Rights

Outposts hardware is managed entirely by AWS — you have no direct access to the physical infrastructure. Clarify with your account team what happens at end of the 3-year term: is hardware refreshed as part of a renewal, or does it require a new procurement cycle? What happens if AWS releases a new Outposts generation during your term?

Service Availability SLAs

Outposts SLAs differ from public region SLAs because the hardware is physically located in your facility. AWS's SLA for Outposts typically requires that you maintain your facility's power and cooling to specified standards. Review the SLA terms carefully to understand your responsibilities as a customer versus AWS's responsibilities as the managed service provider.

Network Connectivity Requirements

Outposts requires a reliable network connection to the parent AWS region for management plane functions. If your connectivity to the AWS region is interrupted, Outposts continues to run existing workloads (within a grace period) but cannot launch new instances or manage resources. Ensure your network architecture provides appropriate redundancy for the Outposts connectivity path.

8 Tactics for Outposts Negotiations

When Outposts Makes Sense

Despite the pricing premium, Outposts is the right choice for specific, well-defined scenarios. Understanding these use cases helps organisations avoid both over-investing in Outposts where alternatives are more economical, and under-investing where Outposts delivers genuine business value.

Outposts is genuinely well-suited for regulated industries requiring data residency — healthcare, financial services, government — where workloads cannot be placed in public regions for compliance reasons but where AWS's operational model and API consistency is required. It is also well-suited for applications with sub-millisecond latency requirements to on-premises systems — industrial IoT, trading systems, hospital imaging — where AWS Local Zones or Direct Connect latency is insufficient.

Organisations that are primarily motivated by "keeping control" of their infrastructure but have no genuine data residency or latency requirement are typically better served by Direct Connect to public regions or AWS Local Zones, which provide AWS service access at lower cost and without the 3-year infrastructure commitment.

Frequently Asked Questions