Two Layers of Cost Optimization
AWS cost optimization happens at two layers that procurement teams routinely conflate. The first is FinOps: rightsizing instances, retiring idle resources, and buying Reserved Instances and Savings Plans against the workloads you keep. That work changes what you consume, and it belongs to engineering. The second layer changes the price and terms of the consumption you have already committed to — and it is negotiated directly with AWS's commercial team. These are the contract-side levers, and they are the ones enterprises most often leave untouched.
The distinction matters because the two layers interact. Every dollar you engineer out of the bill reduces the base your Enterprise Discount Program commitment is sized against; every percentage point you negotiate on the discount applies to whatever consumption remains. Optimise only the console and you discount a bloated bill. Optimise only the contract and you commit to spend you could have engineered away. The two have to be sequenced together — a theme that runs through our complete guide to cloud contracts.
The Discount Tier: Size and Term
The headline contract lever is the AWS Enterprise Discount Program rate itself. Baseline discounts for a $1M annual commitment typically run 6–9%, scaling with both commitment size and term. A three-year deal secures roughly 15% against about 10% for a one-year commitment at the same spend — the multi-year premium is real and worth modelling against your confidence in the spend forecast. The mechanics of how spend tier and term set the achievable rate are laid out in our pillar on multi-year cloud discount structures, with AWS-specific benchmarks in our EDP discount benchmarks by spend tier guide.
Two further dimensions of the discount are negotiable and routinely missed: breadth and depth. Breadth is which services the discount covers — coverage is itself a negotiated term, not a given, so a database- or container-heavy estate must confirm those services are in scope. Depth is whether a concentrated service warrants a service-specific Private Pricing Agreement on top of the blended rate, a choice we work through in EDP vs Private Pricing Agreement. Across 145 analysed EDP contracts, enterprises that negotiated these terms actively saved an average of $340,000 a year more than identical spend left on default pricing.
The Ramp: Sizing to the Downside
The commitment ramp is where most value is won or lost, because it sets the floor you are legally obliged to hit. In the majority of EDP deals we review, the opening commitment AWS proposes sits 15–30% above the customer's realistic spend curve — which quietly converts a discount into a shortfall true-up at term end.
The buyer-side move is a back-weighted ramp: set the year-one commitment below projected consumption, with steeper increases in years two and three as cloud adoption matures. This eliminates first-year shortfall risk while still giving AWS the multi-year revenue certainty it wants, and it is achievable in most EDP negotiations when requested explicitly. Size the commitment to the spend you will actually make, not the discount you wish you could earn.
An EDP commitment is a guaranteed minimum, not a target. The discount is only a saving if you consume the floor — otherwise you pay the difference anyway. Size to the downside, then negotiate the flexibility provisions that protect the gap.
Rollover, Cure Periods and Marketplace Retirement
Three flexibility provisions sit between a clean commitment and a punitive one, and each is available only to buyers who ask. Rollover lets you carry 10–15% of the annual minimum forward into the next commitment year; it applies once per year and does not compound, and rolled amounts unused in the receiving year are forfeited. A 90-day cure period following each anniversary lets qualifying spend — including late Savings Plan and Reserved Instance purchases and Marketplace spend — apply retroactively to the prior year's commitment, so the shortfall penalty applies only to the uncured balance.
The most underused provision is Marketplace retirement. Qualifying AWS Marketplace purchases count toward the EDP commitment, typically up to a cap of 20–30% of the annual minimum. As more enterprise software procurement moves through Marketplace, that provision alone can add $500K to $2M a year in qualifying spend that reduces structural shortfall risk — which is exactly why the cap and the qualifying categories should be negotiated, not accepted at default. The tactics for structuring those deals sit in our guide to AWS Marketplace private offers.
Shortfall: the Risk Nobody Models
The shortfall mechanism is the single largest financial risk in the EDP structure, and it is the one procurement most often discovers too late. Underconsumption does not reduce what you owe and does not roll forward by default: commit to $5M and consume $4.2M, and you owe the $800,000 difference as a true-up at the end of the commitment year. The discount you negotiated is irrelevant to that bill.
Treat shortfall as a modelled risk from the outset. Build the spend curve from real usage data, stress-test it against plausible downside scenarios — a delayed migration, a divested business unit, a workload refactored onto Spot — and size the commitment to that downside, not the optimistic case. Then stack the flexibility provisions above to protect the remaining gap. This is the same discipline we apply to commitment portfolios in our AWS Reserved Instances and Savings Plans portfolio strategy.
Sequencing the Negotiation
Order the work deliberately. First, run the FinOps layer: rightsize, retire idle capacity, and establish the genuine baseline so you are not negotiating a discount on waste. Second, model the spend curve and its downside, and size the commitment and ramp to that. Third, negotiate the discount breadth and depth, the back-weighted ramp, and the rollover, cure-period and Marketplace provisions as a package — not one at a time, where AWS can trade them off against each other.
The recurring mistake is treating the EDP as a discount to accept rather than a contract to negotiate. The discount percentage is the part AWS wants you to focus on; the ramp and flexibility terms are where the real money and risk sit. To model your own spend curve, size a defensible commitment, and pressure-test the flexibility provisions, request a confidential briefing or download the AWS EDP Negotiation Playbook.