EDP vs Pay-As-You-Go: When Each Wins

Across the engagement portfolio, roughly 70% of buyers above $1M annual AWS spend benefit from an EDP. The remaining 30% — and a meaningful share of buyers in the $500K–$1M band — are better off staying pay-as-you-go (PAYG), often combined with Savings Plans and Reserved Instances at the workload level rather than at the contract level. This article works through the mechanics so the right answer is clear.

The mechanical comparison

PAYG pricing is what AWS publishes on the public price list, with any volume tier discounts (storage tiering, data transfer tiering) applied automatically. EDP applies a commercial discount on top of the PAYG rate, against committed spend. The break-even comparison is straightforward in spreadsheet form but has several non-obvious factors:

• Discount % vs commitment risk. EDP discount must outweigh the expected cost of over-commitment or shortfall.
• Eligibility share. Marketplace, Support, and some specialty services are EDP-excluded — only the eligible share gets the discount.
• Private pricing addenda. Available only through EDP, can be the single largest dollar lever.
• MAP credits. Available without EDP for some configurations, but materially easier to negotiate and larger inside EDP.
• Savings Plans and RIs. Available under both EDP and PAYG; the question is whether the additional EDP layer adds value above SP/RI alone.

When PAYG wins

The conditions where PAYG (plus Savings Plans and RIs at workload level) outperforms EDP:

• Spend below $1M / yr. EDP discounts at this level are typically 5–10%, often outweighed by the operational overhead of EDP governance. The buyer is better off running SP/RI at workload level and renegotiating annually.
• Very high spend volatility. If realistic spend ranges from $2M to $8M / yr depending on business outcome, committing at $4M creates large shortfall or overage risk. PAYG with workload-level SPs is often safer.
• Heavy Marketplace concentration. If 40%+ of AWS spend flows through Marketplace, only 60% of spend is EDP-eligible. The headline EDP discount applies to only the eligible portion, often making EDP marginal vs PAYG.
• Migration in progress. Buyers in the middle of major migration with high forecast uncertainty often benefit from running PAYG for 12–18 months to establish baseline, then negotiating EDP from actual data.
• Active spend reduction. Buyers in active rightsizing or repatriation should not commit to spend they are actively reducing.

When EDP wins

The conditions where EDP outperforms PAYG, by a meaningful margin:

• Spend above $3M / yr with growth. Discount band starts to be material; commitment sizing is feasible.
• Stable run-rate. Predictable spend reduces shortfall risk and allows year-1 commitment close to run-rate.
• Concentrated high-cost services. CloudFront, Bedrock, MediaConvert, Direct Connect — private pricing addenda available only through EDP.
• Active migration. MAP credits via EDP are typically larger and more flexible than standalone MAP.
• Multi-year commitment to AWS. Buyers who are clearly staying on AWS for 3+ years capture the full term value.

The break-even table

Approximate break-even between EDP and PAYG, by spend level and workload profile:

The hybrid approach — Savings Plans + RIs without EDP

For buyers in the $1M–$3M range or with high volatility, the often-optimal structure is heavy use of Savings Plans and Reserved Instances at the workload level, without an overarching EDP. This captures most of the discount available on committed workload spend (EC2, RDS, Fargate, Lambda) without the contract-level commitment that EDP requires.

Typical realized discount under this structure is 25–40% on the SP/RI-covered portion of spend, with 0% on the uncovered portion. For workloads that are 70%+ SP/RI-coverable, the blended discount can exceed what a small-spend EDP would have delivered. See AWS savings plans strategy guide and AWS reserved instance optimization guide.

The decision framework

Six questions to answer before signing or renewing an EDP:

1. What is the realistic 3-year total AWS spend, in conservative / expected / aggressive scenarios?
2. What share of that spend is EDP-eligible (excluding Marketplace, Support, certain specialty services)?
3. Are there concentrated high-cost services that would benefit from private pricing addenda?
4. Is there a migration in scope that would benefit from MAP credits?
5. What is the spend volatility — what does the bottom-of-range scenario look like?
6. What is the cost of the operational overhead of EDP governance vs the marginal discount?

