AWS committed-spend discounts under an Enterprise Discount Program or private pricing agreement typically run 5 to 23 percent off on-demand, scaling with commitment size: a $1M per year commit earns 5 to 8 percent, a $10M commit earns 10 to 15 percent, and a $50M-plus commit reaches 17 to 23 percent, layered on top of Savings Plans and Reserved Instance discounts. The committed-spend discount is the flat percentage AWS applies to almost all eligible usage in exchange for a multi-year dollar commitment. It is the single largest contractual discount most enterprises hold with AWS, and it is the one most often sized wrong.
What committed spend means
A committed-spend discount is a contractual agreement to spend a minimum dollar amount on AWS over a defined term, usually one to five years, in return for a flat percentage discount on eligible usage. AWS packages this as the Enterprise Discount Program (EDP) for larger customers. The commitment is a floor, not a cap: you agree to spend at least the committed amount, and if you spend more, the discount continues to apply. The risk lives entirely in the floor, because falling short does not reduce what you owe.
The discount applies broadly across compute, storage, database, networking, and most managed services. It does not stack on top of every line; some marketplace purchases and third-party charges are excluded or count toward the commitment at a reduced rate. Understanding what counts toward the commitment, and what receives the discount, is the core of the negotiation.
EDP discount tiers by commitment size
| Annual commitment | Typical discount | Common term | Negotiation note |
|---|---|---|---|
| $1M to $5M | 5 to 8 percent | 1 to 3 years | Entry EDP, limited room |
| $5M to $10M | 8 to 12 percent | 3 years | Ramp terms become negotiable |
| $10M to $25M | 10 to 15 percent | 3 to 4 years | Credits and PPA add-ons available |
| $25M to $50M | 14 to 19 percent | 3 to 5 years | Service-specific discounts layer in |
| $50M+ | 17 to 23 percent | 4 to 5 years | Bespoke, executive-sponsored |
These bands reflect negotiated outcomes, not a published rate card; AWS does not publish EDP discounts. The discount is a function of commitment size, term length, growth story, and competitive pressure from Azure or Google Cloud in the account. A credible multi-cloud alternative is worth more to the discount than any single contractual argument.
How it stacks with Savings Plans and RIs
The committed-spend discount and resource-level commitments are different layers, and they combine. Savings Plans and Reserved Instances reduce the rate on compute; the EDP discount then applies a further flat percentage on the already-reduced bill. The order matters for modeling: a workload on a 3-year Savings Plan at 50 percent off on-demand, inside a $20M EDP at 13 percent, pays roughly 0.5 times 0.87, about 43.5 percent of on-demand. Treating the layers as additive overstates the saving and leads to over-commitment. See our AWS Savings Plans guide and Reserved Instances guide for the compute layer, and the EDP pillar for the full stack.
The shortfall trap: The most expensive EDP mistake is over-committing on an aggressive growth forecast. If your committed annual spend is $15M and actual eligible spend lands at $11M, you still owe the $15M; the $4M shortfall is pure loss with no discount benefit. Negotiate a back-loaded ramp that matches the commitment curve to realistic adoption, a shortfall true-forward that lets unmet commitment roll into a later year, and exclusion clarity so that marketplace and third-party spend you expected to count actually counts.
Marketplace and what counts toward commitment
AWS Marketplace purchases can count toward EDP commitment, which is a powerful and underused lever: routing third-party software through Marketplace lets that spend retire the AWS commitment instead of sitting outside it. Not all Marketplace transactions count at full value, and the rules differ by contract, so confirm the treatment in writing before assuming a large software purchase will offset the commitment. Our AWS Marketplace procurement strategy covers how to structure this.
Multi-year ramp structures
The commitment is rarely a flat annual number. AWS structures most EDPs as a ramp, where the committed spend rises year over year to match expected growth, and the structure of that ramp is one of the most consequential terms in the agreement. A front-loaded ramp commits you to high spend early, before your migration has caught up, and is where shortfalls originate. A back-loaded ramp keeps early commitments below realistic consumption and pushes the larger numbers into years when your usage will plausibly support them. Because the discount is usually set against the total commitment, you can often hold the headline discount while reshaping the ramp to reduce shortfall risk, which is close to free money for the buyer who asks.
| Year | Front-loaded commit | Back-loaded commit | Realistic spend |
|---|---|---|---|
| Year 1 | $12M | $7M | $8M |
| Year 2 | $14M | $12M | $13M |
| Year 3 | $16M | $23M | $22M |
| 3-year total | $42M | $42M | $43M |
Both ramps total $42M and earn the same discount, but the front-loaded version overshoots realistic spend by $4M in year one while the back-loaded version tracks it closely. Matching the ramp to the adoption curve is the difference between a clean three-year run and an early shortfall that the buyer eats.
True-up, overage, and rollover
Three mechanics govern what happens when actual spend diverges from the commitment, and each is negotiable. Overage, where you spend more than the committed amount, is the good case: the discount continues to apply to the excess, and a well-negotiated EDP confirms that explicitly rather than capping the discount at the commitment. Shortfall, where you spend less, is the costly case, and the default treatment is that you owe the difference. A true-forward or rollover clause softens this by letting unmet commitment carry into a later year instead of being lost, converting a hard penalty into a timing problem. The third mechanic is the annual reconciliation, which sets when AWS measures your spend against commitment; aligning that measurement to your fiscal calendar avoids surprises at the wrong moment.
Common modeling errors
Most committed-spend value is lost not at the negotiating table but in the modeling that precedes it. The first error is treating the EDP discount as additive to Savings Plan and Reserved Instance discounts rather than multiplicative, which overstates the blended saving and tempts a larger commitment than the real economics support. The second is forecasting on the optimistic adoption curve the cloud team wants rather than the conservative one the migration will actually deliver, which manufactures shortfall. The third is ignoring which spend counts toward commitment: marketplace purchases, third-party charges, and certain managed services may count at reduced value or not at all, so a forecast built on gross AWS spend can overshoot the eligible base. Build the model on eligible, discounted, conservatively forecast spend, and the commitment will size itself correctly.
How AWS sizes the commitment
Understanding how AWS arrives at its proposed commitment is what lets a buyer push back credibly. The AWS account team builds the commitment from your trailing usage, your stated growth plans, and the migration pipeline they can see, then proposes a number sized to capture as much of your future spend as the discount can justify. The incentive is asymmetric: AWS benefits from a larger commitment because shortfalls accrue to the customer, while the customer benefits from a smaller commitment that the real consumption will comfortably exceed. The number AWS proposes is therefore an opening position calibrated to the vendor's interest, not a neutral forecast. Treat it as the starting point of a negotiation and rebuild it from your own conservative model, because the gap between the optimistic and conservative forecasts is exactly the shortfall risk you would be absorbing.
The second thing to understand is timing. AWS, like most vendors, has quarterly and annual targets, and the discount available late in a quarter or fiscal year is often deeper than the same deal mid-period. Aligning the commitment negotiation to AWS's calendar, and being willing to wait, can move the discount by several points. The full sequence is detailed in our EDP negotiation guide.
Frequently asked questions
What happens if I exceed my committed spend?
The discount continues to apply to the excess, so overage is the good case. A well-written EDP confirms this explicitly rather than capping the discount at the committed amount, which is a term worth verifying before signing.
What happens if I fall short?
By default you owe the difference between actual and committed spend, with no discount benefit on the shortfall. A negotiated true-forward or rollover clause can let unmet commitment carry into a later year, turning a hard penalty into a timing issue.
Does Marketplace spend count toward the commitment?
Often yes, though sometimes at reduced value, which makes routing third-party software through Marketplace a way to retire commitment. Confirm the treatment in writing, because it varies by contract and materially affects how large a commitment you can support.
Co-terming with existing commitments
Few enterprises sign their first EDP on a clean slate. Most already hold Reserved Instances, Savings Plans, and sometimes a prior EDP, all on different end dates, and how those existing commitments align with a new committed-spend agreement affects both the discount and the administrative burden. Co-terming, aligning the end dates so commitments expire together, gives a single clean renewal point where the whole relationship is renegotiated at once with maximum competitive tension, rather than a series of small renewals that AWS can pick off individually. The trade-off is that co-terming sometimes means extending or shortening an existing commitment to reach the common date, which carries its own cost. Model the alignment deliberately: a single annual renewal where compute commitments, the EDP, and any private pricing all come up together is worth more at the negotiating table than a fragmented calendar, because it concentrates your spend and your alternatives into one conversation. The existing Savings Plan and Reserved Instance positions also count toward how AWS sizes the new commitment, so bring a full inventory of current commitments into the negotiation rather than letting AWS reconstruct it from usage data alone.
How to negotiate the committed-spend discount
Anchor on the commitment size first, because the discount follows it, and size the commitment to a conservative consumption forecast rather than the optimistic one AWS will encourage. Negotiate the ramp so early-year commitments stay below early-year spend. Push for the highest term you are confident in, since longer terms earn deeper discounts, but protect against lock-in with an off-ramp tied to material service changes. Bring a credible alternative to the table; the discount moves on competitive tension more than on any other factor. The full negotiation sequence is in our AWS EDP negotiation guide, and the engagement model is our cloud contract negotiation service. For estates weighing the commitment against egress and support costs, see AWS egress negotiation and AWS enterprise support cost.