AWS EDP Negotiation: The Complete Enterprise Playbook 2026

Understanding the AWS EDP and PPA Framework

The AWS Enterprise Discount Program (EDP) has been rebranded as the Private Pricing Agreement (PPA), but the commercial structure is identical. Both terms describe the same thing: a privately negotiated enterprise agreement where an organisation commits to a minimum level of AWS spend over 1-5 years in exchange for discounted pricing across all AWS services. When AWS account teams use these terms interchangeably, they're not being imprecise — they genuinely refer to the same contractual vehicle.

The EDP/PPA operates as a discount overlay on top of your existing AWS pricing. You don't need to change how your engineering teams deploy services, switch to different instance types, or modify existing Reserved Instances or Savings Plans. The EDP discount is applied as a percentage reduction on your total AWS spend, making it the most operationally seamless discount mechanism AWS offers.

The fundamental exchange in an EDP negotiation is risk for reward. You accept the risk of paying for committed spend whether or not you achieve it (the shortfall risk). AWS rewards that risk acceptance with a discount percentage and, often, ancillary benefits such as support fee caps, Marketplace purchase flexibility, and technical account management. Maximising the deal means minimising the shortfall risk while maximising the discount — which requires precise commitment sizing and disciplined negotiation.

Who Qualifies for an AWS EDP

AWS doesn't publish a firm threshold for EDP access, but the practical minimum is approximately $500,000-$1M in annual AWS spend. Below this threshold, AWS account teams are unlikely to invest the negotiation time required for a bespoke EDP, and the discount percentages achievable at low spend levels don't justify the commitment risk for most organisations.

Organisations that AWS prioritises for EDP offers typically share some combination of: annual AWS spend above $1M, consistent year-on-year spend growth, a significant proportion of spend in Enterprise Support-qualifying accounts, and strategic workloads (production environments, not just development/test) running on AWS. Organisations with large, unpredictable spend patterns — high peaks and low troughs — are harder to commit and may receive lower EDP discounts than a flat, predictable spend profile of equivalent size.

Explore our detailed guide to AWS EDP negotiation for account-level qualification and the internal preparation steps that improve your negotiating position. For comparison of the EDP and PPA terminology, see our AWS EDP vs PPA guide.

Commit Sizing: The Most Important Decision in EDP Negotiation

Commit sizing is where most enterprise EDP negotiations go wrong. AWS account teams have a natural incentive to encourage larger commits — larger commits justify larger discounts and, more importantly, larger locked revenue for AWS. Finance teams without the analytical foundation to challenge AWS's commit recommendations often accept commit levels that either over-commit the organisation (creating shortfall risk) or under-commit it (leaving discount value on the table).

The Right Methodology for Commit Sizing

The correct approach to commit sizing starts from a bottom-up spend forecast, not from AWS's account team projection. Your starting point should be a forensic analysis of your current AWS bill: strip out one-time charges, seasonal spikes, development and test environments that won't scale proportionally with production, and any historical spend from services or projects that are being decommissioned. This analysis typically reveals that your "clean" baseline spend is 15-30% lower than your headline AWS invoice.

From this baseline, build a conservative growth model. If your business is growing at 25% per year, your AWS spend should not automatically be projected to grow at 25% — cloud spend growth slows as engineering teams mature and implement cost optimisation. A realistic AWS spend growth rate for a mature engineering organisation is typically 10-20% annually after initial adoption phases. The AWS Reserved Instance and Savings Plan optimisation framework reduces growth rates further by ensuring existing commitments are efficiently utilised.

Rightsizing Before Committing

Commit only after rightsizing. This is the single most commonly ignored advice in EDP negotiation, and the single most important. If you enter an EDP commitment with orphaned EBS volumes, oversized EC2 instances, unused RDS deployments, and unoptimised data transfer patterns, you're committing to a cost base that a competent FinOps team can reduce by 20-40% without affecting functionality. When that optimisation occurs post-commitment, you'll be paying for committed spend that represents your old, inefficient cost base.

The practical sequence is: (1) complete a cost optimisation audit across your AWS estate; (2) implement the highest-ROI rightsizing recommendations (typically 3-4 months of work for a mature estate); (3) use the post-optimisation spend trajectory as your EDP commitment baseline. This approach typically reduces the required commitment level while maintaining the same discount tier, because AWS discount tiers are based on the commitment-to-discount ratio, not absolute spend levels alone. Explore AWS data transfer and egress cost reduction as one of the highest-impact optimisation categories to address before committing.

Commit Structure: Annual vs Multi-Year

