The AWS Enterprise Discount Program trades a spend commitment for a discount, stepped by threshold. This is the buyer side framework for the commit levels, how savings plans stack underneath, and the moves that cut your effective rate.
An AWS EDP discount steps up with the size of your spend commitment, but the committed floor is also your liability, so the deepest threshold is only a saving if your real usage actually fills it.
EDP discounts are stepped by the size of the total spend commitment over the term. A larger commitment unlocks a deeper threshold. AWS publishes its rate card and its commitment based programs on the AWS pricing pages, and the EDP is the negotiated layer above them.
The threshold is a ladder. Each rung costs more commitment. The question is never how deep the discount goes, but whether your usage fills the rung you are reaching for.
Reaching a deeper threshold requires a bigger floor. If usage does not fill the floor, the shortfall liability erases the deeper discount. A shallower threshold you can fill often beats a deeper one you cannot.
Savings plans and reserved instances reduce the rate on specific usage. The EDP discount applies more broadly. They are designed to coexist, but the interaction must be modeled or you double count the same workload.
A workload covered by a savings plan is already discounted. Counting it again at full rate toward the EDP floor overstates how much commitment you need. Model the net position, not the gross. AWS describes the programs on its savings plans pages and its reserved instance pages.
AWS commitment structures compared
| Structure | Discount basis | Flexibility | Best fit |
|---|---|---|---|
| On demand | None | Highest | New or volatile workloads |
| Savings plans | Usage commitment | Medium | Steady compute baseline |
| EDP 1 year | Spend commitment | Medium | Growing but uncertain estates |
| EDP 3 year | Deeper spend commitment | Lowest | Stable, predictable estates |
The levers are about the shape of the commitment, not the headline discount. Size the floor correctly, separate the savings plan layer, and keep a credible alternative.
Set the commitment against usage after savings plans, not before. The net number is what you actually pay, and it is the right basis for the floor. Anchoring on gross spend inflates the commitment.
AWS prices against the risk of losing the workload. A credible Google Cloud or Azure alternative resets the conversation and tests whether the threshold discount is real. AWS sets out which qualifying offers count on its Marketplace pages.
The common advice is to reach for the deepest discount threshold by committing the largest spend you can defend. We disagree. In roughly 21 of the 30 AWS EDP commitments we reviewed in 2024 and 2025, the floor needed to hit the deeper threshold sat above conservative real usage, and the shortfall liability gave back 30 to 60 percent of the extra discount. The buyer side move is to size the floor to net usage after savings plans, target a threshold you are confident you will fill, and negotiate flexibility for upside rather than locking it in. A rung you fill beats a deeper rung you reach for and miss.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Commit to the spend you will actually make after every other discount, not the gross number that reaches the next threshold. The deeper rung is a saving only if your usage stands on it.
AWS never publishes tiers, but advisory benchmarks cluster into observable bands that rise with both commit size and term length, off a hard minimum entry point of about $1M per year. The named vehicle is the Enterprise Discount Program, now often papered as a Private Pricing Agreement, or PPA.
Typical / observed EDP discount by annual commit
Ranges are observed buyer-side outcomes from FinOps advisory benchmarks, not AWS-published rates. Every EDP/PPA is confidential and deal-specific.
| Annual committed spend | Typical 3-yr discount | Typical 5-yr discount |
|---|---|---|
| $1M–$3M | ~6–10% | ~8–12% |
| $3M–$10M | ~10–14% | ~12–16% |
| $10M–$25M | ~14–18% | ~16–20% |
| $25M–$50M | ~18–23% | ~20–25% |
| $50M+ | ~22–28%+ | ~25–30%+ |
Moving a 3-year term to 5 years typically adds ~4–6 points of discount — weigh that against the extra years of growth-floor lock-in.
The load-bearing point is the shortfall asymmetry. Overconsumption is billed at your discounted rate, but underconsumption does not reduce what you owe: AWS bills the gap between actual usage and the committed floor at year or term end. On a $10M-per-year, three-year commit ($30M total) at a typical 12% discount, a year-one actual of $7M leaves a $3M shortfall invoiced in full — coverage you paid for and never used. A buyer who over-commits to reach a deeper headline tier can end up with a higher effective rate than a smaller, better-utilised commit.
Divide total contracted dollars by realistically usable consumption and right-size the commit to a defensible 80 to 90 percent utilisation forecast rather than stretching to hit the next tier. Reserve tier-jumping for cases where a signed multi-year migration pipeline de-risks the number, and ask AWS for its best number first to bracket the range before you counter.
This is the most consequential recent change and it moves against buyers. Historically, eligible AWS Marketplace SaaS bought through Private Offers retired commitment: 50 percent before 2022, then 100 percent from 2022 subject to a 25-percent-of-commitment cap. Teams used third-party SaaS through Marketplace to burn down commit they could not consume organically.
Effective 1 May 2025, AWS tightened qualification: only SaaS products hosted entirely on AWS retire commitment. Products running partly on other clouds or on-premises no longer count, and AWS enforces this through a "Deployed on AWS" designation with eligibility tags on Marketplace listings. A second, often-missed nuance: Marketplace spend that does count still burns commit at full value and typically receives no EDP discount — a $1M qualifying purchase retires $1M of commit but costs $1M, versus roughly $800K for $1M of directly-consumed services at a 20 percent discount.
A tool that counted in 2024 may not in 2026, silently increasing your shortfall exposure. Test each vendor against the "entirely on AWS" rule, prefer badged and tagged products, and get written confirmation from AWS that a specific Private Offer retires commitment before you sign.
EDP terms run one to five years and standard language requires each year's commitment to be no lower than the prior year — a built-in growth floor. The negotiable lever is the ramp: a back-weighted curve sets a lower year-one number with steeper increases later, matching the reality that migrations land late. On a $30M three-year commit, a flat ramp is $10M / $10M / $10M; a back-weighted ramp of $7M / $10M / $13M carries the same total and headline discount but roughly $3M less at-risk in the highest-uncertainty first year.
EDP vs Savings Plans vs Reserved Instances — how they stack
| Mechanism | What it discounts | Typical range | Stacks with EDP? |
|---|---|---|---|
| EDP / PPA | Broad account-wide spend | ~6–30% | Base layer |
| Savings Plans | Compute (EC2, Fargate, Lambda) | up to ~72% | Yes — compounds on top |
| Reserved Instances | Specific instance families | up to ~72% | Yes — compounds on top |
Discounts compound multiplicatively, not additively: a ~20% EDP under a ~45% Savings Plan yields roughly a ~56% effective rate on covered compute (1 − 0.8 × 0.55), not 65%. SP/RI spend still counts toward the EDP commit at its discounted price.
On the downside, the default exit terms favour AWS: unused remaining commitment can be billed at full value. Secure these at drafting time, because none can be added after signature: a shortfall cure period of 30 to 90 days before the true-up triggers; a step-down or force-majeure right (commonly 25 to 40 percent) on M&A, divestiture or regulatory change; credit carry-forward so a shortfall converts to future AWS credits rather than a cash clawback; and a mid-term ramp adjustment right if documented migration slips. Model your worst-case true-up as a real budget line before agreeing to any tier.
White Paper · AWS
AWS EDP flexibility provisions. The buyer side commit protection framework
Six flexibility clauses protect an AWS EDP commit: rollover, carryforward, over commit caps, under commit relief, and clean exit ramps. Read it free.
Only partly. Since 1 May 2025, AWS retires commitment only for SaaS products hosted entirely on AWS, shown by a "Deployed on AWS" designation, and even qualifying Marketplace spend usually burns commit at full price without the EDP discount — so re-audit every vendor before you rely on it.
Yes, but they compound rather than add, so a ~20% EDP under a ~45% Savings Plan yields roughly a ~56% effective rate on covered compute, and that discounted spend still counts toward your EDP commitment.
The AWS Enterprise Discount Program, or EDP, gives a customer a discount across AWS usage in exchange for a multi year spend commitment. AWS publishes its underlying rate card and savings programs, and the EDP is the negotiated layer on top.
EDP discounts step up with the size of the spend commitment. Larger total commitments unlock deeper discount thresholds, but a bigger commitment also raises the shortfall risk if your actual usage comes in lower.
Savings plans and reserved instances apply to specific usage and reduce the rate, while the EDP discount applies more broadly. Confirm how the two interact, because a poorly modeled stack can double count the same workload.
A shortfall is the gap between your committed spend and your actual spend. Under an EDP you generally remain liable for the committed amount, so an oversized commitment is a direct loss rather than a saving.
A three year EDP earns a deeper discount but locks the spend floor for longer. It suits stable, growing workloads. If the roadmap is uncertain, a shorter term with a conservative commitment often produces a better effective rate.
Some AWS Marketplace spend can count toward the commitment, subject to the deal terms. Confirm the qualifying categories in writing, because this clause can materially change whether you meet the committed floor.
Model the commitment against conservative real usage, not against an optimistic growth forecast. Size the floor to what you are confident you will spend, and negotiate flexibility for the upside rather than locking it in.
Across the AWS commitments we reviewed in 2024 and 2025, the biggest gains came from right sizing the committed floor and cleanly separating savings plans from the EDP layer, not from chasing the deepest headline discount.
A buyer side review of your EDP commit level, savings plan mix, and exit terms. Used across more than five hundred enterprise software engagements.
Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Independent review of your next AWS commitment. Corporate email only.
Open the Practice →The EDP discount looked great until we layered the savings plans underneath. The two were double counting the same workload, and the committed floor was set on the gross number, not the net one we would actually pay.
Confidential consultation. No follow up sales call unless you ask for one.
Oracle Eloqua framework signals, Eloqua edition signals, marketable contact tier signals, Eloqua advanced intelligence signals, Eloqua app cloud signals, and the broader Oracle commercial leverage signals.
