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.
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.
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.
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.
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
| Element | What it sets | Buyer focus | Risk if ignored |
|---|---|---|---|
| Target services | Which services get custom rates | Your highest spend lines | Discount on light usage |
| Custom rate | The negotiated unit price | Benchmark against market | Overpaying blind |
| Commitment | Usage or spend tied to rates | Realistic baseline | Shortfall exposure |
| Review rights | Rate revisits over term | Track falling list prices | Paying stale rates |
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.
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.
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.
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.
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.
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.
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.
White Paper · AWS
AWS Marketplace procurement strategy. The Channel Partner Private Offer framework
Read it free.
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.
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.
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.
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.
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.
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.
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.
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.
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.