EDP commitments are structured as total contract value with annual minimums. A $10M three-year EDP requires you to spend at least $3.33M per year (or a defined annual ramp). AWS prefers front-loaded commits (where the annual minimum increases year-over-year) because they reduce AWS's commitment risk. Buyers should negotiate for flat or modestly ramped annual commits, and for flexibility provisions that allow the annual minimum to be adjusted if business conditions change materially.

Multi-year commitments (three or five years) yield higher discounts than one-year commitments, but they also increase the exposure window for shortfall risk. For organisations with predictable workloads and stable business conditions, three-year commitments typically provide the best discount-to-risk ratio. Five-year commitments are appropriate for very large, stable cloud estates ($50M+ annual spend) where the incremental discount justifies the extended exposure.

Discount Benchmarks by Spend Tier

AWS does not publish EDP discount rates, and account teams are instructed not to share benchmark data with customers. This information asymmetry is a significant disadvantage for buyers who lack access to market data. The following benchmarks reflect Redress's experience across 500+ enterprise engagements and are directionally accurate as of Q1 2026, though individual deals vary based on commit term, AWS service mix, account team targets, and timing within AWS's fiscal year.

Typical EDP Discount Ranges by Annual Commit Level

$500K-$2M annual commit: 5-8% discount. At this level, AWS views the EDP primarily as a retention mechanism rather than a strategic partnership. Discount expectations should be modest. The primary value at this tier is predictability and the operational simplicity of a single commercial relationship.

$2M-$5M annual commit: 8-12% discount. This range begins to move into meaningful discount territory. AWS account teams have more flexibility at this level. Ancillary benefits (Enterprise Support fee caps, technical account management) become more negotiable.

$5M-$10M annual commit: 12-16% discount. At this level, your deal is large enough to attract senior attention from AWS's commercial team. Timing within AWS's fiscal year (Q4, ending December 31) provides additional leverage. Negotiating shortfall provisions and Marketplace flexibility becomes more achievable.

$10M-$50M annual commit: 16-22% discount. Strategic accounts receive bespoke treatment from AWS's Strategic Account Management team. Deals at this level are reviewed at senior AWS leadership levels and often include commitments to dedicated engineering support, roadmap access, and programme benefits beyond the standard EDP structure.

$50M+ annual commit: 22-30%+ discount. Deals at this scale involve direct engagement with AWS's global accounts leadership. Service-specific discounts, SLA improvements, and infrastructure reservation guarantees can be included in the negotiation. Few enterprises operate at this scale, but the discount increments at each tier provide useful context for understanding what AWS considers possible at any spend level.

Shortfall Risk: Understanding and Managing the Core EDP Risk

The shortfall mechanism is the most significant financial risk in the EDP structure. If you commit to $5M annual spend and only consume $4.2M, you owe $800,000 regardless — paid as a "true-up" charge at the end of the commitment year. This is not optional and is contractually enforceable. Understanding the shortfall mechanics and negotiating mitigants is essential before signing any EDP.

How Shortfall Is Calculated

Shortfall is the difference between your committed annual spend and your actual AWS consumption during the commitment period. AWS measures this against your gross AWS spend before the EDP discount is applied — a critical point. If you committed to $5M and received a 10% discount, your effective target is $5M of list-price consumption (generating an actual invoice of $4.5M). The shortfall calculation is on the list-price side, not the discounted invoice side. This distinction matters because it means you need to achieve $5M in billing-record spend, even though you'll only pay $4.5M of it.

Negotiate for commitment measured against discounted spend (what you actually pay), not gross spend. AWS often agrees to this for accounts with strong leverage because it doesn't change the underlying commercial outcome — but it eliminates a source of confusion that can result in unexpected shortfall charges.

Shortfall Mitigation Strategies

The most effective shortfall mitigation strategies are: (1) conservative commit sizing (as described above); (2) quarterly true-up reviews — negotiate quarterly instead of annual true-up assessments so you can identify pacing issues early; (3) Marketplace flexibility — ensure up to 25% of your EDP commit can be retired through qualifying AWS Marketplace SaaS purchases, providing a buffer if infrastructure spend falls short; (4) commit ramp provisions — structure the commitment as a ramp (lower in Year 1, higher in Year 2-3) to reduce Year 1 shortfall risk while business adoption accelerates; and (5) force majeure carve-outs — negotiate provisions that suspend shortfall liability if your business experiences material adverse changes (acquisition target, regulatory disruption, business unit divestiture).

