AWS Private Pricing — the discount layer most enterprises never know to ask for.

PPA is a service-specific discount addendum.

An AWS Private Pricing Addendum is a contract addendum to the standard customer agreement that grants a negotiated discount on specific services, regions, or instance families, in exchange for usage commitments — often nested inside or alongside an EDP. The PPA can carry its own term, its own commitment, and its own discount mechanics. It is the layer where AWS provides the deepest discounts to its largest customers, and the layer where account team discretion has the most range.

PPAs are not standardised across customers. The discount levels, eligibility scope and rebate mechanics differ on a case-by-case basis. This is by design — the PPA is where AWS preserves pricing flexibility without changing the published list price. The negotiation pattern is therefore not about asking for "the standard PPA discount" — it is about constructing a PPA structure that matches the customer's specific consumption profile.

Where the PPA moves the most dollars.

Not every service is a candidate for PPA discounting. The categories where PPA discounts most commonly produce 3–9 percentage points of additional discount on top of EDP and reservation layers:

• EC2 compute — specific instance families with concentrated consumption, particularly on newer Graviton or memory-optimised lines where AWS is incentivising migration.
• Data transfer out (egress) — committed-volume egress pricing that can be 30–50% off standard list at scale.
• S3 storage — tiered discounts on stored volume, particularly Glacier and Deep Archive tiers.
• Database services — RDS, Aurora, DynamoDB with concentrated read or write capacity.
• Networking — Direct Connect ports, Transit Gateway data processing, NAT Gateway egress.

The pattern is consistent: the more concentrated the consumption, the more leverage in the PPA negotiation. A workload that consumes $4M of EC2 across two instance families is more PPA-receptive than the same dollar amount spread across twenty families.

How the discount applies — and when it doesn't.

PPA discounts can apply through several mechanisms. Some PPAs reduce the effective hourly rate on eligible usage. Others rebate a percentage of spend quarterly or annually. A third pattern is a credit-based PPA where eligible spend generates AWS credits that are applied to subsequent invoices. The mechanic matters for tax and accounting treatment. A rate-based PPA reduces invoiced revenue and therefore reduces the revenue base for support tier pricing — Enterprise Support is calculated as a percentage of pre-PPA spend.

PPA eligibility schedules are tightly drawn. The eligible service list typically excludes Reserved Instance upfront payments, certain marketplace SKUs, and sometimes specific regions or instance generations. The customer who plans the PPA assuming everything counts will discover at quarterly reconciliation that 12–18% of expected eligible spend was outside scope.

For enterprises with concentrated AWS consumption above $4M annually in specific service categories, the PPA layer typically protects 4–11% of contract value over the term. Surfacing that hidden layer is the core of our cloud contract advisory work on hyperscaler agreements.