Skip to main content
← Back to Articles
GuideCost Optimization

AWS EDP vs Savings Plans: Which Commitment Comes First?

They are not competitors: Savings Plans discount the rate you pay per hour of compute, while an EDP (now sold as a Private Pricing Agreement) is a negotiated percentage off almost your whole bill in exchange for a multi-year total-spend commitment, typically from around $1M a year. They stack, and the order matters. Optimize first, then buy Savings Plans against the baseline that survives, then size the EDP commitment on that optimized number, because both commitments bill you whether you use them or not.

5 min readBy Hermann Lotter
AWS EDP vs Savings Plans: Which Commitment Comes First?

Up to 72%

Savings Plans discount

~$1M/yr committed

Typical EDP entry point

Yes

Do they stack?

The direct answer

A Savings Plan is a self-service pricing instrument: you commit to a fixed dollar-per-hour spend on compute for one or three years, and AWS discounts the hourly rate, up to 66% on Compute Savings Plans and up to 72% on EC2 Instance Savings Plans versus On-Demand. An EDP (Enterprise Discount Program, which AWS now usually papers as a Private Pricing Agreement or PPA) is a negotiated contract: you commit to a total AWS spend over one to five years, and AWS applies a percentage discount across nearly the whole bill.

They are not alternatives. The EDP percentage is applied to your spend after Savings Plan and Reserved Instance rates, and that spend still counts toward the EDP commitment. A cost-mature account at EDP scale typically runs both: Savings Plans shaping the compute rate, the EDP shaving the total.

The decision that actually matters is sequencing, which is the rest of this article.

What a Savings Plan is, in one paragraph

You commit to spending a fixed amount per hour, say $10/hour, on eligible compute for one or three years, paying none, half, or all of it upfront. Every eligible hour you run is billed at the discounted Savings Plan rate until your committed amount is used up each hour; anything beyond it bills at On-Demand. Compute Savings Plans cover EC2, Fargate and Lambda anywhere, EC2 Instance Savings Plans cover one instance family in one region at the deeper discount. It is self-service in the console, no negotiation, no minimum spend, and the commitment bills every hour whether you used it or not.

  • ✓Scope: compute (EC2, Fargate, Lambda; SageMaker has its own plan). Not S3, not RDS, not data transfer.
  • ✓Discount: up to 66% (Compute) or 72% (EC2 Instance), set by term and payment option, published publicly.
  • ✓Risk: an oversized hourly commitment is paid even when nothing eligible is running.

What an EDP actually is

An EDP is a private contract with AWS: you commit to a minimum total spend over the term, commonly quoted from around $1M a year (some brokers report entry at $500K), for one to five years, and AWS discounts nearly every service on the bill by a negotiated percentage. The percentages are not published. Third-party negotiation guides consistently describe single-digit discounts at the entry level, rising with commitment size and term length, with much deeper discounts reported at the tens-of-millions scale.

Three fine-print items do most of the damage in practice. First, the commitment is owed in full: finish the year under-committed and you pay the shortfall anyway. Second, the discount AWS gives you does not count toward the commitment, so a 10% discount means you need roughly 11% more usage to hit the same committed number. Third, AWS Marketplace purchases can typically count for only up to a quarter of the commitment, so a plan to bridge a shortfall through Marketplace has a ceiling.

An EDP also usually travels with Enterprise Support, so if you are not already paying for that tier, price it into the comparison.

The sequencing rule: optimize, then Savings Plans, then EDP

Both instruments turn your current spend into a floor. That is why the order is not negotiable. Commit first and optimize later, and the optimization no longer saves money; it just digs you further under a commitment you still owe.

The sequence that works: first remove the waste that needs no commitment at all, the idle instances, unattached volumes, over-retained snapshots and hot storage that should be tiered. Second, right-size what remains. Third, buy Savings Plans against the compute baseline that survived, because that baseline is now real. Fourth, and only now, size the EDP commitment on the optimized trajectory plus honest growth, not on last year’s unoptimized bill plus optimism.

This is also the strongest negotiating position. Walking into an EDP conversation with coverage already bought and waste already removed signals that the commitment number is real, and it sets the baseline AWS discounts from at the level you actually intend to spend.

A commitment is a photograph of your bill at signing. Make sure the photograph is of the optimized bill.

Who should even be having the EDP conversation

Under roughly $500K a year of AWS spend, the answer is simple: nobody will offer you one, and the single-digit percentage would be worth less than one honest right-sizing pass. Between $500K and $1M, it is worth asking your account team what is available, but Savings Plans and waste removal still dominate the savings math. From $1M a year upward, with a credible growth story and a multi-year horizon, the EDP percentage starts compounding meaningfully on top of your Savings Plan rates, and leaving it unnegotiated is leaving money on the table.

The one thing that does not change with scale: the commitment must be sized on a bill you have already cleaned. If you want the cleaning done before you sign anything, that is exactly the shape of a scoped cost review.

The short version

  • • Savings Plans and an EDP answer different questions. A Savings Plan is a self-service hourly rate discount on compute; an EDP is a negotiated percentage off nearly the whole bill in exchange for a total-spend commitment over one to five years.
  • • They stack. The EDP percentage applies to your spend after Savings Plan rates, and your Savings Plan spend still counts toward the EDP commitment, so running both is the normal end state for a qualifying account.
  • • EDP entry is commonly quoted around $1M a year in committed spend (some sources say $500K), with entry-level discounts in the single digits. The exact numbers are not public and come out of negotiation with your AWS account team.
  • • The order is the whole trick: remove waste first, buy Savings Plans against the clean baseline, and only then size the EDP commitment. A commitment sized on an unoptimized bill converts removable waste into contractual spend.
  • • Both instruments bill the commitment whether you use it or not. The shortfall on a missed EDP commitment is still owed, and an unused Savings Plan hour is money spent.
  • • Below roughly $500K a year of AWS spend, the EDP conversation is premature: Savings Plans, Reserved Instances and plain waste removal are where the money is.

Frequently Asked Questions

Do AWS EDP discounts and Savings Plans stack?

Yes. The EDP percentage is applied to your spend after Savings Plan and Reserved Instance rates, and that discounted spend still counts toward your EDP commitment. Running both is the normal end state for accounts at EDP scale.

What is the minimum spend for an AWS EDP?

AWS does not publish a figure. Third-party negotiation guides most commonly cite around $1M a year in committed spend as the practical entry point, with some reporting entry at $500K. Below that, Savings Plans and Reserved Instances are the available instruments.

Is the EDP the same thing as a Private Pricing Agreement (PPA)?

Commercially, yes. AWS has been papering these deals as Private Pricing Agreements; the structure, a negotiated cross-service discount in exchange for a multi-year total-spend commitment, is the same, and people use the names interchangeably.

What happens if we miss our EDP commitment?

You pay the shortfall. The commitment is a contractual minimum, not a target, which is exactly why it should be sized on an optimized baseline rather than a hopeful forecast.

HL

Hermann Lotter.FinOps practitioner who has led cloud and AI cost optimization inside a 180-person organisation, identifying six-figure annual savings across AWS and LLM spend. He writes Easy Entropy from hands-on engagements, not theory, and takes on scoped AWS FinOps consulting engagements.LinkedIn

Free Assessment

Want this outcome in your AWS bill?

Get a free cloud cost analysis and a prioritized optimization roadmap.

Request Free Analysis →

Topics covered

AWS EDPSavings PlansPrivate Pricing AgreementAWS Discount NegotiationFinOps

Related Articles