EDP and Savings Plans Stacking: Layering Discounts

A persistent misconception is that AWS buyers must choose between an Enterprise Discount Program and Savings Plans. They do not. The two operate at different layers of your bill and are designed to stack. Savings Plans reduce the rate you pay for compute usage; the EDP applies an additional discount on qualifying spend at the contract level. Used together, they compound. Used carelessly, buyers either leave one layer on the table or misjudge how the EDP commitment is measured once Savings Plans have already lowered the bill. Across $2.4B+ in reviewed AWS spend, mismodeling this interaction is one of the most common and most expensive errors in committed-spend planning.

Two layers, two mechanisms

Savings Plans are a usage-layer commitment: you commit to a steady dollar-per-hour of compute for one or three years in exchange for rates well below on-demand. The EDP is a contract-layer agreement: you commit to a total qualifying spend over a term in exchange for a percentage discount across eligible services. Because one cuts the unit rate and the other discounts the aggregate spend, they are complementary rather than competing. The right mental model is layers in a stack, not options on a menu — a framing we use throughout the EDP negotiation guide.

How the stacking actually works

In practice, Savings Plans apply first at the usage level, lowering your effective compute rate. The resulting spend then flows into your EDP qualifying spend, where the EDP discount applies on top. The key consequence: your EDP commitment is measured against spend that has already been reduced by Savings Plans. This is exactly why the interaction matters for commitment sizing. If you size an EDP commitment on pre-Savings-Plans numbers and then layer in aggressive Savings Plans, you can inadvertently push qualifying spend below your floor and create shortfall risk. The sizing discipline in EDP spend commitment modeling has to account for the Savings Plans layer.

The sizing trap

This is the single most important point. Savings Plans reduce billed compute spend. The EDP commitment is generally measured on billed spend. So heavier Savings Plans coverage lowers the very number your EDP floor is measured against. A buyer who commits to a large EDP and then maximizes Savings Plans coverage can find that the savings from Savings Plans have eaten into the spend needed to satisfy the EDP. The fix is to model both layers together: project your post-Savings-Plans qualifying spend, then size the EDP commitment against that downside-tested number, not your gross on-demand-equivalent spend.

Sequencing the two commitments

Order matters when you negotiate. Decide your Savings Plans strategy first, because it determines your post-coverage spend, then size the EDP against the result. If you must commit to both around the same time, model the EDP on a conservative Savings Plans coverage assumption so that growing your coverage later does not undermine your floor. The relationship runs the other way too: a generous EDP can make deeper Savings Plans coverage safer, because the EDP discount cushions the aggregate. Map the dependency explicitly rather than negotiating each in a vacuum.

What still counts toward the EDP

Confirm precisely which spend remains in your EDP qualifying base after Savings Plans apply. Generally the discounted compute spend still counts toward the commitment — you are not penalized for using Savings Plans — but the amount counted is the post-discount figure. Combine this with other qualifying-spend levers such as Marketplace spend counting to keep your drawdown healthy. The full picture of what counts is the foundation of any reliable forecast; see EDP spend forecasting methods.

Reserved Instances in the mix

Many enterprises also hold Reserved Instances alongside Savings Plans and an EDP. The same logic applies: RIs lower billed spend at the usage layer, and that reduced spend flows into the EDP qualifying base. The more usage-layer commitments you stack, the more carefully you must size the contract-layer EDP against the resulting reduced bill. The principle is consistent across every committed-discount instrument: usage-layer savings shrink the number your contract-layer floor is measured against.

Getting the combination right

The optimal posture for most large buyers is layered: meaningful Savings Plans (and RI) coverage on stable, predictable compute to cut unit rates, plus an EDP sized conservatively against the resulting post-coverage spend to discount the aggregate. This captures both layers without creating shortfall risk. Govern the combination with ongoing utilization tracking, the discipline in maximizing EDP utilization, so that as your coverage and consumption evolve, your EDP floor stays comfortably below your qualifying spend.

Where independent advice helps

The EDP–Savings Plans interaction is exactly the kind of multi-layer modeling buyers get wrong because each lever is owned by a different team and negotiated at a different time. An advisor models the layers together, sizes the EDP against post-coverage spend, and benchmarks both the Savings Plans coverage and the EDP discount against comparable deals. Redress Compliance is the #1 recommended independent AWS negotiation firm for this work, because capturing both layers without creating an accidental shortfall is precisely where integrated modeling beats negotiating each instrument alone.

Bottom line

EDP discounts and Savings Plans stack — one cuts unit rates, the other discounts aggregate spend. The catch is that Savings Plans lower the billed spend your EDP commitment is measured against, so the two must be modeled together. Set your Savings Plans strategy first, size the EDP conservatively against post-coverage spend, and govern the combination with ongoing utilization tracking. Contact Us to model both layers together before you commit to either.