An AWS Enterprise Discount Program commitment should be sized to the spend you are confident you will use, not the growth AWS forecasts for you. The EDP trades a multi-year spend commitment for a discount, and the discount scales with the size and length of the commit. The trap is the commitment floor: agree to more than you consume and you pay the shortfall anyway. This guide explains how AWS structures an EDP, the levers that improve it, how to size and ramp the commit, and how to protect against an overcommit at renewal.
AWS sells the EDP as a simple trade: commit more, save more. The simplicity hides the risk. The commitment is on total spend across the term, usually three years and often ramped so each year's floor rises. Marketplace purchases, Savings Plans, and Reserved Instances all interact with the commit. AWS runs on a December 31 fiscal year, and the account team has quarter-end and year-end incentives that a prepared buyer can use.
How AWS builds an EDP offer
An EDP is a private agreement that layers a percentage discount on top of your AWS consumption in exchange for a committed minimum spend over a fixed term. The discount is not published. It is set by the size of your commit, the length of the term, your growth trajectory, and how hard you negotiate. The same annual spend can earn very different discounts depending on how the commit is structured.
The commitment is the part that carries risk. You agree to spend a minimum amount, usually growing year over year through a ramp. If your actual usage falls short of the committed floor in a period, you owe the difference. That shortfall true-up is the most expensive clause in an EDP, and it is the reason sizing matters more than the headline discount.
Marketplace spend changes the picture. A defined portion of eligible AWS Marketplace purchases counts toward your EDP commitment, which means third-party software bought through Marketplace can help retire the commit. Savings Plans and Reserved Instances reduce your rates, and the discounted spend still counts toward the commitment, so they lower cost without slowing your progress against the floor.
Account teams are measured on committed spend growth, not on your efficiency. That is not a criticism, it is the incentive structure, and it explains why the first proposal pushes a larger commit and a steeper ramp than your data supports. The counter is simple: bring your own bottom-up forecast and make the account team negotiate against your number rather than the other way around.
The EDP levers that improve a deal
Discount is one lever among many, and it is the weakest place to spend your effort. The EDP gives buyers structural levers that protect spend across the full term. Use them in order, starting with the ones that protect you the most.
| Lever | What it does | When it works best |
|---|---|---|
| 1. Commit sizing | Set the floor to confident consumption | Always; the floor is the real risk |
| 2. Ramp shape | Back-load growth into later years | When adoption builds over the term |
| 3. Term length | Trade a longer term for a deeper discount | When your cloud roadmap is stable |
| 4. Marketplace retirement | Count eligible Marketplace spend to the commit | When you buy third-party software on AWS |
| 5. Private pricing (PPA) | Service-specific rate cards below standard | When one or two services dominate spend |
| 6. Egress and data transfer | Negotiate data transfer rates | When egress is a large, growing line |
| 7. Savings Plans interplay | Stack rate discounts on committed spend | When compute is steady-state |
| 8. Shortfall protection | Cap or soften the true-up exposure | When the ramp outruns your forecast |
| 9. Credits and migration funds | Take onboarding or migration credits | When a workload move is planned |
| 10. Renewal and co-term | Align renewal timing and terms early | When agreements renew apart |
| 11. Exit and flexibility | Build room for divestiture or decline | When the business may contract |
| 12. Discount | The headline percentage, last | After the structure is set |
The order matters. The discount is the easiest thing for AWS to give and the least valuable thing to win if the commitment floor is wrong. Settle the commit size, the ramp, and the shortfall terms first, then negotiate the percentage.
Sizing an AWS commit in the next two quarters? Our advisors run this playbook with you.
Cloud Contract NegotiationSizing and ramping the commit
The work that decides whether an EDP saves money happens before you accept a number. Sizing is a forecasting exercise, not a negotiation tactic, and it should be done bottom up from real workload plans rather than top down from last year's bill.
| Months before signing | What to do | Why |
|---|---|---|
| 6 to 5 | Build a bottom-up spend forecast by workload | The commit must rest on real demand |
| 5 to 4 | Separate committed from discretionary spend | Only commit to the spend you control |
| 4 to 3 | Model the ramp against the adoption curve | Avoid a floor that rises faster than usage |
| 3 to 2 | Benchmark discount against commit and term | Know the trade before AWS frames it |
| 2 to 1 | Negotiate structure, then discount | Lock the floor and ramp before price |
| 1 to 0 | Close near AWS quarter or year end | Timing pressure favors the buyer |
Private pricing, Marketplace, and rate cards
For organizations with concentrated spend, a Private Pricing Agreement can matter more than the headline EDP discount. A PPA sets negotiated rates on specific services, often the ones that dominate your bill, such as compute, storage, or data transfer. Where one or two services drive most of your cost, service-level rates can beat a flat EDP discount applied across everything.
AWS Marketplace is the second instrument buyers underuse. A defined share of eligible Marketplace purchases retires EDP commitment, which means software you would buy anyway can count toward your floor. Routing eligible third-party purchases through Marketplace can turn a commitment risk into committed spend you were always going to make.
Data transfer, particularly egress, is negotiable and often overlooked. If your architecture moves large volumes of data out of AWS, the egress line grows with the business and is a fair target for a private rate. Bring it into the EDP conversation rather than treating it as a fixed cost. The AWS private pricing guide covers how rate cards are structured.
Savings Plans, Reserved Instances, and the commit
Rate discounts and the EDP solve different problems, and the best buyers use them together rather than as alternatives. The EDP applies a discount in exchange for a total spend commitment. Savings Plans and Reserved Instances lower the unit rate on specific resource families in exchange for a usage commitment on those resources. The two stack: rate-discounted spend still counts toward your EDP floor, so committing to steady-state compute through a Savings Plan both lowers cost and retires commitment.
The discipline is to layer them in the right order. Establish the EDP commit on spend you are confident about. Inside that envelope, use Compute Savings Plans for flexible, steady compute and Reserved Instances or EC2 Instance Savings Plans where the instance family is stable. Match the term of each instrument to how stable the underlying workload is, so a one-year commitment covers anything uncertain and a three-year commitment covers only the truly fixed base.
| Instrument | What it commits | Best for |
|---|---|---|
| EDP | Total AWS spend over the term | Account-wide discount on growing spend |
| Compute Savings Plan | Hourly compute spend, flexible across families | Steady compute with a changing instance mix |
| Reserved Instances | A specific instance family and region | Stable, predictable workloads |
| Marketplace spend | Eligible third-party software purchases | Retiring commitment with planned buys |
A common mistake is to over-rotate into long Reserved Instances for workloads that later move or shrink. Because the EDP already rewards total committed spend, you do not need to lock every workload into a three-year reservation to capture value. Keep the reservation term matched to workload stability and let the EDP discount cover the rest.
Shortfall, the overcommit trap, and exit flexibility
The overcommit is the most common and most expensive EDP mistake. It happens when the committed floor, especially in the later ramped years, exceeds what the business consumes. You then pay the shortfall as a true-up, which means you pay for cloud you never used.
Protect against it before signing. Size conservatively, back-load the ramp, and negotiate shortfall terms that soften the exposure, for example the ability to carry unused commitment forward or to apply Marketplace spend against a gap. Build flexibility for the cases that reduce spend: a divestiture, a workload that moves off AWS, or a downturn.
| Risk | How it bites | The protection to negotiate |
|---|---|---|
| Ramp outruns adoption | Later-year floor exceeds usage | Back-loaded ramp and a lower first-year floor |
| Shortfall true-up | You pay the gap to the commit | Carry-forward of unused commitment |
| Business contraction | Divestiture or decline cuts spend | Exit or reduction rights for defined events |
| Concentrated commit | One service stalls and drags the floor | Marketplace and PPA spend counted to the commit |
Renewal is where AWS expects the commitment to grow again. Start the renewal conversation early, with your own forward forecast in hand, and be willing to hold the commit flat or reduce it if usage does not support growth. A renewal negotiated from the vendor's growth assumption rather than your own data is how overcommitment compounds.
Get this playbook applied to your AWS agreement. Confidential assessment within one business day.
Book a 30 minute callKey takeaways
- The EDP discount is negotiable; the commitment floor is the real risk.
- Size the commit bottom up from confident, controllable spend.
- Back-load the ramp so the floor never outruns adoption.
- Use a private pricing rate card when spend is concentrated.
- Route eligible Marketplace spend to retire the commitment.
- Negotiate shortfall protection and exit flexibility before signing.
- Renew from your own forecast, not the vendor's growth assumption.
Frequently asked questions
What is an AWS EDP and how does the discount work?
The Enterprise Discount Program trades a committed minimum spend over a multi-year term for a discount on AWS usage. The discount is private and scales with the size of the commitment, the term length, and your negotiation. The discounted spend still counts toward your commitment.
What happens if we do not meet the EDP commitment?
You pay the shortfall. If actual usage falls below the committed floor in a period, you owe the difference as a true-up. That clause makes conservative sizing more important than the headline discount.
Does AWS Marketplace spend count toward the EDP commitment?
A defined portion of eligible AWS Marketplace purchases retires EDP commitment. Routing eligible third-party software through Marketplace can help you meet the floor with spend you were already planning.
Should we take an EDP or rely on Savings Plans and Reserved Instances?
They solve different problems and work together. Savings Plans and Reserved Instances lower your rates, while the EDP applies a discount in exchange for a spend commitment. Discounted spend still counts toward the EDP, so most large buyers use both.
When is the best time to negotiate an AWS EDP?
Negotiate with a bottom-up forecast in hand and aim to close near an AWS quarter or year end, when timing pressure favors the buyer. Settle the commit size, ramp, and shortfall terms before discussing the discount.
Want a second set of eyes on the commit number before you sign? Talk to our advisors.
Cloud Contract NegotiationRelated reading: the AWS Enterprise Agreement and EDP guide, AWS committed spend discounts, and cloud commit shortfall penalties. See also our ranking of the top software negotiation consulting firms.