AWS private pricing and committed spend agreements are negotiated contracts in which you promise AWS a minimum total spend over a multi-year term and receive a discount across your usage in return. The most common form is the Enterprise Discount Program, an account-wide percentage discount in exchange for a committed annual spend, but private pricing agreements can also include custom rates on specific services. They sit on top of, not instead of, instrument-level discounts like Savings Plans and Reserved Instances, which is the single most important thing to understand before signing: the agreement discounts the bill, while the instruments discount the rate, and the two stack.
This explainer sits under our complete guide to AWS cost optimization, the pillar for this cluster, and is a Cut-step play in our See, Cut, Lock, Run method focused on rate negotiation. For the practical negotiation playbook see the sibling article how to negotiate an AWS Enterprise Discount Program.
A committed spend agreement gives a percentage off your overall bill. Savings Plans and Reserved Instances give a lower rate on specific usage. You want both: commit at the account level for the floor, then optimize rates underneath it.
What a committed spend agreement covers
The discount typically applies broadly across AWS usage, which is why it is powerful, but the coverage details decide its real value. Most agreements count the great majority of AWS service spend toward the commitment and the discount, and eligible AWS Marketplace purchases can contribute as well, which matters when you are sizing the commitment. The crucial questions are which services are in scope, whether the discount applies before or after Savings Plan and Reserved Instance discounts, and how shortfalls against the commitment are treated. A commitment you cannot realistically hit is not a discount, it is a liability, so the spend floor must be set against a defensible forecast rather than an optimistic growth story.
The levers that set your rate
The discount percentage is not a published table; it is negotiated, and a handful of factors move it. Total committed spend is the biggest, since larger commitments earn deeper discounts. Term length matters, with longer commitments generally trading a higher discount for less flexibility. Timing helps, because AWS, like any vendor, has periods where it is more motivated to close. Your growth trajectory and strategic value as a reference customer can also factor in. The asymmetry to respect is that AWS negotiates these deals constantly and you do so rarely, which is why going in with an independent forecast and benchmark of what comparable customers achieve is worth far more than the percentage it tends to add.
Negotiating a private pricing or EDP renewal?
We sit on your side of the table: independent benchmarks on the discount comparable customers achieve, a defensible commitment forecast, and the term structure that protects flexibility. We are not an AWS reseller, so our only incentive is your rate.
Book a commitment review →The risks to manage before signing
Three risks deserve attention. Over-commitment is the worst: a spend floor set above what you will actually use means paying for the shortfall with no benefit, so the forecast must be conservative and account for your own optimization work reducing spend during the term. Term lock-in reduces leverage to renegotiate if your architecture or the market changes, which argues for not over-extending the term. And the interaction with instrument discounts must be modeled, because a committed spend agreement that applies before Savings Plan discounts behaves very differently from one that applies after. Get these three modeled before you sign, not after.
| Lever | Effect on discount | Trade-off |
|---|---|---|
| Committed spend | Higher commit, deeper discount | Shortfall risk if over-committed |
| Term length | Longer term, larger discount | Reduced flexibility and leverage |
| Timing | End-of-period motivation helps | Requires planning the renewal |
| Benchmark | Knowing the market lifts the rate | Needs independent data |
AWS Enterprise Discount Program structure, private pricing scope, Marketplace eligibility and the interaction with Savings Plans reflect AWS as of May 2026. Specific terms are confidential and negotiated per customer; verify scope and stacking rules in your own agreement and current AWS documentation before relying on them.
The AWS Cost Optimization Field Guide includes the commitment forecasting model and the benchmark questions we bring to a private pricing negotiation, so you size the floor on evidence rather than optimism.
The short version
AWS private pricing and committed spend agreements trade a multi-year spend commitment for a discount across your bill, stacking on top of Savings Plan and Reserved Instance discounts rather than replacing them. The discount is negotiated, driven by commit size, term, timing and benchmark knowledge, and the real risks are over-commitment, lock-in and the interaction with instrument discounts. Sizing and negotiating these agreements with an independent forecast is core to an AWS cost optimization engagement, as in our SaaS on AWS case study.