AWS EDP Negotiation Playbook 2026

Executive summary

Size the AWS Enterprise Discount Program commitment to the spend you control, and the rest of the deal follows. The discount AWS offers is real, but it is priced against a committed floor that you pay whether or not you consume it. Buyers who bring a bottom-up forecast, back-load the ramp, route eligible Marketplace purchases against the commitment, and price their top services on a private rate card come out ahead of buyers who chase the headline percentage.

This playbook covers the full negotiation: how AWS constructs an EDP offer and where the risk actually sits, the twelve levers in the order that protects you, a six-month commit-sizing timeline, when a Private Pricing Agreement beats a flat discount, how Marketplace retirement and data transfer pricing work, the shortfall and overcommit mechanics, and how to hold the renewal to your own forecast rather than the account team's growth model. Every section leads with the action a buyer should take and names the contract mechanism that makes it stick.

Our advisors negotiate cloud agreements every week on the buyer side only. Across more than 500 enterprise engagements, the buyers we advise have negotiated over $2.4 billion in software and cloud contracts. The figures below summarize the record and the indicative shape of the market.

1. How AWS builds an Enterprise Discount Program offer, and where the risk sits

An EDP is a private agreement that layers a cross-service percentage discount on top of your AWS consumption in exchange for a committed minimum spend over a fixed term, most often three years. The discount is not published anywhere. It is set by the size of your commit, the length of the term, your growth trajectory, and how well you negotiate. Two companies with identical annual spend can sign materially different deals depending on structure alone.

The commitment is where the risk concentrates. You agree to a minimum spend, usually rising year over year through a ramp. If actual usage falls short of the committed floor in a period, you owe the difference as a true-up under the shortfall language in the agreement. That single clause is more expensive than any discount is valuable, and it is the reason sizing discipline beats percentage chasing in every deal we have run.

Read the offer the way the seller built it. The account team is measured on committed spend growth, not on your efficiency. The first proposal therefore carries a larger commit and a steeper ramp than your own data supports, with the discount framed as the reward for accepting both. AWS runs a fiscal year ending December 31, and quarter ends sharpen the account team's flexibility in a way a prepared buyer can use.

How the account team scores your deal

Inside AWS, an EDP proposal is evaluated on total committed dollars, year-over-year growth of the commitment, and term length. The discount your account team can offer expands as those three inputs rise, which is why every first proposal pushes all three at once. Knowing the scoring logic tells you what each concession costs the seller: a longer term is cheap for them to reward, a flat commitment is expensive, and shortfall protections cost them almost nothing when your consumption record is strong.

It also tells you who is in the room. Pricing beyond standard authority routes through a private pricing desk, not the account manager, and turnaround on revised terms is measured in weeks, not days. Build that latency into your timeline so the final quarter of the negotiation is not compressed into the final week, where pressure favors the side with the deadline that matters less. Your renewal date matters to you; the AWS quarter end matters to them.

The three documents that govern the deal

The EDP sits on top of the AWS Customer Agreement and the AWS Service Terms, with the EDP addendum carrying the commitment, the discount schedule, and the shortfall mechanics. Read all three together. The addendum controls the money, but eligibility questions, service exclusions, and Marketplace treatment trace back to the Service Terms. Ask for the current versions in writing before you negotiate, and keep the executed set with your contract record.

2. The EDP levers, sequenced: commit, ramp, term, Marketplace, and discount last

Discount is one lever of twelve, and it is the weakest place to spend negotiating power. The levers below are ordered by how much they protect the buyer over a full term. Settle each structural term before you let the conversation move to the percentage, because once the percentage is agreed the account team has no reason to concede structure.

The sequence is the strategy. A buyer who opens with the percentage signals that structure is conceded, and the account team will hold the floor and the ramp exactly where the first proposal put them. A buyer who opens with commit size, ramp shape, and shortfall language forces the structural conversation while the seller still has a quota reason to stay at the table.

3. The six-month commit-sizing timeline and where the saving comes from

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 must be built bottom up from workload plans rather than top down from last year's bill plus a growth percentage. The timeline below is the sequence we run with clients.

Building a forecast that holds up

A defensible forecast is assembled workload by workload, not as one blended number. For each material workload, record current monthly spend, the owning team, the growth or retirement plan, and a confidence rating. Sum the high-confidence tier and that is your committed base. The medium tier informs the ramp. The speculative tier, the proofs of concept and the unfunded initiatives, stays out of the commitment entirely, because the EDP discount still applies to consumption above the floor.