For organisations already in an EDP and experiencing shortfall risk, the Savings Plan and Reserved Instance optimisation programme can help accelerate spend toward the committed level without increasing infrastructure waste.

Enterprise Support: Mandatory, Expensive, and Negotiable

AWS Enterprise Support is mandatory for all accounts under an EDP. This is non-negotiable as a condition of the programme — AWS requires that the payer account and all linked accounts have Enterprise Support to participate in an EDP. What is negotiable is the cost of Enterprise Support.

Standard Enterprise Support Pricing

AWS Enterprise Support is priced as a percentage of monthly spend: 10% for spend up to $150K/month, 7% for the portion between $150K and $500K, 5% between $500K and $1M, and 3% above $1M. For a $5M annual AWS account ($417K/month), the standard Enterprise Support fee is approximately $24.5K/month, or $294K annually. This is roughly 6% of annual AWS spend, a material add-on cost on top of your base services.

Negotiating Support Fee Caps and Rates

Enterprise Support fees are negotiable as part of the EDP commercial package. The most common modifications achieved by Redress across our AWS support plan negotiation engagements are: (1) flat fee support — converting from percentage-of-spend to a fixed monthly or annual fee, typically set at a discount to the projected percentage-based cost; (2) fee cap — a maximum monthly support charge regardless of how high AWS spend grows, providing cost certainty as workloads scale; (3) rate reduction — a lower percentage rate applied to the entire spend bracket; and (4) tech account management inclusion — a dedicated Technical Account Manager (TAM) included in the support fee, rather than at additional cost.

At $5M+ annual commit levels, AWS account teams have authority to include Enterprise Support modifications in the EDP package. The negotiating frame is straightforward: "Enterprise Support is a condition of EDP participation. We're accepting a multi-year commitment to justify the EDP discount. The support fee should reflect our commitment level, not the standard percentage rate." Most enterprise accounts at this level achieve at least a rate reduction or fee cap.

AWS Marketplace Optimisation Within Your EDP

The AWS Marketplace can serve as both a spend management tool and a procurement efficiency vehicle within your EDP. Understanding the 2026 rules for Marketplace spend eligibility is essential for organisations that plan to route ISV software procurement through Marketplace as part of their commitment pacing strategy.

The 25% Marketplace Rule

AWS allows up to 25% of your EDP commitment to be retired through qualifying AWS Marketplace SaaS purchases. This provision was introduced to make the EDP more attractive to organisations with significant third-party software costs alongside infrastructure spend. If you have $5M annual EDP commit, up to $1.25M of that commit can be offset by qualifying Marketplace purchases.

The key qualifier is "SaaS products fully deployed on AWS" — a rule updated in May 2025 that tightened the eligibility criteria. Marketplace purchases of products that have components deployed outside AWS infrastructure (hybrid or multi-cloud SaaS products) no longer qualify for EDP retirement. Review your Marketplace ISV portfolio against this criterion before relying on Marketplace purchases for commit pacing.

Procurement Efficiency Benefits

Beyond commit pacing, the AWS Marketplace provides the same procurement efficiency benefits as other cloud marketplaces: consolidated billing, faster procurement cycles, and reduced direct negotiation overhead for smaller ISV relationships. For ISV software that is already deployed on AWS infrastructure, routing the procurement through Marketplace simplifies vendor management without adding cost (assuming the ISV absorbs the Marketplace transaction fee, which varies by product and partner). See our guide on AWS Marketplace procurement strategy for detailed guidance on building a Marketplace-integrated procurement programme.

Negotiation Timing: AWS Fiscal Year and Quarter End

AWS's fiscal year ends December 31. Quarter ends are March 31, June 30, September 30, and December 31. EDP negotiations are significantly influenced by where they fall relative to these dates. Understanding AWS's internal incentive structure helps buyers time negotiations for maximum commercial benefit.

Q4 (October-December): The Power Quarter

AWS's Q4 is the best time to negotiate an EDP. Sales teams are under intense pressure to close revenue before the fiscal year ends on December 31. AWS account teams have maximum authority to offer concessions in Q4, approval cycles are accelerated, and AWS leadership is motivated to protect renewal revenue and close new logo commitments before year-end reporting.

The practical implication: if you're approaching an EDP renewal or planning a first EDP, time your commercial conversation to be in active negotiation by October-November, targeting a December close. If you let the conversation slip to January, you've entered a new fiscal year where AWS's internal urgency has reset to zero and approval processes restart.

Q3 (July-September): The Second Window

