What an AWS Enterprise Agreement Is
The AWS enterprise agreement negotiation most buyers mean is a private pricing commitment — historically the Enterprise Discount Program (EDP), and increasingly issued under the Private Pricing Agreement (PPA) label. The structure is the same: you commit to a minimum total AWS spend over a one-, three- or five-year term, and AWS applies a percentage discount to qualifying consumption. The discount tiers are private and unpublished, so the agreement is only as good as the benchmark data you bring to it. This guide sits inside our wider multi-year cloud discount structures framework and the AWS vendor intelligence hub.
Sizing the Commit
The commit is the riskiest number in the agreement, because AWS's standard tactic is to offer a higher discount on a higher commit rather than meeting your requested discount at your requested commit level. A higher discount on an over-commit is worse than a lower discount on a right-sized commit — the maths only works if you actually consume the committed spend.
Before you name a number, clean the house. A forensic review of current usage — eliminating orphaned resources, idle instances and over-provisioned reserved capacity — lets you commit to a lower, more efficient baseline. Most enterprises find 10–20% of current spend is removable waste; committing on top of that waste simply locks it in for the term. Build the commit from a conservative bottom-up forecast of EC2, S3, RDS and your other core services, not from last year's gross bill.
The cost of getting this wrong is concrete. AWS commitments are typically proposed 15–30% above the customer's realistic spend curve, and any shortfall is paid back at the end of the term at full published rates. Commit to $10M a year and consume $8M, and you lose the discount on the $2M gap — a $200,000–$500,000 penalty depending on your discount rate. That is the entire benefit of the agreement, handed straight back. The discipline is to separate the spend you are confident you will make in a downside scenario (the floor) from the spend you merely hope to make (the upside), and commit only to the floor.
Watch for the eligibility framing, too. EDP eligibility generally begins around $1M–$3M of annual AWS spend, and AWS routes accounts above roughly $10M to its large-enterprise and strategic teams — which is where the deeper discounts and more flexible structures actually live. If you sit near a threshold, projected growth can move you into a better-resourced negotiating track, so present a credible forward forecast rather than only trailing spend.
Discount Benchmarks
The following 2026 benchmarks reflect observed enterprise outcomes. AWS will not confirm them, so treat them as the reference for what is achievable rather than a rate card.
| Annual commitment | Indicative discount | Notes |
|---|---|---|
| $500K – $2M | 5–8% | Entry tier; PPA more common than full EDP |
| $5M | ~10% | Pricing steps near $1.5M, $2M, $5M |
| $10M – $20M | 13–18% | Strategic accounts team engaged above ~$10M |
| $50M+ | 20–25%+ | Deepest discounts and custom structures |
Term is the second axis: at the same spend, a three-year agreement is worth roughly five percentage points more than a one-year deal, and five-year structures carry more again. For the full discount-by-spend curve, see our AWS EDP discount benchmarks, and for the EDP-versus-PPA distinction read AWS EDP vs Private Pricing Agreement. Our existing AWS EDP negotiation guide walks the end-to-end process in more depth.
AWS will counter a discount request with a bigger commit at a bigger headline discount. Model the effective rate against your realistic spend, not the committed spend — the discount you keep is the only one that counts.
The Back-Loaded Ramp
The ramp — the schedule of minimum spend across the term — is the single highest-risk element of most AWS agreements. AWS's standard proposal is flat or front-loaded, which creates shortfall risk in Year 1 before a migration has caught up. A back-loaded ramp fixes this: set Year 1 at 60–70% of target, Year 2 at about 85%, and Year 3 onward at 100%, keeping the total term commitment unchanged. The annual distribution shifts to match adoption reality, cutting first-year shortfall risk to near zero.
AWS's commercial team has internal flexibility to approve back-weighted ramps — particularly for customers running significant on-premises migrations — but will not offer the structure proactively. You must request it explicitly. In one engagement, a mid-market software company about to sign a $4.2M agreement with an aggressive Year 1 ramp had a 28% shortfall risk identified before signing; restructuring the ramp removed roughly $840,000 of penalty exposure while preserving the headline discount.
Marketplace Drawdown
AWS allows up to 25% of an EDP commitment to be retired through qualifying AWS Marketplace purchases. This is one of the most underused levers in the agreement: third-party software you were going to buy anyway can be routed through the Marketplace to draw down your commitment, raising commitment retirement by 10–25% and making an aggressive committed number far easier to meet. Confirm in writing which Marketplace categories are eligible before signing — the definition varies by deal and materially changes how achievable your floor is.
Used well, this reframes the whole commitment. If a fifth of your committed number can be met with software licences you already intended to buy, the effective consumption you actually need to generate on AWS infrastructure drops accordingly — which means you can accept a higher headline commitment, and the deeper discount that comes with it, without raising your real shortfall risk. Map your planned third-party software spend against the eligible Marketplace catalogue before you finalise the commit, not after.
Running the Negotiation
Sequence the negotiation deliberately. Open with your cleaned-up utilisation baseline so the commit is anchored to efficient consumption, not gross spend. Present independent benchmark data as the reference for the discount, rather than negotiating against AWS's opening offer. Request the back-loaded ramp and Marketplace drawdown as structural terms, not afterthoughts. And time the close to AWS's quarter-end, when its account team carries its own deadline pressure.
Negotiate flexibility as hard as you negotiate the discount. None of the provisions that protect you are standard terms: a cure period before any shortfall true-up is charged, the right to extend the term to absorb unused commitment rather than forfeit it, and the ability to reallocate budget across services or business units if one project underconsumes. These clauses convert a rigid commitment into a manageable one, and they cost AWS little to grant if you ask while the discount is still being negotiated rather than after the commercial terms are settled.
Be deliberate about who is in the room. AWS account teams are practised at reading disagreement between a customer's stakeholders and pricing to the most optimistic voice. A single empowered negotiating lead, working from one agreed position document, consistently outperforms a committee that negotiates live in front of the vendor.
Most importantly, avoid committing above the floor you can defend in a downside scenario. For the deeper AWS-specific playbook — negotiation sequence, benchmark tables and flexibility-clause language — download the AWS EDP Negotiation Playbook. If you are sizing a commitment this year, request a confidential briefing and we will model your floor against current benchmark data before you respond to AWS.