What the AWS EDP Actually Is — and Is Not

The AWS Enterprise Discount Programme (EDP), formally known as a Private Pricing Agreement (PPA), is a contractual commitment to a minimum annual AWS spend in exchange for a percentage discount applied across eligible services. The EDP is not a procurement vehicle (you continue using your existing AWS accounts and billing structure), not a support tier (Enterprise Support is a separate subscription that EDP customers are required to maintain), and not a guarantee of any specific service pricing — AWS retains the right to change list prices, and discounts are applied as a percentage reduction to prevailing rates.

Understanding what the EDP is and is not matters because it determines where negotiation leverage actually exists. The discount rate is the primary commercial variable, but commitment structure, Marketplace inclusion, flexibility provisions, and service coverage breadth are equally negotiable — and often more impactful over the life of the agreement. Organisations that focus exclusively on the headline percentage routinely leave more value on the table in structural terms than they captured in the discount itself.

"We reviewed an EDP renewal where the customer had negotiated from 12% to 18% discount — a genuine win — but had accepted an annual true-up, no Marketplace headroom, and a ratchet commitment. The structural terms cost more over three years than the discount saved."

The Four Stages of a Successful EDP Negotiation

Stage 1: Usage Forensics — Know Your Numbers Before AWS Does

AWS account teams have access to detailed consumption data and growth forecasts for your accounts before the negotiation begins. Entering the room without an equivalent independent analysis means AWS is negotiating with better information than you are. A thorough pre-negotiation usage review should map actual consumption by service family over the past 12–24 months, identify growth drivers versus one-off spikes, model 12, 24 and 36-month spend scenarios under conservative, base and upside assumptions, and calculate the implicit discount available through Reserved Instances and Savings Plans — which reduces the incremental value of an EDP discount for committed compute spend.

Stage 2: Commitment Structuring — Build a Number That Reflects Reality

The commitment figure you table should be defensible from your own financial planning process, not derived by accepting AWS's growth projections. AWS account teams routinely use pipeline assumptions and sector benchmarks to suggest commitment levels that favour the programme economics. Your commitment should be based on: confirmed infrastructure roadmaps for the next 12–18 months, contracted application migration timelines, headcount growth plans that drive SaaS and compute consumption, and a conservative view of discretionary project spend that is genuinely uncertain. Ramp provisions — where year-one commitment is lower and scales up — protect organisations at early stages of cloud adoption from overcommitting to trajectory assumptions that have not yet been validated by execution.

Stage 3: Competitive Positioning — Use Multi-Cloud Reality Without Fabricating It

Genuine multi-cloud deployments or credible platform evaluations involving Azure or Google Cloud provide negotiating leverage in EDP discussions. AWS account teams are incentivised to retain and grow committed spend, and competitive displacement risk is a proven lever for improving both discount rates and structural terms. The critical discipline is deploying this lever credibly: AWS teams are experienced enough to distinguish genuine multi-cloud environments from theoretical alternatives, and overstating competitive alternatives risks damaging the relationship without producing commercial movement. If you have real Azure or GCP footprint, use it explicitly. If you have a genuine evaluation underway, reference it with specifics. Vague competitive threats rarely move the needle.

Stage 4: Consolidation Strategy — Aggregate Spend for Scale Discounts

EDP discounts scale with commitment size. Organisations with AWS spend distributed across subsidiaries, business units or acquisition targets that have maintained separate AWS accounts should evaluate spend consolidation ahead of EDP negotiation — combining commitments into a single organisational agreement unlocks discount brackets that no individual unit would qualify for independently. This consolidation exercise also provides a credible basis for a higher commitment level, which in turn supports a stronger discount request.

Free Guide: AWS EDP Negotiation Playbook

Commitment modelling framework, discount benchmarks by spend tier, negotiation sequencing guide, and the structural provisions to secure before signing — download in under 60 seconds. Download Free Guide →

What Typically Moves — and What Does Not

In our experience across 200+ AWS commercial engagements, the elements of an EDP that AWS will consistently improve with appropriate preparation are: the headline discount rate (when supported by credible commitment modelling and competitive context); the Marketplace inclusion threshold (from the default 25% to 30–35%); true-up cadence (from annual to quarterly); and service coverage breadth (ensuring newer service families are included in discount coverage from day one).

Elements that require specific business justification and are less routinely available include: commitment reduction provisions (available for material M&A uncertainty or regulatory risk); multi-year discount lock-in protection against future list price changes; and credits for specific infrastructure migration workloads. Understanding the distinction enables a negotiation strategy that focuses effort on achievable objectives rather than burning credibility on structural requests that require exceptional circumstances to unlock.