AWS's Q3, ending September 30, represents the second-best negotiation window. Sales teams are trying to hit three-quarter targets, and there's a natural push to close deals before the summer slowdown ends. Q3 deals typically don't receive the same level of concession as Q4, but they're significantly better than Q1-Q2 deals where AWS has the least incentive to move on price.

Renewal Timing Strategy

For EDP renewals, begin the conversation 6-9 months before your current EDP expires. This timeline serves two purposes: it gives you adequate time to conduct the spend analysis, rightsizing, and commit sizing work that underpins a good negotiation; and it ensures your renewal discussion is active during a Q3 or Q4 window. Allowing a renewal to drift to within 60 days of expiry creates time pressure that AWS can exploit — you need to renew to maintain your discount, and AWS knows the consequence of not renewing is immediate reversion to list prices.

The EDP Negotiation Sequence

Effective EDP negotiations follow a structured sequence that ensures you have the information and leverage to make strong commercial decisions at each stage. The six-step process Redress uses across enterprise EDP engagements is:

Step 1: Spend Baseline Analysis. Pull a detailed billing analysis covering the most recent 12-24 months. Identify the clean baseline spend (removing one-time charges, non-recurring projects, and optimisation opportunities). Build a conservative growth projection. This becomes your negotiating floor — you should not accept an EDP commit level below your conservative baseline projection.

Step 2: Cost Optimisation. Implement the highest-ROI cost optimisation recommendations before entering negotiations. Rightsize EC2 instances, eliminate orphaned resources, optimise Reserved Instance and Savings Plan coverage, and reduce unnecessary data transfer costs using the guidance in our AWS data transfer cost reduction guide. Document the savings achieved — this evidence demonstrates analytical capability and strengthens your negotiating credibility.

Step 3: Competitive Context. Ensure you have at least preliminary conversations with AWS's competitors (Azure, Google Cloud) before your EDP negotiation begins. You don't need active proposals — you need documented evidence that you've evaluated alternatives and have a realistic migration pathway for at least a portion of your workloads. This transforms the conversation from "how much discount can we get" to "how do we retain your AWS business."

Step 4: Initial Ask. Present your EDP proposal to AWS with a specific commit level, discount ask, support fee structure, and term length. The initial ask should be aggressive — you should assume some concession from your opening position, so leave room. Asking for 18% when you'd accept 14% is a different negotiation from asking for 14% upfront.

Step 5: Anchor and Negotiate. AWS will respond with a counter-proposal. The common AWS tactic is to offer a higher commit level at a higher discount rather than meeting your requested discount at your requested commit level. Resist this trade-off unless the larger commit is genuinely within your baseline projection. A higher discount on an over-commit is worse than a lower discount on a right-sized commit.

Step 6: Close on All Terms. Agree on the full package: discount rate, annual commit levels, term, shortfall provisions, support fee structure, Marketplace flexibility, and ancillary benefits. Do not leave "to be confirmed" items for a follow-up conversation — those items invariably resolve in AWS's favour after signature.

Common EDP Negotiation Mistakes

The mistakes that cost enterprises the most value in EDP negotiations are consistent across organisations of every size and industry. Knowing them in advance allows you to avoid them.

Accepting AWS's spend projection as the commit baseline. AWS's account team projections are derived from internal models that over-estimate growth. They incentivise larger commits. Always build your own projection from your own data.

Negotiating discount rate without negotiating shortfall provisions. A 15% discount on an over-committed EDP is worse than a 12% discount on a precisely sized one. Shortfall provisions are as important as the headline discount percentage.

Treating Enterprise Support as non-negotiable. It's required, but not at list price. Enterprise Support is a revenue line for AWS and is included in EDP negotiations at accounts with meaningful leverage. Always ask.

Not using fiscal year timing. AWS Q4 negotiations yield materially better outcomes than Q1-Q2. Planning your negotiation timeline around December 31 is simple, but enterprises frequently allow renewal conversations to drift past this window.

Signing before implementing cost optimisation. Post-signature, your cost optimisation reduces your spend and creates shortfall risk against the commit you've just signed. Optimise first, then commit.

Real-World Example: From EDP Overcommit to Restructured Terms

In one engagement, a mid-market SaaS company committed to a $4.2M EDP with an overly aggressive Year 1 ramp. Redress identified a 28% shortfall risk before signing and restructured the commit profile, saving $840,000 in potential penalty exposure. The engagement was completed four weeks before contract signature.

About the Author

Morten Andersen is Co-Founder of Redress Compliance, with 20+ years in enterprise software licensing and 500+ vendor engagements. He is Gartner-recognised for independent advisory on cloud and SaaS procurement. Connect on LinkedIn.