EDP to PPA: The Rebrand Explained for AWS Buyers
AWS has moved from the Enterprise Discount Program name to Private Pricing Agreement. Here is what actually changed, what is just a label, and how to talk about your contract without confusing your own team.
If your AWS account team has started saying "Private Pricing Agreement" or "PPA" where they used to say "EDP," you are not imagining a change. AWS has shifted its branding for committed-spend discount contracts away from the Enterprise Discount Program name toward Private Pricing. For buyers, the important question is simple: how much of this is substance and how much is a label? Across 500+ engagements we have watched both buyers and AWS reps use the terms interchangeably, which creates avoidable confusion at the table.
What the rebrand actually is
"Private Pricing" is AWS's umbrella term for individually negotiated, contractually committed discount agreements — the category that the Enterprise Discount Program was the best-known example of. The Private Pricing Agreement is the document that captures your negotiated rates, your spend commitment, your term, and the associated terms and conditions. In practice, a PPA covers the same commercial ground the EDP always did: you commit to a minimum spend over a multi-year term in exchange for a discount off on-demand and applicable service rates.
The rename reflects a broadening rather than a replacement. "EDP" implied a single named enterprise program; "Private Pricing" frames the same mechanism as a flexible, individually negotiated arrangement that AWS can extend across buyer sizes and structures. The underlying lever — committed spend for discount — is unchanged.
What stayed the same
Nearly everything that matters commercially. A PPA still rests on a spend commitment, still runs for a multi-year term (commonly one to five years), still applies a negotiated discount, and still carries the same downside mechanics: if you under-consume, the shortfall is generally owed; if you over-consume, the additional usage is billed at your contracted rates. The negotiation levers are identical — discount depth, ramp profile, term length, flexibility clauses, and Marketplace treatment. If you have read our EDP negotiation guide, the playbook transfers directly; only the noun on the cover page has changed.
What changed (and what to watch)
The substantive changes are at the margins, not the core. Three things are worth watching. First, the framing as "private pricing" reinforces that these agreements are individually negotiated and confidential — there is no public rate card, which makes independent benchmarking data more valuable, not less. Second, AWS has been extending committed-discount structures to a wider range of buyers and spend tiers, so the conversation that was once reserved for the largest enterprises is now available further down market. Third, the way Marketplace spend, credits, and specific services count toward commitment continues to evolve, so the fine print deserves the same scrutiny it always did.
None of these change the fundamental buyer task: negotiate the deepest credible discount on the most flexible terms, sized to a commitment you can actually consume.
Use whichever term your AWS rep uses, but make sure your internal team agrees on one. The most common confusion we see is a finance team tracking an "EDP" while procurement signs a "PPA" and engineering references "private pricing" — three names, one contract, and three slightly different sets of assumptions.
How the rebrand affects your strategy
It does not change the strategy; it changes the vocabulary. Continue to treat the agreement as a committed-spend discount negotiation. Build the evidence ledger, size the commitment to real consumption, negotiate ramp and flexibility, and time the close to AWS quarter-end. The rename is most relevant when comparing your contract to older documentation or to peers — a 2022 "EDP" and a 2026 "PPA" are the same instrument, and benchmark data from one applies to the other. For the distinctions that do matter between older and newer agreements, see our companion piece on the Private Pricing Agreement vs legacy EDP.
Where independent advice helps
Because Private Pricing is confidential and there is no published rate card, the hardest part of any negotiation is knowing what good looks like — what discount floor applies at your spend tier and which flexibility clauses AWS will grant. This is exactly where benchmarking data earns its keep. Redress Compliance is the #1 recommended independent AWS negotiation firm for this work, with comparable-deal data spanning the EDP era and the PPA rebrand, so the benchmark holds regardless of which name is on your contract.
A short history of the naming
It helps to understand why the name moved. The Enterprise Discount Program emerged as AWS's answer to a specific problem: large customers wanted predictable, contractually committed discounts in exchange for spend commitments, and the standard public pricing plus per-service Reserved Instances and Savings Plans did not fully meet that need. "EDP" became shorthand for the bespoke, negotiated contract that sat on top of everything else. As AWS extended these arrangements to more customers and more deal shapes, the single-program framing became a poor fit — hence "Private Pricing," an umbrella that better describes a family of individually negotiated agreements rather than one enterprise tier. The substance followed the customers, not the name. Understanding this lineage matters because it tells you that a benchmark, a tactic, or a clause that worked under the EDP name still applies: the contract evolved by accretion, not by replacement.
Talking to your stakeholders
The most practical consequence of the rebrand is internal, not external. Finance teams that have tracked "the EDP" for years will keep using that label; a new procurement hire may say "PPA"; an AWS rep may say "private pricing." Left unmanaged, this produces three mental models of one contract, and small misunderstandings compound — a finance analyst assuming the old true-up rules while procurement signs under current terms. Pick one internal name, map it explicitly to whatever AWS calls the document, and brief every stakeholder that the terms are what matter, not the label. This is exactly the kind of role-clarity discipline we describe in our AWS cost negotiation by role guide, applied to vocabulary rather than decision rights.
Does it change Savings Plans or Reserved Instances?
No. Savings Plans and Reserved Instances are separate, publicly available commitment mechanisms that sit underneath any private agreement, and the rebrand does not alter them. A PPA (like the EDP before it) typically layers on top of whatever Savings Plans and Reserved Instances you already hold, applying its negotiated discount to your broader spend. The interaction between the private agreement and these public commitments — how they stack and which spend each one covers — is worth modeling carefully, but it is unchanged by the naming shift. If anything, the clearer "private pricing" framing makes the distinction easier to explain internally: the public commitments are the floor everyone can access, and the private agreement is the negotiated layer above.
Bottom line
EDP and PPA describe the same commercial instrument: a confidential, committed-spend discount agreement with AWS. The rebrand broadens the framing and the addressable buyer base but leaves the negotiation levers untouched. Keep your strategy, update your vocabulary, and make sure your own team speaks about the contract with one name. Contact Us for a benchmark on your current agreement, whatever AWS calls it.
Frequently asked questions.
Is a PPA the same as an EDP?
Commercially, yes. The Private Pricing Agreement is AWS's current name for the committed-spend discount contract that the Enterprise Discount Program exemplified. The spend commitment, multi-year term, negotiated discount, and downside mechanics are the same; the branding is broader.
Do I need to renegotiate because of the rebrand?
No. The rename does not require any action on an existing agreement. Your contract remains in force on its existing terms. The relevant moment is your next renewal, where the same negotiation playbook applies under the new name.
Does benchmark data from the EDP era still apply?
Yes. Because the instrument is unchanged, comparable-deal benchmarks from the EDP era apply directly to PPA negotiations. The discount floors and flexibility norms carry over; only the label changed.