AWS EDP Flexibility Provisions: What You Can Actually Negotiate

What the EDP Actually Is

The AWS Enterprise Discount Program — rebranded in some contexts as the Private Pricing Agreement (PPA) — is a negotiated commercial arrangement in which an enterprise commits to a minimum annual spend on AWS in exchange for a percentage discount applied across eligible services. The commitment is made upfront, typically in a multi-year contract ranging from one to five years, and the discount applies automatically to qualifying service consumption.

Meaningful discounts begin at approximately $2 million in annual committed spend. Below that threshold, AWS's standard pricing tiers and Reserved Instance savings generally offer comparable value without the commitment obligation. At $2 million and above, the EDP unlocks discounts of roughly 8 to 15 percent depending on commitment size, term length, and the services covered. At $5 million and above, strategic pricing breaks become available that reward longer terms with materially higher discount rates.

What enterprises frequently discover after signing, however, is that the flexibility of the program — how much room exists to adjust commitments, restructure coverage, or avoid overpayment during periods of slower growth — is far narrower than expected. Understanding each flexibility provision before negotiation is essential to avoiding a commitment that penalises your organisation for the next three to five years.

The Ratchet Clause: The Most Consequential Provision

The ratchet clause is the provision that surprises enterprises most. Under standard EDP terms, your annual commitment for each subsequent contract year cannot be lower than the commitment in the prior year. If you committed to $3 million in year one, your minimum in year two is $3 million, even if your actual spend fell short.

This creates a one-directional escalator. Commitments can remain flat or increase, but they cannot decrease within the contract term. In practice, this means that organisations which experience slower growth, undergo restructuring, divest business units, or shift workloads to on-premises or competing cloud providers remain obligated to the original commitment floor.

While the ratchet itself is typically non-negotiable, the rate of escalation is not. AWS standard terms may propose automatic commitment increases of three to five percent annually. During negotiation, you can push for a flat commitment structure across the term, particularly if you are entering at a higher spend level that already provides AWS with strong revenue visibility. Enterprises committing $5 million or more annually have successfully negotiated flat multi-year structures with no upward escalation obligation.

Marketplace Ratio: The 25 Percent Default

By default, AWS limits Marketplace purchases — software and services procured through the AWS Marketplace from third-party vendors — to 25 percent of your committed EDP spend. This means that if your annual commitment is $4 million, a maximum of $1 million of that commitment can be retired through Marketplace transactions. The remaining $3 million must be direct AWS service consumption.

For enterprises that rely heavily on third-party SaaS deployed on AWS infrastructure, this default ratio can be a significant constraint. It forces direct AWS spend beyond what the organisation may actually consume, effectively increasing the over-commitment risk.

The Marketplace ratio is negotiable. Enterprises with a demonstrable reliance on Marketplace-listed software — ISVs, data services, security tools, analytics platforms — regularly negotiate the ratio to 30 or even 35 percent. The leverage for this negotiation comes from a clear mapping of your Marketplace spend as a percentage of total AWS consumption, presented before negotiation begins.

One critical development to note: from May 2025, AWS changed its Marketplace SaaS qualifying policy. Only SaaS products fully deployed on AWS infrastructure now qualify for commitment retirement against the EDP. Products running on non-AWS infrastructure no longer count, regardless of when the original deal was structured. If your AWS Marketplace portfolio includes hybrid-hosted SaaS products, audit which ones qualify under the new rules before relying on them to meet your commitment.

True-Up Cadence: Quarterly vs Annual

The true-up mechanism governs how and when AWS reconciles your actual spend against your committed spend. Under default EDP terms, true-ups occur annually — at the end of each contract year, AWS calculates whether your actual spend met the commitment. If you fell short, you pay the difference. If you exceeded, the overage is simply billed at standard (post-discount) rates.

Annual true-ups create a dangerous visibility gap. Many enterprises approach the end of their commitment year unaware of their spend position until it is too late to accelerate consumption or adjust business decisions. An unexpected shortfall bill for hundreds of thousands of dollars at year-end is a common outcome for organisations that do not actively track their EDP pacing.

Quarterly true-ups are negotiable and strongly advisable. With quarterly cadence, you receive an earlier view of whether consumption is pacing ahead of or behind commitment, giving you time to shift workloads, accelerate migration projects, or activate Reserved Instance purchases to close the gap. Many enterprise procurement teams successfully negotiate quarterly true-ups as a condition of signing — it costs AWS nothing and benefits you significantly.

Service Coverage Scope

EDP discounts do not apply equally across all AWS services. The scope of coverage — which services qualify for the discount rate — is a negotiation point that directly affects the value you realise from the program.

Standard EDP coverage typically includes EC2 compute, RDS, S3, and most core infrastructure services. However, several service categories are either excluded by default or carry reduced discount rates:

