AWS Private Pricing Agreement (PPA) Negotiation: A Buyer's Guide

An AWS Private Pricing Agreement (PPA) is a committed-spend discount you negotiate directly with AWS in exchange for a defined-term usage commitment. If your team has negotiated one of these before, you likely know it by its older name — the Enterprise Discount Program (EDP). It’s the same underlying idea, but AWS now structures it cross-service, and the deal terms that matter to procurement and FinOps teams have shifted along with it.

This guide covers what to scrutinize during a Cross-Service PPA negotiation, the eligibility groundwork AWS expects before it will discuss terms, and where a qualified AWS partner can help you get a better overall deal — including a cost line that a PPA never touches.

PPA vs. the “EDP” name you may already know

AWS’s Private Pricing overview describes the current program plainly: a Private Pricing commitment covers more than 200 eligible AWS services over a defined term, available whether you buy directly from AWS or through an AWS partner. That cross-service breadth is the practical difference from the older EDP structure many enterprises are used to — a single commitment, spread across a much wider slice of your AWS bill, rather than a narrower set of core services.

If your last negotiation predates this shift, don’t assume the old deal shape still applies. Re-baseline your usage across the full service list AWS now includes before you propose a commitment number.

What to scrutinize during negotiation

Commitment level vs. real forecast. The single biggest risk in any PPA is over-committing against a usage forecast that assumed continued growth. Build the commitment number from your actual multi-year usage trend, not a target you hope to hit.

Term length and timeline. In our deal experience, a full cross-service negotiation typically takes around 90 days from initial proposal to signature — plan renewal conversations early enough that you’re not negotiating under deadline pressure. Some cycles can be expedited, but that usually depends on how prepared your usage data and internal approvals already are.

Which services actually count toward the commitment. Confirm the eligible-services list your AWS account team is proposing. Cross-service PPAs are broader than legacy EDPs, but “cross-service” doesn’t mean every service or every Marketplace purchase automatically counts — get the list in writing before you size the commitment.

How the discount curve behaves as usage grows. Model your effective rate at multiple usage levels across the term, not just at the commitment floor. A rate that looks attractive at your current spend can look very different once workloads scale.

Support cost — the line a PPA never touches. This is the detail buyers most often miss. AWS calculates Enterprise Support (and Business Support) fees on your gross monthly AWS charges — before your PPA discount is applied. Your negotiated PPA rate reduces what you pay for usage; it does nothing to the support percentage sitting on top of that gross figure. If support is a meaningful line item, it needs a separate review in the same budget cycle, not an assumption that a good PPA rate already covers it.

Enterprise Support and Well-Architected practice as eligibility groundwork. In our deal experience, AWS treats an active Enterprise Support plan as a requirement for a cross-service commitment, not an optional add-on — go into the conversation already enrolled rather than negotiating it alongside the PPA. AWS also expects to see evidence of ongoing cost optimization and Well-Architected Review practice before it will size a favorable commitment. Have a recent review on file, or get one done, before you open the negotiation.

Exit terms and renewal benchmarking. Understand true-up obligations if you miss the commitment, and set a calendar reminder well before renewal to benchmark your rate again — pricing and eligible-service lists both evolve between terms.

Where a qualified partner improves the deal

A PPA itself is negotiated directly with your AWS account team — no partner involvement is required to sign one. Where a qualified AWS partner adds real value is in the preparation and the adjacent cost levers:

• Benchmarking your proposed commitment and rate against comparable deal shapes, so you’re not negotiating blind against AWS’s opening terms.
• Sizing the commitment to your actual workload forecast, using usage history rather than a growth target, to avoid the over-commitment risk described above.
• Meeting the Enterprise Support and Well-Architected Review groundwork. Since AWS expects both in place before it sizes a favorable commitment, a partner who already runs TAM-led Well-Architected Reviews and delivers Enterprise Support can walk in with that evidence ready, instead of scrambling to produce it mid-negotiation.
• Addressing the support-cost blind spot separately. Since a PPA doesn’t reduce Enterprise Support fees, that’s a distinct lever. AWS-authorized Managed Service Provider (MSP) partners can deliver the identical AWS Enterprise Support plan — same ticketing system, same SLAs — at a discounted rate calculated on the same gross charges, without touching your PPA or requiring any AWS account migration. ASCENDING’s AWS Partner-Led Support is built specifically around that gap.

Treat the PPA negotiation and the support-cost review as two separate line items in the same overall AWS cost conversation. Optimizing only one leaves savings on the table.

Buyer-ready checklist

• Re-baseline usage across AWS’s current cross-service eligible-services list, not last term’s narrower list
• Size the commitment from actual multi-year usage history, not a growth target
• Start renewal conversations roughly 90 days out to avoid negotiating under deadline pressure
• Get the eligible-services list in writing before agreeing to a commitment number
• Model effective rate at multiple future usage levels, not just at the commitment floor
• Review Enterprise/Business Support cost separately — a PPA discount does not reduce it
• Enroll in Enterprise Support and complete a Well-Architected Review before opening the negotiation, not during it
• Confirm true-up terms and calendar a pre-renewal benchmarking review

Bringing support cost into the same conversation

If Enterprise Support fees are a meaningful part of your AWS bill alongside your PPA commitment, it’s worth reviewing both in the same budget cycle. Schedule a consultation with ASCENDING to see what your Enterprise Support bill should look like at the MSP partner-led rate, with your PPA left completely untouched.

References

• AWS Private Pricing overview
• AWS Enterprise Support plan
• AWS Support pricing
• AWS Managed Service Provider Program
• ASCENDING Well-Architected Reviews

FAQ — Cross-Service PPA Questions Buyers Ask

Is a Private Pricing Agreement (PPA) different from the Enterprise Discount Program (EDP)?

Not a separate program — AWS's current committed-spend discount vehicle is officially called the Private Pricing Agreement (PPA). Many buyers still say "EDP" out of habit, but AWS now structures these commitments cross-service, covering 200+ eligible services under one agreement rather than a narrower legacy structure.

How long does a Cross-Service PPA take to negotiate?

In our deal experience, a full cross-service negotiation typically runs around 90 days from initial proposal to signed agreement, though some cycles can be expedited depending on renewal timing and how prepared your usage forecast is. This is our observed pattern, not a published AWS SLA.

Does a PPA reduce our AWS Enterprise Support bill?

No. AWS calculates Enterprise Support fees on your gross monthly AWS charges, before any PPA discount is applied. A PPA lowers your usage rates; it does not touch the separate support line item, so support cost needs its own review during the same budgeting cycle.

Is Enterprise Support required to get a Cross-Service PPA?

In our deal experience, yes — AWS's eligibility review for a cross-service commitment typically expects an active Enterprise Support plan, along with evidence of ongoing cost-optimization and Well-Architected Review practice. Treat these as prerequisites to prepare before you propose a commitment number, not optional extras.

Do we need an AWS partner to negotiate a Cross-Service PPA?

No. A PPA is negotiated directly with your AWS account team. Where a qualified partner adds value is benchmarking your proposed commitment and rate, delivering the Well-Architected Review evidence AWS expects, and, separately, delivering discounted Enterprise Support if that support line is also a cost concern.