AWS EDP vs PPA: What Is the Difference in 2026?

The Bottom Line: EDP and PPA Are the Same Thing

AWS's Enterprise Discount Program (EDP) and Private Pricing Agreement (PPA) describe the same commercial programme. Both refer to a privately negotiated enterprise agreement where an organisation commits to a minimum level of AWS spend over a defined term (typically 1-5 years) in exchange for a discount applied across all AWS services. The terms are used interchangeably by AWS account teams, AWS documentation, and enterprise procurement teams — and since approximately 2023, AWS has standardised on "PPA" as the preferred label.

If your existing contract is called an EDP and a colleague's is called a PPA, the underlying commercial structure is the same: a spend commitment, a discount rate, shortfall liability, mandatory Enterprise Support, and various ancillary negotiated provisions. No substantive entitlement or commercial difference exists between the two labels. The only reason to distinguish them is historical context.

For the full commercial mechanics of this programme, see the AWS EDP negotiation enterprise playbook 2026, which covers commit sizing, discount benchmarks, shortfall risk, and support fee negotiation in full detail.

A Brief History: How EDP Became PPA

To understand why both terms persist in circulation, it helps to understand the historical distinction that once existed. In AWS's early enterprise commercial framework, there were two separate discount vehicles with distinct scopes.

The Original EDP: Cross-Service Discount

The original Enterprise Discount Program was specifically designed as a cross-service discount — a single percentage applied uniformly across the customer's entire AWS bill regardless of which services were consumed. If an account had an EDP discount of 12%, every EC2 instance, every S3 bucket, every RDS database, and every Lambda invocation was billed at 12% below AWS list price. The EDP was the only vehicle through which this broad, cross-service discount could be obtained.

The Original PPA: Service-Specific Discounts

The Private Pricing Agreement was historically used for service-specific discounts — situations where AWS wanted to incentivise adoption of a specific service or where a customer had unusual consumption patterns in a particular category. A PPA might offer a 25% discount on EC2 for a high-performance computing workload, or a 30% discount on S3 for a media company with unusually high storage volumes. PPAs operated as addenda to a customer's existing EDP — you could have a PPA on top of an EDP, but not as a replacement for it.

The Convergence

Over time, the distinction between EDP and PPA became less relevant as AWS's commercial programme evolved. The cross-service discount structure of the EDP and the service-specific flexibility of the PPA were merged into a single commercial vehicle. AWS's current standard enterprise agreement is a PPA that functions exactly as the original EDP did — a cross-service discount tied to a minimum spend commitment — but with the flexibility to include service-specific discount rates where relevant.

Today, AWS uses "PPA" as the umbrella term for all privately negotiated enterprise agreements, whether they include a global discount, service-specific discounts, or both. The EDP label persists in legacy documentation, in the AWS Marketplace where both terms appear in product listings, and in conversations with customers who signed their original agreement before the terminology standardisation. But from a commercial and contractual perspective, asking "is this an EDP or a PPA?" in 2026 is like asking whether a mobile phone is a cellular phone or a wireless phone — the terminology has evolved but the thing it describes has not fundamentally changed.

Why the Terminology Confusion Persists

If the EDP and PPA are identical, why does the confusion persist so persistently in enterprise procurement conversations? Several factors contribute to the ongoing confusion.

AWS's Own Documentation Is Inconsistent

AWS's own website, Marketplace listings, and sales documentation continue to use both terms. The AWS Marketplace lists products specifically called "EDP Planning, Negotiation & Optimization" and "Enterprise Discount (EDP and PPA) Guarantee" side by side — using both acronyms as though they might have different meanings. AWS's public-facing documentation doesn't clearly explain the convergence, leaving buyers to draw their own conclusions from incomplete information.

Account Teams Use the Terms Interchangeably

AWS account teams are not uniformly consistent in their use of terminology. Some account teams (particularly those who joined AWS before the convergence) default to "EDP" as the natural label for enterprise discount agreements. Others use "PPA" consistently. Buyers who hear different terminology from different account team members naturally wonder whether there is a commercial distinction they're missing. There is not — but the inconsistency creates legitimate uncertainty.

Legacy Contracts Still Use EDP Language

Thousands of enterprise accounts signed EDP agreements before the PPA terminology was standardised. When those accounts renew, their renewal documentation often references the original EDP structure. The renewal is economically a PPA (a new privately negotiated agreement), but the account's internal documentation still refers to the "EDP renewal." This legacy language perpetuates the two-term environment in enterprise procurement teams for years after the formal convergence.

What Actually Matters: The Commercial Terms, Not the Label

