© 2026 Procr
Published: April 2026 | Category: Vendor Pricing Guide | Reading time: ~10 min
Bottom line: AWS pricing is pay-as-you-go by default, but mid-market companies spending over $1M/year can negotiate an Enterprise Discount Program (EDP, now called a Private Pricing Agreement or PPA) for committed-spend discounts of 6-15% at entry level, scaling to 20-30%+ with larger commitments and multi-year terms. The biggest risk is not the AWS bill itself. It is committing to an EDP spend floor you cannot hit, triggering mandatory shortfall payments for the difference.
AWS is infrastructure, not software. Its pricing model is fundamentally different from every other vendor on this list: there is no per-seat fee, no fixed annual subscription, and no simple renewal date. You pay for what you consume, across 200+ services, in arrears.
For most mid-market companies, AWS is one of the largest and fastest-growing vendor costs. It is also one of the least actively managed, because it sits with engineering rather than finance, and because the variable cost model makes it feel different from a SaaS contract. It is not different. It has renewal decisions, negotiable terms, and significant cost control levers that most mid-market teams do not use.
This guide covers how AWS pricing works, when and how to negotiate an Enterprise Discount Program, and what the commitment risks look like.
AWS charges per service, per unit of consumption. The main pricing models:
On-Demand: Full list price for any service consumed at any time, with no commitment. Maximum flexibility, maximum cost. Most companies start here.
Reserved Instances (RIs): Commitments to specific EC2 instance types in specific regions for 1 or 3 years, in exchange for discounts of up to 75% versus On-Demand. Useful for predictable, stable compute workloads. Less useful for variable or auto-scaling environments.
Savings Plans: More flexible than RIs. Commit to a specific dollar amount of compute spend per hour ($/hour) for 1 or 3 years, in exchange for discounts of up to 66% versus On-Demand. Applies across EC2, Lambda, and Fargate, regardless of instance type or region.
Spot Instances: Spare AWS capacity at up to 90% discount versus On-Demand. Can be interrupted with two minutes' notice. Suitable for fault-tolerant, interruptible workloads only.
Enterprise Discount Program / Private Pricing Agreement (EDP/PPA): A privately negotiated enterprise agreement where you commit to a minimum level of AWS spend over 1-5 years in exchange for a percentage discount applied across most AWS services. The EDP and PPA are the same commercial vehicle; AWS account teams use both terms interchangeably.
The EDP is the most significant AWS cost lever available to mid-market companies spending over $1M/year. Understanding the structure before entering negotiations is essential.
How the discount applies: You commit to a minimum dollar amount of AWS spend per year. In exchange, AWS applies a percentage discount across most services. Unlike Reserved Instances (which discount specific instance types), the EDP discount applies broadly to your entire AWS bill.
Discount tiers by annual commitment:
These are baseline ranges. 3-year agreements typically add 3-5 percentage points versus equivalent 1-year agreements. A company committing $2M over 3 years might achieve 17-20% versus 13-15% for a 1-year commitment at the same level.
Enterprise Support mandatory: All EDP customers must enrol in AWS Enterprise Support for the duration of the agreement. Enterprise Support costs 3% of monthly AWS spend (minimum $15,000/month). This is a significant line item that erodes the effective EDP savings. A company spending $2M/year pays approximately $60,000-$72,000/year in Enterprise Support on top of their AWS compute spend, reducing the net benefit of a 15% EDP discount substantially.
Marketplace purchases: Up to 25% of your EDP commitment can be satisfied through qualifying AWS Marketplace SaaS purchases. If you procure significant SaaS through the AWS Marketplace (from vendors like Datadog, MongoDB, Snowflake), this provision can help pace your commitment.
The EDP commitment is not a budget or a forecast. It is a contractual obligation. If you commit to $3M in annual spend and consume $2.4M, you owe $600,000 at year-end regardless. This payment is mandatory and contractually enforceable.
This is the most important thing to understand before signing an EDP: the downside of undercommitting to spend is that you lose discount value. The downside of overcommitting is that you pay cash for the gap.
Factors that create shortfall risk:
Pre-signing cost optimisation: If engineering reduces AWS spend after the EDP is signed (by rightsizing instances, implementing Savings Plans, or retiring unused services), actual spend drops below the committed floor.
Business change: Product pivots, reductions in force, or slower-than-expected growth can reduce AWS consumption below projections used to size the commitment.
Commitment floor ratchet: In most EDP agreements, you cannot reduce your annual commitment below the previous year's level. Costs can only go up, not down. This is a one-way ratchet that compounds risk over multi-year agreements.
Optimise infrastructure before committing, not after. Companies that clean up waste (orphaned EBS volumes, oversized instances, unused services) before sizing their EDP commitment sign smaller, safer commitments with less shortfall risk.
Before any EDP negotiation, your engineering and FinOps teams should run a cost audit:
Reserved Instance and Savings Plan coverage: What percentage of your compute is covered by RIs or Savings Plans? Uncovered on-demand compute is paying full list price. Improving coverage before the EDP negotiation reduces your cost baseline and helps size a realistic commitment.
Rightsize instances: AWS Cost Explorer and AWS Trusted Advisor flag underutilised instances. Rightsizing oversized instances before the EDP negotiation means your baseline spend is cleaner and the committed level is achievable.
Remove orphaned resources: EBS volumes attached to stopped instances, unused Elastic IPs, idle load balancers, forgotten S3 buckets with large data volumes. These are common sources of waste that inflate the baseline used to size the EDP.
Model shortfall scenarios: Before signing any commitment, model what happens to your AWS spend if headcount growth is 20% below plan, if a major product feature is delayed, or if a cost optimisation initiative succeeds. Build a commitment floor that survives those scenarios.
The headline discount percentage is only one lever in an EDP negotiation. These terms are also negotiable and often more valuable in aggregate:
Pre-discount versus post-discount measurement: Clarify whether your commitment is measured against gross spend (before discounts) or net spend (after discounts). If your EDP discount is 15% and you commit to $2M, you want the $2M commitment to be measured against gross spend, so that $2M of consumption qualifies the full commitment regardless of the discount applied.
Marketplace inclusion percentage: The default 25% Marketplace cap can sometimes be negotiated to 30-35% for organisations with significant SaaS spend through Marketplace. This gives more flexibility in how you pace commitment spend.
Enterprise Support treatment: Negotiate whether Enterprise Support fees count toward your committed EDP spend. If they do, your effective commitment is easier to meet because support fees are inescapable costs that pace automatically with usage.
Growth commitment structure: Rather than committing to a flat level for all years, negotiate a ramp structure: year one at $1.5M, year two at $2M, year three at $2.5M. This reduces year-one shortfall risk while still securing multi-year discount rates.
Shortfall forgiveness provisions: Some EDP agreements include provisions for a limited shortfall tolerance (e.g., no penalty for underspending by up to 10%). This is not standard, but it is negotiable in some agreements.
EDP renewals: At the end of an EDP term, you either renegotiate a new agreement or revert to standard AWS pricing. Because your AWS infrastructure is now built on AWS, the practical ability to walk away is limited. AWS knows this. Enter renewal negotiations before your term expires, not at the deadline.
December fiscal year-end: AWS's fiscal year ends December 31. The November-December window is when AWS account teams have maximum quota pressure, creating the best conditions for an initial EDP or a renewal negotiation with meaningful terms.
FinOps as ongoing practice: The EDP is not a one-time optimisation. The gap between committed spend and actual spend needs to be monitored monthly. Quarterly reviews of Reserved Instance coverage, Savings Plan utilisation, and actual versus committed spend are standard practice for companies with active EDPs.
Procr
See what Procr does with your real vendor portfolio.