AWS EDP: the complete negotiation guide.

The AWS EDP is sized for a forecast that never arrives

The AWS EDP, the Enterprise Discount Program, also called a Private Pricing Agreement, trades a multi year spend commitment for a discount off list. That is the whole deal, and it is a good deal only if the committed number is right. As of June 2026 an EDP is a spend commitment over a one to five year term that unlocks tiered discounts scaling with the committed amount. It is typically available from around one million dollars of annual spend, with dedicated account attention usually arriving nearer five million. We read these agreements from the buyer side only. We take no reseller margin, no AWS incentive, and we are paid only by you.

The problem is never the discount. The problem is the commitment it is attached to. AWS sizes the EDP from an optimistic growth curve, prices the discount against a list rate you would never actually pay, and stacks the commitment on top of Reserved Instances and Savings Plans you already hold. The result looks generous and commits you to spend you may never reach. This guide rebuilds the EDP from real consumption and shows you where to apply pressure before you sign.

This page is the hub for everything we publish on the AWS EDP. It walks through the mechanics, the eligibility, the levers, and the traps, and links to a detailed guide on each. Start with the section that matches your deal, and find the full library at the foot of the page. If you want the broader context, the cloud commitment negotiation playbook sets out the principles that apply across every provider.

How AWS EDP discounts actually work

EDP discounts are tiered. The larger the amount you commit across the term, the deeper the discount AWS will offer. That structure is designed to pull your commitment upward, because each tier dangles a slightly better rate just above the number you had in mind. The discount also applies against list pricing, so a headline percentage can mean far less once your real effective rate, after Reserved Instances and Savings Plans, is taken into account. See how AWS EDP discounts actually work and how AWS calculates EDP discount tiers.

The right way to read a tier is to ask whether you can reach it without overcommitting. A deeper rate at a commitment you will not consume is not a saving, it is a shortfall waiting to happen. We model the tiers against your real forecast so you can see which one is genuinely within reach and which one is bait. See AWS EDP discount benchmarks by commitment size to judge the rate against what comparable buyers achieve.

Eligibility, minimums, and when to ask

As of June 2026, an EDP is generally available from around one million dollars of annual AWS spend, and you usually have to ask for it rather than wait for an offer. Dedicated account attention tends to arrive nearer five million dollars of annual spend. If you are approaching either threshold, the time to prepare is before AWS frames the conversation for you. See AWS EDP minimum spend and eligibility explained.

A first EDP is a different negotiation from a renewal. You have no prior agreement to anchor against and less history with the account team, which makes an independent benchmark more valuable, not less. See how to negotiate your first AWS EDP and, if you are weighing the naming, AWS EDP vs Private Pricing Agreement explained.

The traps that cost buyers the most

• 01Overcommitment, the single most common mistake, where the committed amount exceeds what you will consume and the gap becomes a shortfall you pay.
• 02A front loaded ramp that commits spend before your migration or growth lands.
• 03Service exclusions and carve outs that shrink the effective discount below the headline.
• 04Marketplace spend counted toward the number, then quietly narrowed in scope later.
• 05A term longer than the workloads the commitment is meant to fund, extending your lock in.

An EDP shortfall is the buyer obligation. If you commit one hundred million across the term and consume eighty, you generally owe against the gap. That is why overcommitment and shortfall penalties deserve more attention than the discount percentage.

Sizing the commitment and shaping the ramp

Everything in an EDP follows from the committed number, and the committed number should follow from your real consumption, not the seller forecast. Build the model from your run rate, your committed roadmap, and a conservative view of growth, then size the commitment so a realistic downside still clears it. See forecasting spend before signing an AWS EDP.

The ramp is the second half of sizing. A front loaded ramp commits spend before your workloads arrive, turning a timing risk into a shortfall. A back loaded, evidence based ramp tracks consumption instead of leading it. See negotiating a ramp structure into your AWS EDP, and weigh how growth profile changes the calculus in AWS EDP for high growth vs flat workloads.

Stacking, Marketplace, and credit application

The EDP stacks on top of Reserved Instances and Savings Plans rather than replacing them. A buyer who does not model that interaction can commit to a number their existing coverage already satisfies, paying for a discount on spend that was already discounted. See stacking EDP with Reserved Instances and Savings Plans.