Once you've established that EDP and PPA describe the same programme, the relevant question shifts from "which one do I have?" to "what are the key commercial terms I need to negotiate?" The label doesn't determine your discount, your shortfall risk, or your support obligations. The terms do.

Discount Rate and Tier

The headline discount percentage is the most visible commercial term in any EDP/PPA. It applies across all AWS services as a percentage reduction on list price billing. The discount tier is determined by a combination of your committed spend level, your term length, and AWS's internal account strategy. Our AWS EDP negotiation guide provides benchmark ranges by spend tier, though individual deals reflect negotiation quality as much as spend volume.

Spend Commitment Structure

Your commitment level — the minimum annual spend that triggers shortfall liability — is the most consequential commercial decision in an EDP/PPA negotiation. Commit too high and you face shortfall risk. Commit too low and you leave discount value on the table. The methodology for right-sizing your commitment is detailed in the AWS EDP enterprise playbook, which covers the step-by-step approach from spend baseline to final commit number.

Shortfall Provisions and Measurement

How shortfall is calculated matters as much as whether it applies. The key distinction is whether shortfall is measured against gross (list-price) spend or net (discounted) spend. Negotiating for net-spend measurement reduces the nominal shortfall exposure because your committed level is denominated in what you actually pay, not what you would pay at list price. Quarterly true-up reviews, as an alternative to annual assessments, provide earlier visibility into pacing and allow course-correction before year-end shortfall crystallises.

Enterprise Support Cost

Enterprise Support is mandatory for all accounts under an EDP/PPA. The support fee — calculated as a percentage of monthly spend on a sliding scale — can represent 3-7% of your annual AWS bill. Negotiating a support fee cap or rate reduction as part of the EDP/PPA package is standard at $5M+ spend levels. Details are in our AWS support plan negotiation guide.

AWS Marketplace Flexibility

The provision allowing qualifying Marketplace purchases to count toward EDP/PPA commitment retirement (up to 25% of the commit) is a standard provision but not always automatically included. Confirm this provision is explicitly documented in your agreement, and understand the 2025 eligibility update that restricted qualifying purchases to fully AWS-deployed SaaS products. Our AWS Marketplace procurement strategy covers how to use this provision strategically within your overall commitment structure.

Reserved Instances and Savings Plans Interaction

A common point of confusion is how Reserved Instances (RIs) and Savings Plans interact with EDP/PPA discounts. The relationship is straightforward: RI and Savings Plan discounts apply at the service level before the EDP/PPA discount is applied. The EDP/PPA discount applies to the remaining bill after RI/Savings Plan discounts. This means RI and Savings Plan purchases reduce your effective EDP/PPA commitment pacing because they lower your net bill, potentially creating shortfall risk if your commitment was sized against gross spend. Align your Savings Plan and RI optimisation strategy with your EDP/PPA commitment level before implementing new reservations.

EDP vs PPA: The Comparison Summary

For procurement teams who want a clear side-by-side view:

• Commercial structure: Identical. Both are spend commitment plus discount agreements.
• Discount scope: Identical. Both apply across all AWS services at the negotiated rate.
• Commitment mechanics: Identical. Both require minimum annual spend with shortfall liability.
• Enterprise Support requirement: Identical. Mandatory for both.
• Marketplace eligibility: Identical. Both allow qualifying Marketplace purchases to offset up to 25% of commit.
• AWS's current preferred term: PPA. EDP is legacy terminology still in use but no longer the primary label.
• What you should focus on: The commercial terms — discount rate, commit level, shortfall provisions, support costs — not the label on the contract.

Practical Implications for Buyers

Whether your contract is labelled an EDP or a PPA has zero practical implications for how you should approach the negotiation. The levers are the same, the risks are the same, and the best practices are the same. The most important practical implication of understanding the EDP/PPA equivalence is that you should not allow terminology confusion to slow down your preparation or the negotiation itself.

When you encounter an AWS account team member who uses EDP and PPA interchangeably, don't spend negotiation time clarifying terminology — spend it clarifying commercial terms. The questions that matter are: What is the discount rate at our proposed commit level? How is shortfall measured and when? Can we include a quarterly true-up provision? What does Enterprise Support cost under this agreement? How much of our commit can be retired through Marketplace purchases? These are the commercial variables that determine the value of the deal.

For a complete treatment of all these variables and a step-by-step negotiation methodology, see the AWS EDP negotiation enterprise playbook 2026. For egress and data transfer cost considerations that affect your effective spend baseline before committing, see our AWS data transfer and egress cost reduction guide.

About the Author

Fredrik Filipsson is Co-Founder of Redress Compliance, with 20+ years in enterprise software licensing and 500+ vendor engagements. He is Gartner-recognised for independent advisory on cloud and SaaS procurement. Connect on LinkedIn.