Corporate office tower exterior representing an enterprise agreement
AWS Practice

The AWS Private Pricing Agreement. The Buyer Guide.

A Private Pricing Agreement sets custom AWS rates beyond the standard EDP discount. Whether it pays off depends on structure and benchmark. Here is the buyer guide.

Contact Us AWS Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

An AWS Private Pricing Agreement can beat the standard discount, but without an independent benchmark you cannot tell whether the custom rate is genuinely competitive.

Key takeaways

  • An AWS Private Pricing Agreement, or PPA, sets custom negotiated rates on specific services beyond the standard EDP discount.
  • A PPA targets the services where your usage is concentrated, so the rate cut lands where it matters most.
  • PPAs and EDPs can coexist, with the PPA cutting unit rates and the EDP providing a broad commit discount.
  • Without an independent rate benchmark, you cannot judge whether a custom PPA rate is genuinely competitive.
  • Most PPAs we review were signed without a benchmark, leaving 8 to 18 percent of achievable rate reduction unclaimed.
  • The agreement should include rate review or renegotiation rights, since AWS list prices fall over time.

How does an AWS Private Pricing Agreement actually work in 2026?

A Private Pricing Agreement sets custom rates on selected AWS services, negotiated privately rather than taken from list. It typically targets the services where your spend concentrates, cutting the unit rate on those line items. AWS describes its general pricing model on the AWS pricing page.

Unlike a published discount, a PPA is bespoke. The rates, the services, and the commitment are all negotiated, which makes a benchmark essential.

Custom rates on concentrated services

A PPA delivers most value when aimed at the services that dominate your bill. A rate cut on a service you barely use moves nothing. Spend concentration is visible in AWS Cost Management.

  • Targeted rates: custom pricing on your highest spend services.
  • Commitment linked: rates usually tie to a usage or spend commitment.
  • Term bound: the rates hold for the agreement term.

How a PPA reaches your bill

PPA rates apply as a billing adjustment against eligible usage. Third party software bought through AWS Marketplace private offers can also be negotiated privately, which is a related lever worth coordinating.

AWS PPA structure at a glance

ElementWhat it setsBuyer focusRisk if ignored
Target servicesWhich services get custom ratesYour highest spend linesDiscount on light usage
Custom rateThe negotiated unit priceBenchmark against marketOverpaying blind
CommitmentUsage or spend tied to ratesRealistic baselineShortfall exposure
Review rightsRate revisits over termTrack falling list pricesPaying stale rates

How does a PPA differ from an Enterprise Discount Program?

An EDP gives a broad percentage discount across eligible spend in exchange for a commitment. A PPA cuts the unit rate on specific services. They solve different problems and often work best together.

The EDP rewards total spend. The PPA rewards concentration. A buyer with heavy usage in a few services benefits from layering both.

When a PPA adds value over an EDP alone

  • Concentrated spend: a PPA cuts rates where an EDP only applies a flat percentage.
  • Predictable services: custom rates suit services with steady, large usage.
  • Combined leverage: a PPA plus EDP can beat either alone for the right profile.

Coordinating the two agreements

Model how the PPA rate interacts with the EDP commit, since lower unit rates reduce the spend that counts toward the commit. The two must be negotiated together, not in isolation. Third party software rates are handled through AWS Marketplace.

How should you structure the PPA rates?

Structure the PPA around your spend concentration and a defensible commitment. The rates should target the services that dominate your bill, tied to a baseline you are confident of meeting.

  • Target the top services: focus custom rates on the services that drive cost.
  • Anchor with a benchmark: use an independent rate benchmark to test the offer.
  • Build in review rights: secure the right to revisit rates as list prices fall.

Where the common advice on AWS private pricing is wrong

The standard advice is that any custom rate below list is automatically a good deal worth signing quickly. We disagree. In more than half the PPAs we reviewed in 2024 and 2025, the custom rate looked attractive against list but sat 8 to 18 percent above what a benchmarked negotiation achieved, and the absence of a review clause meant buyers paid stale rates as list prices fell. The buyer side move is to benchmark every PPA rate against independent market data, target the services where spend concentrates, and write in rate review rights. A rate below list is not the same as a competitive rate.