Marketplace inclusion and cross account credit application are negotiable, and both are worth pushing for. Counting eligible Marketplace spend toward the commitment makes it easier to clear, and applying credit across linked accounts ensures the discount reaches your whole organization. See including AWS Marketplace in your EDP discount and credit application across linked accounts.

Exclusions, multi account structure, and consolidation

Service exclusions quietly shrink your effective discount, because spend that does not qualify still counts toward your bill but not toward your savings. Knowing what to exclude from the commitment, and what carve outs to resist, protects the rate you are actually getting. See what to exclude from an AWS EDP commitment and negotiating EDP service exclusions and carve outs.

For enterprises with many AWS accounts, structure matters. How the commitment applies across a multi account organization, and whether separate agreements should be co termed or consolidated, can change both the discount and the administrative burden. See AWS EDP and multi account organizations and co term and consolidation strategies.

Term length and renewal leverage

AWS will offer one, three, or five year terms, and a longer term usually buys a deeper discount. It also extends your lock in and removes the leverage you will want at the next negotiation. The right term is a buyer decision about flexibility versus rate, not a default. See AWS EDP term length.

As of June 2026, renewal leverage is greatest in the window six to nine months before expiry, so a renewal handled early becomes a negotiation rather than an automatic continuation. Plan the exit path even if you intend to renew, because a credible willingness to not renew is what gives the renewal its leverage. See AWS EDP renewal strategy and exit and non renewal planning.

Using competing quotes and reading the paper

A documented quote from Azure or GCP is one of the strongest levers in an EDP negotiation, because it turns your alternative from a threat into evidence. Used carefully, it gives AWS a concrete reason to improve the number. See how to use Azure and GCP quotes as EDP leverage.

When the agreement arrives, the detail is in the addendum, and the detail is where money moves. Reading it line by line, and understanding the annual true up and reconciliation, prevents surprises at the end of each year. See reading the AWS EDP addendum line by line and true up and annual reconciliation. If circumstances change, understand whether a mid term renegotiation is realistic.

Common mistakes and why independence helps

The recurring EDP mistakes are predictable. Buyers commit to the seller forecast, chase a deeper tier they cannot reach, ignore the ramp and the exclusions, and treat renewal as a formality. Each is avoidable with preparation and a benchmark. See common AWS EDP negotiation mistakes and the EDP negotiation FAQ.

Independence changes the outcome because our interest matches yours. A reseller earns margin on the spend you commit. We do not. We take no reseller margin and no AWS incentive, and we are paid only by you, so the only number we are working toward is the leanest commitment that still serves your roadmap. A confidential review before you sign is where that work begins.

What the EDP actually buys, and what it costs

An EDP buys two things, a lower rate and a relationship. The lower rate is the visible benefit. The relationship, the dedicated account attention that tends to arrive nearer five million dollars of annual spend, is the quieter one, and it cuts both ways. A senior account team is a useful channel for credits, support, and escalation, but it is also the team whose job is to grow your commitment at every turn.

The cost is optionality. A signed EDP removes your ability to walk for the length of the term, and that loss of leverage is the real price of the discount. The discount is worth taking. The lock in is worth minimizing. Most of our work is widening the first while narrowing the second, so you keep the saving without surrendering the position you will want at renewal.

Modeling the downside before you commit

The number that protects you is not the forecast, it is the downside. We model what your AWS spend looks like if a migration slips, a product underperforms, or a workload moves to another platform, and we size the commitment so even that case clears the committed amount. A commitment that only works if everything goes right is a shortfall with a delay.

This is also where existing coverage is reconciled. Reserved Instances and Savings Plans already discount a portion of your spend, and the EDP stacks on top of them rather than replacing them. We separate net new committed spend from coverage you already hold, so the committed baseline reflects genuine commitment and not a number you would have spent anyway.

Marketplace and eligible spend as a clearance lever

One of the most useful levers in an EDP is what counts toward the commitment. Negotiating broad eligible spend, including qualifying AWS Marketplace purchases, makes the committed number easier to clear and lowers your shortfall risk without changing the headline. A buyer who treats eligibility as a primary term, not a footnote, often gains more than from a point of extra discount.