• Data egress charges are among the most commonly excluded items and represent the most frequent source of surprise overspend. Data transfer out from AWS to the internet or to on-premises locations is billed at standard rates unless specifically negotiated into the EDP discount scope. For organisations with significant data transfer workloads — media delivery, backup, hybrid architectures — negotiating egress coverage is essential.
• AWS Support tiers (Enterprise Support is mandatory for EDP participants, at a minimum of $15,000 per month or three percent of monthly spend, whichever is higher) are typically excluded from the discount.
• Managed services, professional services, and training are generally excluded unless specifically negotiated.
• New service categories launched after EDP signing may fall outside the discount scope unless your contract includes a blanket new-services clause.

Pushing for a broad service coverage definition — including egress, newer managed services, and a blanket clause for services launched during the term — is one of the highest-value flexibility provisions to negotiate before signing.

Reserved Instances and Savings Plans Within the EDP

A frequent point of confusion in EDP negotiations is the interaction between the EDP discount and Reserved Instances (RIs) and Savings Plans. Understanding the difference between these mechanisms matters because all three affect your total cost, but they operate differently and stack in specific ways.

Reserved Instances are a commitment to a specific EC2 instance type, size, and region (or family and region for Convertible RIs) in exchange for a discount of up to 72 percent versus On-Demand pricing. RIs are billed regardless of whether you use the capacity. Standard RIs provide the deepest discounts but the least flexibility. Convertible RIs allow instance type changes but provide somewhat lower discounts.

Savings Plans are a more flexible commitment: you agree to a minimum dollar-per-hour spend on compute (Compute Savings Plans) or specific EC2 instances (EC2 Instance Savings Plans), and AWS applies discounts of up to 66 percent. Savings Plans are not instance-type specific and automatically apply to whatever qualifying compute you run, making them preferable for organisations with evolving infrastructure.

Within the EDP, both RIs and Savings Plans count toward your committed spend. The EDP discount applies on top of your negotiated rate structure, which means that the effective cost for compute covered by RIs or Savings Plans is lower than either mechanism alone. The critical point: RIs and Savings Plans are not substitutes for the EDP commitment — they are complementary tools that help you meet your commitment floor while reducing per-unit compute cost.

Data Egress: The Most Common Surprise Cost

Data egress — charges for transferring data out of AWS — is the single most common source of unexpected cost in enterprise AWS bills, and it deserves dedicated attention in any EDP negotiation. AWS bills data transfer out at rates starting at $0.09 per GB for the first 10 TB per month, declining at volume tiers but never reaching zero.

For enterprises running hybrid architectures, disaster recovery to on-premises, large-scale analytics outputs, or content delivery workloads, monthly egress costs routinely run tens of thousands of dollars. Because egress is often excluded from EDP discount coverage by default, these costs can accumulate outside the commitment structure entirely, neither retiring spend against the commitment nor receiving the discount rate.

During EDP negotiations, push explicitly for egress to be included within the discount-eligible service scope. AWS will often agree to a tiered egress discount (rather than full EDP rate) as a compromise. Even a 20 to 30 percent reduction on egress charges represents substantial savings for data-intensive organisations, and having egress count toward the commitment floor reduces the shortfall risk.

Early Termination and Business Change Provisions

Standard EDP contracts do not include an early termination right. Once signed, the commitment is binding for the full term. However, two scenarios are worth negotiating provisions for before you sign.

First, change-of-control events — mergers, acquisitions, and divestitures — can fundamentally alter your AWS consumption profile. A divestiture that eliminates 40 percent of your workloads does not reduce your EDP commitment. Negotiating a change-of-control clause that allows commitment renegotiation in specified circumstances is achievable for large-commitment customers and is worth significant effort to obtain.

Second, commitment rollover provisions allow unused commitment from a shortfall year to be rolled into the following year rather than forfeited. AWS does not offer rollover by default, but it has been negotiated for customers with strong multi-year relationships and large commitments. Even a partial rollover — 50 percent of shortfall — materially reduces the financial risk of a demand slowdown.

Our AWS contract negotiation specialists review EDP terms independently. See also the GenAI Knowledge Hub for cloud commercial strategy content.

Six Provisions to Negotiate Before You Sign

1. Flat ratchet structure — negotiate commitment floors that do not automatically escalate year over year, particularly for commitments of $5 million or more annually.

2. Marketplace ratio expansion — push for 30 to 35 percent Marketplace inclusion, and audit which SaaS products qualify under the post-May-2025 rules before the negotiation.

3. Quarterly true-up cadence — avoid annual blind spots by securing quarterly pacing visibility.

4. Broad service coverage scope — explicitly include data egress, newer managed services, and a new-services clause for products launched during the term.

5. Change-of-control flexibility — negotiate renegotiation rights triggered by material corporate structure changes.

6. Shortfall rollover — pursue at least partial rollover of uncommitted spend rather than forfeiture in shortfall years.