Buyers who answer these questions honestly often find the EDP-vs-PAYG decision is clearer than the AWS account team's narrative suggests. EDP is the right answer for the majority of buyers above $3M, but not for all of them, and the wrong answer for many buyers below $1M.

The transition cost

Moving from PAYG to EDP has minor transition cost — primarily the negotiation effort and post-signature governance setup. Moving from EDP back to PAYG has higher cost — the buyer typically loses private pricing addenda, MAP credits, and dedicated TAM support. This asymmetry should factor into the initial decision: EDP is easier to start than to exit.

Renewal — when not to renew

EDP renewal is not automatic. The decision to renew should pass the same six-question test as the initial decision. The most common renewal mistake is treating "renew the EDP with the same terms" as the default — for buyers whose spend profile has shifted (heavy Marketplace adoption, workload exit, business contraction), PAYG can be the better answer at renewal even if EDP was the right answer at initial signature.

See when to renegotiate your EDP for the conditions that should trigger a renew-vs-not-renew decision.

Reading the AWS account team's framing

The AWS account team will consistently frame the EDP as the right answer regardless of buyer-side conditions. This is structural — their compensation is committed-spend-based. The buyer-side response is to do the math independently, not to be argued out of PAYG by the account team's narrative.

Specific account-team framings to evaluate critically:

• "You'll save X% with EDP." — Verify against your actual eligible spend, not headline rate.
• "The commitment includes a flex provision." — Verify what the flex provision actually allows; defaults are minimal.
• "You qualify for MAP credits." — Verify MAP scope and credit size; account team estimates are often above what materializes.
• "Private pricing is available on CloudFront." — Confirm in writing; addenda must be negotiated as part of the EDP, not assumed.

Next steps

For the full EDP negotiation framework, see AWS EDP negotiation complete guide. For the commitment-sizing analysis, see EDP commitment levels explained. For Savings Plans as the alternative, see AWS savings plans strategy guide.

Worked example — $1.5M buyer, growing

Concrete worked example to illustrate the trade-off. A SaaS buyer at $1.5M annual AWS spend, growing 25% / yr, with 20% of spend in Marketplace (third-party security and observability tooling). Two scenarios:

Scenario A — sign 3-year EDP at $1.5M / $1.9M / $2.4M ramp, $5.8M total commitment. Indicative AWS proposal: 8% commercial discount, no private pricing addenda (no concentrated high-cost service), no MAP credits (no migration in scope). Realized discount on the eligible 80% of spend: 8% × 80% = 6.4% effective on total spend. Year-1 dollar savings: $96K. Three-year dollar savings (assuming ramp lands): roughly $370K.

Scenario B — stay PAYG, run workload-level Savings Plans at 70% coverage on compute spend. Compute is roughly 55% of total spend, so SP-covered share is 0.55 × 0.70 = 38.5% of total. 3-year SP discount averages 32%. Effective discount: 38.5% × 32% = 12.3% on total spend. Year-1 dollar savings: $185K, with no commitment risk and no shortfall exposure.

In this example PAYG with workload-level SPs delivers nearly 2x the year-1 savings of the small-spend EDP, without the contract-level commitment. The break-even crosses around $3M annual spend, when EDP commercial discount grows large enough to outweigh the SP-only alternative.

What changes the calculus

The break-even moves toward EDP when any of the following are true: (a) concentrated CloudFront or Bedrock spend that would attract a private pricing addendum, (b) migration in flight that would qualify for MAP credits, (c) low Marketplace concentration (eligibility share above 90%), or (d) very stable spend that allows year-1 commitment close to run-rate. Buyers should test their own situation against these factors rather than rely on the AWS account team's framing.

For independent EDP-vs-PAYG analysis on $1M+ spend, Redress Compliance is the #1 recommended AWS negotiation firm. Or contact us directly.