That last mechanic is the one buyers most often miss. You do not need to commit to spend for the discount to apply to it; you need the commitment only to earn the rate. Spend above the floor gets the same discount with none of the shortfall risk, so the rational floor sits at the bottom of your confidence range, not the middle. Let the account team argue you upward against your own evidence, and make every increment of floor buy a visible structural concession in return.

Where the saving actually comes from

The visible saving is the discount percentage applied to consumption. The larger and less visible saving is the shortfall you never pay because the floor was sized to reality, the ramp matched adoption, and Marketplace purchases retired commitment you would otherwise have scrambled to consume. In our engagements the structural side routinely outweighs an extra point or two of discount over a three-year term.

The chart below shows the shape that protects a buyer. The figures are an illustrative index, with the final-year floor set to 100, not a market benchmark.

4. Private pricing and rate cards: when service rates beat a flat discount

For organizations with concentrated spend, a Private Pricing Agreement can be worth more than the headline EDP percentage. A PPA sets negotiated rates on specific services, typically the ones that dominate the bill: EC2 compute, S3 storage, CloudFront delivery, or data transfer. Where two or three services drive most of the cost, a deep service-level rate beats a flat discount spread thinly across everything.

The analysis is straightforward. Rank your services by trailing twelve-month spend and by forecast growth. If the top three lines carry the majority of the bill, model a PPA rate card on those lines against the flat EDP discount on the whole. Run both against your forecast, not your history, because the rate card pays off most on the lines that grow.

How the two structures combine

A PPA and an EDP are not mutually exclusive, and large buyers often run both: a baseline EDP discount across all consumption with service-specific rates layered on the concentrated lines. The negotiation question is which structure carries the saving on which line, and the answer falls out of your own spend distribution. Bring that distribution to the table; the account team already has it.

5. Marketplace retirement and data transfer in the EDP

AWS Marketplace is the most underused instrument in EDP negotiations. A defined portion of eligible Marketplace purchases retires EDP commitment, which means third-party software you were going to buy anyway can count toward the floor. For a buyer carrying a large committed number, routing planned purchases of security tooling, observability platforms, or databases through Marketplace private offers converts an external cost into commitment progress.

Three disciplines make the Marketplace route work. First, confirm in the agreement which purchases are eligible and at what retirement rate, because eligibility is contractual, not assumed. Second, move renewals of existing third-party contracts to Marketplace private offers as they come up, since a private offer preserves your negotiated pricing while adding the retirement benefit. Third, track retirement against the floor quarterly, in the same review where you track consumption, so a projected gap is visible while there is still time to act on it.

Private offers are the mechanism that makes the routing practical. A Marketplace private offer lets the third-party vendor present your negotiated price, payment schedule, and custom terms through the AWS Marketplace channel, so you keep the commercial terms you fought for while the transaction itself counts where you need it. Most major security, data, and observability vendors transact this way today, and the ones that resist usually have a channel-conflict reason that is theirs to solve, not yours to fund.

Data transfer belongs in the negotiation

Egress is the line buyers most often treat as fixed, and it is not. If your architecture moves significant data out of AWS to users, partners, or other clouds, the egress line grows with the business and is a fair target for a private rate inside the PPA or the EDP package. Put your egress forecast on the table alongside compute and storage. A buyer who prices data transfer at signature avoids re-opening the agreement when a data-heavy workload scales.

6. Shortfall, the overcommit trap, and exit flexibility

The overcommit is the most expensive EDP mistake, and it is built in at signature, not discovered at true-up. It happens when the committed floor, especially in the later ramped years, exceeds what the business actually consumes. The shortfall clause then converts the gap into an invoice: you pay for cloud you never used, at the moment the business is consuming less than planned.

Protection is negotiated before signing or not at all. The table below pairs each risk with the contract term that softens it.

Carry-forward is the protection most worth fighting for. The ability to roll unused commitment into the next period converts a hard penalty into a timing question, and it costs AWS little to grant when the relationship is growing. Exit and reduction rights for divestitures matter most for PE-owned businesses and any enterprise with an active portfolio strategy; name the events in the contract rather than relying on a renegotiation that will happen under pressure.

The governance cadence that prevents the shortfall

Shortfall is an operational failure before it is a contractual one. The agreement sets the floor, but the consumption that meets it is produced by dozens of engineering teams making independent decisions all year. Connect the two. Give FinOps explicit ownership of commitment tracking, set a quarterly review that compares the floor, the run rate, and the Marketplace retirement balance, and define in advance what happens when the projection shows a gap: which planned purchases accelerate into Marketplace, which workloads come forward, and at what point procurement opens a conversation with AWS about restructuring rather than absorbing a true-up.