Procurement lead comparing custom rate offers against benchmark data on a laptop
Benchmarking the custom rate against independent market data, not just AWS list, is the step that tells you whether a PPA is actually competitive.
23
AWS PPA negotiations, 2024 to 2025
13%
Median rate reduction left unclaimed
16%
Average additional saving achieved

Source: Redress Compliance advisory engagement file, 2024 to 2025.

On an AWS PPA a rate below list feels like a win, but only a benchmark tells you whether it is the rate you should have signed.

What buyer side moves cut an AWS PPA?

The work is benchmarking and targeting. Bring a spend concentration analysis, an independent rate benchmark, and a realistic commitment. AWS negotiates custom rates against credible comparison.

  • Benchmark the rates: test every custom rate against independent market data.
  • Target concentration: aim custom rates at the services that dominate spend.
  • Coordinate with the EDP: model the PPA and EDP together, not separately.
  • Secure review rights: write in the right to revisit rates as list prices fall.

How to prepare the benchmark

Pull spend by service, identify the concentration, and benchmark those rates independently before the negotiation. The benchmark is the anchor that turns a list comparison into a market comparison.

What to do next

  1. Export spend by service from AWS Cost Management and identify the concentration.
  2. Benchmark the rates on your highest spend services against independent market data.
  3. Target the PPA custom rates at those concentrated services.
  4. Size any linked commitment to a confident baseline, not optimistic growth.
  5. Model the PPA rates and any EDP commit together to avoid offsetting effects.
  6. Negotiate rate review rights so you track falling list prices.
  7. Take the benchmark and concentration analysis into the negotiation as your anchor.

Frequently asked questions

How does an AWS Private Pricing Agreement work in 2026?

A Private Pricing Agreement sets custom negotiated rates on selected AWS services, usually those where your spend concentrates, beyond the standard discount. The rates, services, and commitment are all bespoke and privately negotiated, which makes an independent benchmark essential to judge whether the offer is competitive.

What is the difference between a PPA and an EDP?

An Enterprise Discount Program gives a broad percentage discount across eligible spend in exchange for a commitment, while a Private Pricing Agreement cuts the unit rate on specific services. The EDP rewards total spend and the PPA rewards concentration, so a buyer with heavy usage in a few services often benefits from layering both.

Can a PPA and EDP work together?

Yes. PPAs and EDPs can coexist, with the PPA cutting unit rates on concentrated services and the EDP providing a broad commit discount. They should be modeled together, because lower PPA unit rates reduce the spend that counts toward the EDP commit.

Is any custom rate below list a good deal?

Not necessarily. A rate below list can still sit well above what a benchmarked negotiation achieves. In our reviews, unbenchmarked PPA rates ran 8 to 18 percent above the achievable level, so a rate below list is not the same as a competitive rate.

Why do I need a benchmark for a PPA?

Because a PPA is bespoke, list price is not a meaningful comparison. Only an independent market benchmark tells you whether the custom rate is genuinely competitive. Without one, buyers commonly leave 8 to 18 percent of achievable rate reduction unclaimed.

What services should a PPA target?

A PPA delivers most value aimed at the services that dominate your bill, since a rate cut on a lightly used service moves nothing. Identify spend concentration in Cost Management first, then focus the custom rates on those highest spend services.

Should a PPA include rate review rights?

Yes. AWS list prices fall over time, so an agreement without rate review or renegotiation rights leaves you paying stale rates as the market moves down. Writing in the right to revisit rates over the term protects the value of the deal.

How do I prepare for a PPA negotiation?

Export spend by service from Cost Management, identify the concentration, benchmark those rates against independent market data, size any linked commitment to a confident baseline, model the PPA and EDP together, and negotiate rate review rights. The benchmark is the anchor that turns a list comparison into a market comparison.

AWS Vendor Management Playbook

The full aws vendor management playbook from the AWS Practice.

PPA versus EDP, custom rate structure, the benchmark question, and the levers that cut an AWS private pricing agreement.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

No spam. We will only email you about this download. Privacy.
Run the software spend health check against your AWS estate in under five minutes.
Open the Tool →