Private pricing is the highest-threshold layer of the AWS discount system: a cross-service discount rather than a single-service commitment. Two traps come first - a shortfall payment if you miss the commitment, and mandatory enterprise support. And AWS states plainly that buying through a partner qualifies too.
The lower layers (credits, commitment discounts, spare capacity, architecture work) are all "obtained by rule". AWS has one more layer above them: the one you negotiate.
Most people will never use it - but it is worth knowing it exists, because one of its rules is directly relevant to whether you go through a channel.
Most people never reach this layer, but it is worth knowing
The official pricing page states: within a defined term, a private pricing commitment unlocks discounts across 200+ eligible AWS services, and you contact AWS to negotiate.
Keep it separate from the lower layers: credits offset an amount, commitment discounts change the unit price, architecture work reduces usage - private pricing negotiates an overall percentage with the vendor. It does not replace the others; it sits on top of them. The full layering is in AWS discounts, the complete picture.
It is not the same thing as Savings Plans or reservations
This is the most common confusion. Both are called "discounts", but their coverage is entirely different:
| Savings Plans / reservations | Private pricing (EDP / PPA) | |
|---|---|---|
| Coverage | Mainly compute (EC2, Lambda, Fargate and similar) | Cross-service - compute, storage, database, networking and more |
| Can it cover storage and databases | No (RDS, S3 and transfer each have their own mechanics) | Yes - which is the point of it |
| How you get it | Self-service, a few clicks in the console | Negotiated with AWS, under contract |
| Does it stack | - | Stacks on top of Savings Plans / reservations / Spot |
What makes it uniquely valuable: Savings Plans and reservations only treat compute; if your largest lines are storage, databases or data transfer, none of those mechanisms help. Private pricing is the only overall discount that reaches them. Which is another reason to answer "what dominates my bill" first.
The threshold: what scale makes it worth negotiating
AWS publishes no hard threshold, but third-party industry observation is fairly consistent (the following is third-party, not an official commitment):
- Where conversations start: typically around 500,000 to 1,000,000 USD of annual spend.
- Meaningful tiers: larger spend and longer terms mean deeper discounts; three-year terms are the most common.
- The nature of the discount: a cross-service percentage applied to eligible usage.
- Terms: one, three and five years all exist, longer terms discount more (five-year deals usually go only to very stable large customers).
⛔ So for most small and mid-sized teams this layer can be skipped outright - not because it is wrong, but because the threshold is not met. The lower layers (especially architecture work and commitment discounts) have more certain returns and far lower barriers. Spending effort on something you cannot reach is the most common waste in cost optimisation.
The biggest risk: missing the commitment means paying the difference
This is where private pricing differs in kind from the lower layers, and it is the risk third-party sources emphasise most:
⛔ A private pricing commitment is not a budget and not a forecast - it is a contractual obligation. If actual spend in a year falls below the commitment, the difference is payable (commonly called a true-up or shortfall payment). Using less is not saving; it is paying the committed amount anyway.
This is the same class of risk as over-buying Savings Plans, but at an entirely different magnitude: over-buy a plan and you waste one commitment; over-sign here and you absorb a full year of difference. Which is why "optimise first, sign later" is not advice but discipline:
- Remove the waste first (right-size, clear orphaned resources, fix architecture) to get a true baseline.
- Negotiate against that optimised baseline.
- Sign against today current (waste-included) cost and you lock the waste in, at a discount, for years.
The same ordering appears throughout the commitment-discount pages - see how to buy AWS Savings Plans and what Graviton actually saves.
An overlooked hidden cost: enterprise support becomes mandatory
On the consistent third-party account, signing private pricing normally requires enrolling in AWS Enterprise Support at the same time. This is easy to miss because it is two separate bills:
- Private pricing reduces a percentage of service usage.
- Enterprise support is a separate charge, billed as a percentage of usage with a high floor - the mechanics are in how to choose an AWS support plan.
⛔ Net benefit must count both. "Getting 15% off" and "netting 15%" are not the same thing - if a costly support plan is mandatory alongside, the real benefit shrinks materially. Cost the support fee separately and add it in before judging whether the deal is worth it.
One structural limit worth knowing as well: third-party accounts indicate only a portion of the commitment (roughly a quarter) can be satisfied through AWS Marketplace purchases - useful if you already buy significant SaaS there, as it helps you pace the commitment.
A shortcut: buying through a partner qualifies too
The most practically useful line on this page, and it is an official one: AWS states plainly that customers buying either directly from AWS or through an AWS partner qualify for private pricing.
That matters in two ways:
- You do not have to avoid a channel to get private pricing. "You must go direct to get the big discounts" is a common misconception - at least at this layer, AWS itself says both routes work.
- A partner is often the more realistic entry point. For teams that have not yet reached the scale where AWS comes to them, a partner that already operates at that scale may find it easier to get this done - because it is itself a counterparty at that size.
One boundary to keep straight: a partner can open the door, but what it reduces is still the amount you actually pay - a different layer from official discounts, and the two stack. The three vetting questions are in where to find AWS discount information you can trust, and channel pricing is in AWS discounts and reseller pricing.
FAQ
I spend a few hundred thousand a year - can I negotiate private pricing?
On the third-party account, conversations typically start around 500,000 to 1,000,000 USD of annual spend. Below that, the lower layers (architecture, commitment discounts, channels) have more certain returns and lower barriers. A pragmatic test: if AWS has never approached you to talk, your scale probably is not there yet.
Are EDP and PPA the same thing?
On the consistent third-party account, they are the same instrument: EDP (Enterprise Discount Program) was the earlier name, and AWS now uses PPA (Private Pricing Agreement) as the umbrella term. If your old contract said EDP and the new one says PPA, nothing material changed. (This is a commercial naming shift, from third-party sources - your contract text is authoritative.)
Does private pricing cover data transfer?
This is exactly what distinguishes it from Savings Plans and reservations: official wording says private pricing spans 200+ eligible services, whereas plans and reservations mainly cover compute. For businesses whose largest lines are transfer, storage or databases, that matters - but which services are actually in scope is defined by the eligibility list in your contract.
What if my usage drops after signing?
The difference is payable. This is the risk to think through before signing: the commitment is an obligation, not a budget. So do two things first: clear the waste before setting the baseline, and negotiate flexibility into the contract (ramp periods, true-down rights) - third-party accounts indicate such clauses are negotiable.
Is there a more realistic "overall discount" path for small teams?
Yes, but it is the channel layer rather than private pricing. A channel reduces what you actually pay, the barrier is far lower, and it does not conflict with official discounts (they stack). For small and mid-sized teams that is usually far more realistic than negotiating private pricing. See AWS discounts and reseller pricing and cloud discount mechanisms compared.