Marketplace treatment is frequently offered generously at signature and narrowed later, so the scope needs to be pinned down in writing before you sign. We work the eligible spend definition deliberately, because it is one of the few levers that reduces both your rate and your risk at the same time.

How a Cloud Commitment Advisory EDP engagement runs

We begin by reconstructing your true consumption and separating it from existing coverage, then we benchmark the offer against what comparable buyers achieve at your commitment size. That gives you an immediate read on whether the rate is market and whether the committed number is reachable.

From there we build the position, the forecast, the ramp, the eligible spend, the exclusions to resist, and a credible alternative drawn from competing providers. We brief your team and either coach your negotiation or run the commercial exchange alongside your procurement lead. The aim is a documented, defensible EDP that you shaped, condensed before signature and built to hold its value through the term and into renewal.

A timeline that keeps the leverage on your side

The strongest EDP negotiations run on a timeline. Six to nine months before you need the agreement, you establish the real forecast, reconcile existing coverage, and decide the commitment you would accept. In the middle stretch you open the conversation on your terms and test the provider appetite without committing. In the final weeks you hold the position and use any calendar leverage the seller quarter offers.

Compress that and the advantages erode. A buyer with two weeks has no alternative to point to, no time to model the downside, and no room to walk. AWS account teams read that on the first call. For a renewal the same logic applies, which is why the leverage window opens six to nine months before expiry, not in the final month.

Reading the EDP as a structure, not a percentage

An EDP proposal is a structure, and the structure is where the cost hides. The committed amount, the ramp, the term, the eligible spend, the service exclusions, and the renewal language each carry value, and a concession on one can be recovered on another. A buyer who negotiates only the discount percentage leaves most of the deal untouched.

This is why we read these agreements line by line and model the whole structure rather than the headline. The discount is one variable among several, and rarely the one that moves the most money over the life of the term. The detailed guides in this cluster break each element down so you can see where your real exposure sits before you sign, and the FAQ collects the questions buyers ask most often.

From guide to result

The way to use this page is to start with your own EDP and follow the section that matches your situation into the guide beneath it. A first time buyer works the forecast, the eligibility, and the benchmark. A renewing buyer works the timing and the exit path. A buyer under budget pressure works the structure so a smaller commitment still earns a fair rate. Whatever the case, the sequence holds. Size from your evidence, shape the ramp to consumption, broaden eligible spend, resist unnecessary exclusions, and keep a credible alternative in view.

If you would rather not run it alone, that is what we are for. We bring the buyer side pressure, the benchmarks, and the experience of reading EDP agreements hundreds of times, applied entirely to your outcome and paid for only by you. Condense the EDP before you sign, and it stays condensed through the term.

The full AWS EDP negotiation library

Every guide in the AWS EDP cluster, written from the buyer side. Start with the mechanics, then work the levers and traps that match your deal.

• What is the AWS Enterprise Discount Program
• How AWS EDP discounts actually work
• AWS EDP minimum spend and eligibility explained
• How to negotiate your first AWS EDP
• AWS EDP shortfall penalties and how to avoid them
• Negotiating a ramp structure into your AWS EDP
• AWS EDP term length: 1, 3 or 5 years
• Stacking EDP with Reserved Instances and Savings Plans
• Including AWS Marketplace in your EDP discount
• AWS EDP renewal strategy: start 6 to 9 months early
• How AWS calculates EDP discount tiers
• AWS EDP vs Private Pricing Agreement explained
• Reading the AWS EDP addendum line by line
• AWS EDP credit application across linked accounts
• What to exclude from an AWS EDP commitment
• AWS EDP overcommitment: the most common mistake
• Forecasting spend before signing an AWS EDP
• AWS EDP discount benchmarks by commitment size
• Negotiating EDP service exclusions and carve outs
• AWS EDP and multi account organizations
• AWS EDP co term and consolidation strategies
• How to use Azure and GCP quotes as EDP leverage
• AWS EDP mid term renegotiation: is it possible
• AWS EDP exit and non renewal planning
• AWS EDP true up and annual reconciliation
• AWS EDP for high growth vs flat workloads
• Common AWS EDP negotiation mistakes
• AWS EDP negotiation FAQ: 20 buyer questions

Related buyer guides

• Cloud commitment negotiation: the buyer playbook
• Cloud commitment exit traps and lock in
• Azure MACC: the complete negotiation guide