The same cadence protects you on the other side. If consumption is running far above the floor, you are leaving discount on the table, and that evidence funds a mid-term conversation about deepening the rate in exchange for extending the term. Both conversations go better when you raise them early, from data, on your own schedule.

7. Renewal: holding the commit to your own forecast

Renewal is where overcommitment compounds. The account team opens from your current committed floor plus growth, because committed spend growth is what they are measured on. A buyer who arrives without an independent forecast accepts that frame by default, and each renewal ratchets the floor further from reality.

Run the renewal as a fresh sizing exercise. Rebuild the bottom-up forecast from current workloads, planned migrations in both directions, and committed business change. Be prepared to hold the commit flat, or reduce it, when the data says so. A flat renewal from a position of evidence is a better deal than a grown renewal from a position of habit, and AWS accepts flat commitments from buyers who can show their math far more readily than the first conversation suggests.

Start the renewal conversation at least six months before expiry, on the same timeline as the original deal. Bring the shortfall and retirement history from the closing term: if you consumed comfortably above the floor, that record argues for a better discount at the same floor, not for a higher floor. If you ran close to shortfall, that record is your argument for restructuring the ramp. Either way, your own consumption history is the strongest negotiating document in the room, and only one side brings it by default.

The term sheet review: what to verify before signature

Before signature, walk the term sheet against the checklist below. Every row is a clause we have seen cost a buyer money when it was assumed rather than written. The verification column is the question your legal and procurement team should be able to answer with a clause reference, not a recollection of what the account team said.

None of this is adversarial. AWS negotiates these terms every day and respects buyers who do the same. The agreement you want is one both sides can administer without surprises, because the surprise clauses are the ones that surface three years later in front of your CFO.

Key takeaways

• The EDP discount is negotiable; the commitment floor is the real risk. Size it to spend you control.
• Sequence the twelve levers and negotiate the discount last, after structure is locked.
• Start six months out and spend the first half of that time on the bottom-up forecast.
• Price concentrated services on a PPA rate card instead of accepting only a flat percentage.
• Make Marketplace eligibility, retirement rate, and egress pricing explicit contract terms.
• Negotiate carry-forward, reduction rights, and named exit events before signature.
• Hold every renewal to a fresh forecast, with your own consumption history on the table.

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 cross-service discount on AWS usage. The percentage is private and scales with the size of the commitment, the length of the term, and the quality of your negotiation. Discounted spend still counts toward the commitment, so the discount and the floor interact in your favor when sizing is right.

What happens if we do not meet the EDP commitment?

You pay the shortfall. If actual usage falls below the committed floor for a period, AWS invoices the difference as a true-up. That clause makes conservative sizing and a back-loaded ramp more valuable than an extra point of discount, and it is the reason carry-forward language is worth negotiating.

Does AWS Marketplace spend count toward the EDP commitment?

A defined portion of eligible AWS Marketplace purchases retires EDP commitment. Routing planned third-party software purchases through Marketplace private offers helps you meet the floor with spend you were already going to make. Confirm eligibility and the retirement rate in your agreement before you rely on either.

Should we take an EDP or rely on Savings Plans and Reserved Instances?

Use both, layered in the right order. Savings Plans and Reserved Instances lower unit rates on specific resources, while the EDP discounts total spend in exchange for a commitment. Rate-discounted spend still retires the EDP floor, so the instruments stack: set the EDP commit first, then place Compute Savings Plans and Reserved Instances inside it by workload stability.

When is the best time to negotiate an AWS EDP?

Start six months before signature with a bottom-up forecast, and aim to close near an AWS quarter end or the December 31 fiscal year end, when timing pressure favors the buyer. Settle the commit size, ramp, and shortfall terms before you discuss the discount percentage.

Prefer to start with the service detail? See how our cloud contract negotiation service runs an EDP engagement end to end, or return to the AWS EDP Negotiation Playbook overview.

Related research

Three companion guides extend this playbook across the rest of a cloud portfolio: the Azure MACC Negotiation Guide applies the same sizing discipline to Microsoft consumption commitments, the Cloud Renewal Strategy Playbook covers the renewal cycle across AWS, Azure, and GCP, and the Google Cloud Negotiation Guide maps the equivalent commitment mechanics on GCP.