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.
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.
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.
