EDP commitments ran 15 to 25 percent above realized consumption
The EDP discount runs 5 to 20 percent. The typical overcommitment ran 15 to 25 percent. Put those two numbers on the same page and the default EDP is net negative: the discount is real, and the unconsumed commitment it was traded for is larger. The negotiation is the sizing, not the rate.
Prepared by Redress Compliance · August 14, 2026 · AWS advisory. EDP and Savings Plan reviews across enterprise estates, 2024 to 2026.
Executive summary
Typical buyer commitments were sized 15 to 25 percent above realized consumption, and Compute Savings Plans were over committed against trailing twelve month consumption by 14 to 28 percent on most estates. The forecast, not the rate, is where EDP value leaks.
The discount runs about 5 percent for smaller commitments to 20 percent at the top commitment thresholds and longer terms, stepping at thresholds rather than scaling smoothly. Whenever the overcommitment percentage exceeds the discount percentage, the agreement costs more than list.
The offer is a mix of credits and discounts, and the mix changes quarter to quarter. EDP and PPA proposals blend rate discounts with credits, and AWS's appetite on each component shifts with its own quarter, so every proposal should be dated and read against the quarter it was issued in.
The marketplace is the flexible valve. Marketplace transactions credit toward the commitment at typically 50 percent for general purchases and 100 percent for specific strategic partners, letting third party software spend help fill a commitment consumption alone would miss.
Three years is the balance point on term, trading discount depth against optionality, because every additional committed year extends the weakest number in the agreement, the forecast.
The exits are written at signature or not at all. Early termination with defined notice and pro rated commitment relief is negotiable as part of the framework, and the default structure, firm commitment against uncertain consumption, is materially in the publisher's favor until it is.
The framework, element by element
| Element | How it works | Buyer note |
|---|---|---|
| Commitment | Firm annual spend across the term | Size to trailing telemetry, never to the growth forecast |
| Discount | 5 to 20 percent, stepped by commitment thresholds and term | Worthless the moment the overcommit exceeds it |
| Credits | Blended into EDP and PPA offers alongside the rate | Sweeten year one without repricing the base; weigh them separately |
| Term | Typically three years | Longer terms deepen the rate and extend the forecast risk |
| Marketplace credit | 50 percent general, 100 percent strategic partners | The valve that lets third party spend fill the commitment |
| Savings Plans beneath | Rate commitments inside the spend commitment | Over committed 14 to 28 percent against trailing use on most estates |
| Early termination | Notice and pro rated relief, if negotiated | The default structure has no exit worth having |
Run the two percentages against each other before signing anything. A 12 percent discount on a commitment that runs 20 percent above what you will consume is not a saving, it is an 8 percent premium wearing a discount's name. The EDP only pays when the commitment is honest, which is why the trailing twelve month consumption file is worth more than any negotiation tactic in this agreement.
The terms that move the number
- Size the commitment to trailing twelve month consumption, because the growth forecast produced the 15 to 25 percent overshoot and the telemetry did not.
- Trade commitment depth for rate only from an honest baseline, since the discount curve rewards commitments the forecast inflates for free.
- Negotiate the marketplace credit rates and route eligible third party spend through them, so the commitment fills from spend you were making anyway.
- Hold the term at three years unless the rate movement genuinely pays for the extra forecast risk.
- Write the early termination clause at signature: defined notice, pro rated commitment relief, and treat the renewal cycle as the moment all of this reopens.
- Date every proposal and time the ask, because EDP and PPA offers are a mix of credits and discounts whose composition changes quarter to quarter, and the same request lands differently across AWS's own calendar.
The AWS EDP negotiation playbook
The commitment sizing method, the discount curve, the marketplace credit mechanics, the exit clause set, and the renewal cycle leverage.
Get the playbook →The discount is the price of your optionality
Strip the branding and an EDP is a simple trade: AWS buys certainty about your spend, and pays for it with a discount. The question every buyer should ask is whether the price AWS paid, 5 to 20 percent, covers what the certainty cost you. Across our reviews, mostly it did not, and the reason is structural.
The commitment is a firm number and the consumption is an uncertain one, so someone has to absorb the gap between them. The contract assigns that risk entirely to the buyer: consume less than committed and you pay anyway, consume more and AWS simply bills it. There is no scenario where the gap falls on the publisher, which is what makes the sizing conversation the entire negotiation.
And the sizing conversation is where the forecast walks in. Commitments built on growth forecasts ran 15 to 25 percent above realized consumption, and the Savings Plans beneath them repeated the pattern at 14 to 28 percent. The forecast is not a lie; it is the seller's optimism and the buyer's ambition agreeing with each other, and the agreement between them is billed to you. The trailing twelve month file is the only party in the room without a motive.
The marketplace credit is the underused counterweight. At 50 percent general credit and 100 percent for strategic partners, third party software the estate already buys can flow through the marketplace and fill commitment the workloads alone would miss. It converts the commitment from a bet on your infrastructure growth into a routing decision about spend that already exists, which is a far safer thing to promise.
The exit clause completes the frame. An EDP with defined notice and pro rated relief is an agreement you can afford to be wrong about; the default EDP is not, and the difference between those two documents costs nothing at signature and everything after. Ask for the exit while AWS still wants the signature. That is the only moment it is cheap.
The wider cloud commit picture, including the same forecast mechanics at the other hyperscalers, sits in the AWS overspending report and the AWS practice.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What the commitment reviews showed, 2024 to 2026
Across the EDP and Savings Plan reviews we ran, the pattern held at both layers of the commitment stack:
The gap between committed spend and realized consumption when the commitment was sized on the forward forecast.
The same forecast mechanism repeating one layer down, against trailing twelve month compute consumption.
Three patterns recurred. Commitments sized in the growth planning meeting rather than from the billing data. Marketplace credit left unnegotiated and unrouted, so existing third party spend filled nothing. And exit clauses missing entirely, so the overcommitment had no relief valve when the forecast met reality.
The buyer side move is to let the billing history write the commitment. The wider library sits in the AWS practice.
Your first five moves
- Build the trailing twelve month consumption file first, by service and by account, because it is the one number in the negotiation without a motive.
- Size the commitment at or below trailing consumption and let genuine growth arrive as uncommitted upside, not as pre paid forecast.
- Inventory the estate's third party software spend and negotiate the marketplace credit rates that let it fill the commitment.
- Price the term honestly: take the extra years only where the rate movement exceeds the forecast risk they add.
- Write the exit at signature, defined notice and pro rated relief, and calendar the renewal cycle as the moment the whole framework reopens. The AWS practice runs the sizing and the negotiation with you.
Frequently asked questions
What discount does an AWS EDP deliver?
Typically 5 percent for smaller commitments rising to about 20 percent at the top commitment thresholds and longer terms. The discount steps at commitment thresholds rather than scaling smoothly, and the overall EDP or PPA offer is a mix of credits and discounts whose composition changes quarter to quarter, which is why the commitment number matters more than any single percentage.
How should an AWS EDP commitment be sized?
To trailing consumption, not to growth forecasts. Typical buyer commitments were sized 15 to 25 percent above realized consumption, and Compute Savings Plans were over committed against trailing twelve month consumption by 14 to 28 percent on most estates. An unconsumed commitment is spend no discount recovers.
Do AWS Marketplace purchases count toward an EDP commitment?
Yes, at a credit rate: typically 50 percent for general marketplace transactions and 100 percent for specific strategic marketplace partners. That makes the marketplace the flexible valve in the commitment, letting third party software spend help fill an EDP that consumption alone would miss.
What is the right AWS EDP term length?
Typically three years, which balances the discount rate against optionality. Longer terms deepen the rate but extend the forecast risk, and the forecast is already the weakest number in the agreement.
Can an AWS EDP be terminated early?
Only on the terms you negotiated at signature: defined notice and pro rated commitment relief, subject to the early termination clauses in the EDP contract. The buyer side discipline is to negotiate that protection as part of the framework, before it is needed.
Is the default AWS EDP structure buyer friendly?
No. The default structure is materially in the publisher's favor: the commitment is firm, the consumption is uncertain, and the discount is the only compensation. The buyer side job is to construct the EDP as a commercial framework that preserves optionality without sacrificing the rate.
When is the best time to negotiate an EDP?
At the renewal cycle, with a trailing consumption file in hand. Renewal is when the commitment resets, the credit rates are negotiable, and the exit clauses can be written in, and the trailing file is what stops the next commitment from repeating the 15 to 25 percent overshoot.
Negotiating AWS 2: The Commitment, and the Measurement Rule
The commitment retires on net spend while support bills on gross, so AWS uses whichever base is worse for you in each place. Plus the one way ramp, shortfall as an invoice, and the relief clauses to win first.