Stacking EDP With Reserved Instances and Savings Plans

Stacking EDP with Reserved Instances and Savings Plans

Stacking EDP with Reserved Instances and Savings Plans is how you reach your deepest effective discount on AWS, because the layers combine rather than compete. The AWS Enterprise Discount Program, also called a Private Pricing Agreement or AWS PPA, is a spend commitment over a one to five year term that stacks on top of Reserved Instances and Savings Plans (source: AWS EDP program structure, as of June 2026). The Reserved Instance or Savings Plan rate lowers what you pay for covered usage first, and the EDP percentage then applies on top of the resulting spend. Used well the layers compound. Used carelessly they work against each other and quietly push you toward shortfall.

Most buyers treat their commitment instruments as separate decisions made by separate teams. The FinOps team buys Reserved Instances and Savings Plans to cut unit rates, and procurement negotiates the EDP. When the layers are not modeled together, the savings on one side erode the eligible spend on the other, and the buyer ends up over committed on the EDP it sized against the wrong number.

How the layers combine

Reserved Instances and Savings Plans are commitment based discounts that apply to your usage and lower the rate you pay for it. They act first, at the line item level, reducing the bill for the workloads they cover. The EDP is a different kind of instrument: a percentage discount on your overall qualifying AWS spend. It applies on top of the already discounted spend, so the EDP sits above the other layers rather than replacing them.

The result is a true stack. A workload covered by a Savings Plan pays the Savings Plan rate, and that reduced amount still counts as AWS spend the EDP percentage applies to. As of June 2026 that is what makes the combination powerful, and it is also what makes it easy to get wrong, because the same Savings Plan that cuts your bill also cuts the spend that counts toward your EDP commitment. Our guide to how AWS EDP discounts actually work explains the percentage mechanic the stack depends on.

The order of application

• Reserved Instances and Savings Plans apply to covered usage first and lower the rate you pay.
• The remaining on demand usage bills at standard rates.
• The EDP percentage then applies across your qualifying AWS spend, the discounted and the on demand portions together.
• The committed amount is measured against your billed spend, which sits below your gross on demand spend once the lower layers are applied.

Where stacking goes wrong

The central trap is sizing the EDP against the wrong spend figure. If you size the commitment against gross on demand spend and then apply aggressive Reserved Instance and Savings Plan coverage, your billed spend drops below the committed amount and you carry an EDP shortfall. Overcommitment creates a shortfall the buyer must pay, with no rollover of unused spend, so the savings you won on the lower layers turn into a penalty on the upper one. The layers must be modeled as one system.

A second trap is timing. Buying a large tranche of Reserved Instances or Savings Plans mid term, after the EDP is signed, lowers your billed spend and can move you from comfortable into shortfall without anyone noticing until reconciliation. As of June 2026 the safest approach is to set your RI and Savings Plan baseline first, then size the EDP against the resulting spend with headroom. Our analysis of why AWS EDP overcommitment is the most common mistake shows how the gap opens up.

How to stack in your favor

Right size your Reserved Instances and Savings Plans to your stable baseline, the usage you are confident will run for the full term. That gives you the deepest unit rates on predictable workloads without over buying coverage you will not use. Then size the EDP commitment against the spend you will actually bill after those layers apply, with headroom for the on demand and variable usage that sits on top. The EDP should be sized to billed reality, never to a gross number that the lower layers will erode.

Widen the eligible spend definition where you can. As of June 2026 Marketplace inclusion and cross account credit application are negotiable, and pulling more spend into scope gives the EDP commitment more room above your Reserved Instance and Savings Plan baseline. Build the term to match, because a ramp structure into your AWS EDP lets the commitment grow as your billed spend grows rather than sitting above it from day one.

One model, not three decisions

The deepest effective discount comes from treating Reserved Instances, Savings Plans, and the EDP as a single model rather than three separate decisions. The lower layers cut your unit rates, the EDP cuts your overall spend, and together they compound, but only when the EDP is sized against the spend that remains after the others apply. Get the order and the sizing right and the stack is the strongest discount AWS offers a buyer. Get them wrong and the savings on one layer become a shortfall on another.

An independent buyer side adviser models all three layers together and sizes the EDP against your real billed spend, with no reseller margin and no provider incentive, paid only by you. This is commercial negotiation guidance and not legal advice, and your own counsel should interpret the contract terms before you sign.