The Rename: What Actually Changed
Start with the headline most coverage buries: for the majority of customers, the AWS EDP vs Private Pricing Agreement distinction is now largely a naming question. Historically, the Enterprise Discount Program (EDP) was one large, enterprise-wide discount applied across your whole AWS bill, while a Private Pricing Agreement (PPA) was the term for private, service-level pricing. AWS has since unified these into a single modern deal approach and uses "PPA" for all private pricing contracts, regardless of scope.
The practical implication is liberating: if your old contract was labelled EDP and your renewal says PPA, nothing has changed except the name — the commercial structure is identical. Do not let an account team frame the rename as a new programme with new constraints. Focus on the discounts and commitments, not the label on the cover page. This article sits within our multi-year cloud discount structures framework and the AWS vendor intelligence hub.
Blanket vs Service-Specific Pricing
What still genuinely differs is the shape of the discount. A blanket cross-service discount applies a single percentage to qualifying consumption across all AWS services — simple, predictable, and the historical EDP model. A service-specific deal targets your highest-cost services with a deeper, custom rate, often in exchange for a volume sub-commitment on that service.
The lever matters most when a small number of services dominate your bill. AWS's own guidance gives the example: a customer with aggregate S3 storage of 15PB or more that agrees to grow that storage over the term can receive per-GB pricing far better than applying the platform discount to published S3 rates. If EC2 and S3 are the bulk of your spend, a deeper rate on those two services can beat a shallower discount spread thinly across everything you consume.
The trade-off is concentration risk. A service-specific deal usually carries a sub-commitment on the targeted service — you are promising not just total spend but a minimum volume of S3 or EC2. That is fine when the workload is genuinely committed and growing, but it narrows your flexibility: if you later re-architect off that service, the sub-commitment can turn into its own shortfall. A blanket discount, by contrast, does not care which services you consume, so it tolerates a changing workload mix without penalty. The right choice depends on how stable your service mix is, not just on where your spend sits today.
The cheapest agreement is rarely the one with the highest headline percentage. It is the one that produces the lowest effective rate against your actual usage mix — which is a modelling exercise, not a negotiation slogan.
EDP vs PPA Side by Side
Despite the convergence, it helps to hold the two historical models side by side when deciding what to ask for.
| Dimension | EDP (blanket model) | PPA (service-specific model) |
|---|---|---|
| Discount scope | One rate across all qualifying services | Deeper rate on targeted high-cost services |
| Best when | Spend is spread across many services | A few services dominate the bill |
| Commitment basis | Total AWS spend over term | Often a service-level volume sub-commitment |
| Typical entry | ~$1M+ annual spend | $500K–$1M annual spend |
| Indicative discount | 5% to 20–25%+ by spend tier | Can exceed the platform rate on the target service |
| Current AWS label | Issued under the PPA name | Issued under the PPA name |
For the underlying discount-by-spend curve that applies to both, see our AWS EDP discount benchmarks, and for the broader process read the AWS enterprise agreement negotiation guide and our existing AWS EDP negotiation guide.
Combining Both Structures
The structures are not mutually exclusive, and the best outcome often layers them. If your existing agreement provides 20% across all services, negotiating a service-specific rate of 30% on EC2 and S3 — your highest-cost services — improves your overall effective discount without disrupting the base agreement. The discipline is to model both your blended and your service-specific options against your real bill and choose whichever combination produces the lowest effective rate. You can stress-test the discount range either approach should target with our cloud commitment discount calculator.
Traps in the EDP-to-PPA Transition
Because the rename happened mid-stream, the renewal conversation is where buyers get caught. The first trap is anchoring: an account team may present the new PPA as a fresh programme with its own opening discount, quietly resetting the negotiation to a worse starting point than your existing EDP rate. Treat your current effective rate as the floor — a renewal should improve on it, not restart from list. The second trap is scope creep on the commit: a service-specific PPA can carry a sub-commitment that, combined with your total-spend commitment, leaves you doubly exposed if either falls short. Read both commitment lines and model them together.
The third trap is term lengthening. Providers often pair the rename with an offer of a longer term at a marginally deeper discount. The extra points are real, but so is the reduced flexibility — and an unfamiliar PPA structure is exactly the wrong moment to lock in five years. Separate the two decisions: agree the structure and effective rate first, then decide the term on its own merits against your forecast confidence, as covered in the multi-year cloud discount structures guide.
Which to Negotiate
Ignore the acronym and decide on structure. If your spend is genuinely diversified across many services, a blanket discount is simpler and captures most of the value. If two or three services carry the bill, push for service-specific pricing on those — and, where possible, layer it on top of a base blanket rate. Private pricing typically becomes available around $500K–$1M of annual spend; below that, partner-led commitments or Savings Plans may be the more practical route.
A practical test settles most cases. Pull your trailing twelve months of spend by service. If the top two or three services account for more than roughly 60% of the bill and are stable or growing, model a service-specific deal on those — the deeper targeted rate usually wins. If your spend is spread across a long tail of services, or your architecture is actively changing, a blanket discount captures most of the value with far less commitment risk. When in doubt, ask AWS to quote both and compare effective rates against your real usage rather than headline percentages.
Whatever the shape, the negotiation fundamentals are unchanged: size the commit to a realistic spend curve, structure a back-loaded ramp to protect Year 1, and confirm Marketplace drawdown eligibility — AWS allows up to 25% of a commitment to be retired through qualifying Marketplace purchases under either structure. For the full AWS playbook, download the AWS EDP Negotiation Playbook, or request a confidential briefing and we will model the blanket-versus-service-specific options against your actual usage before you respond to AWS.