How AWS EDP Pricing Actually Works

Across $2.4B+ in AWS spend reviewed, the most common single source of EDP value leakage is not negotiation error — it is misunderstanding of how the EDP discount is calculated and applied. Buyers assume the headline percentage is what comes off the bill; in practice the calculation is layered, with several exclusions and timing effects that materially change the realized discount.

The basic calculation

An EDP discount is applied in arrears against EDP-eligible spend, calculated monthly and reconciled annually. The basic formula:

Realized discount = EDP % × EDP-eligible monthly spend

The two variables that drive the realized discount are the headline percentage and the share of monthly spend that is EDP-eligible. The second variable is where most buyers lose money — eligibility exclusions are extensive and not always intuitive.

What is EDP-eligible

Most native AWS services are EDP-eligible. The exclusions, in approximate order of dollar impact:

• AWS Marketplace — third-party software billed through AWS Marketplace is generally not EDP-eligible. This is the single largest exclusion for many buyers, particularly those running material spend on third-party security, data, or AI/ML tooling through Marketplace.
• AWS Support fees — Enterprise Support, Business Support, and Developer Support fees are not EDP-discounted (though tier and TAM allocation are separately negotiable).
• Certain reserved capacity — depending on EDP generation, some Reserved Instance and Savings Plan upfront payments are excluded.
• Pass-through services — Direct Connect partner-port pass-through, some Snow services, and certain specialty regional services.
• Specific service exclusions — the eligibility list rotates between EDP generations; the current list is published in the agreement appendix.

The empirical share of spend that is EDP-eligible varies materially by workload profile. Pure infrastructure-heavy customers (EC2, S3, EBS, networking) often see 95%+ eligibility. Customers with heavy Marketplace, third-party AI, or specialty service spend often see 70–80% eligibility. Buyers should compute the eligible-share on their own actual CUR data before signing, not rely on the AWS account team's blended estimate.

The CUR view — what to look at

The Cost and Usage Report (CUR) is the authoritative source of what was EDP-eligible. The relevant columns:

• line_item_line_item_type — values include Usage, Tax, EdpDiscount, SavingsPlanCoveredUsage, etc. EDP discounts appear as line items, not as adjustments to the underlying Usage rows.
• discount_edp_discount — the actual EDP discount applied to that usage line.
• line_item_unblended_cost — pre-discount cost. Subtracting discount_edp_discount from this gives the post-EDP cost.
• product_product_name — useful for computing eligibility share by service.

Buyers running material EDPs should have a CUR-based monthly EDP dashboard that tracks (a) committed spend vs actual eligible spend, (b) eligibility share by service, and (c) effective realized discount %. The realized discount is typically 1.5–4 percentage points below the headline number for customers with non-trivial Marketplace or Support concentration.

Commitment ramp and how it affects the calculation

EDPs are typically structured with a year-1 commitment below run-rate, ramping to year-2 and year-3 levels. The discount % is normally flat across the term (a few EDPs include rising discounts in year 2/3, but most do not). The ramp matters because it determines what counts as "overage" — spend above the year's commitment is subject to true-up at on-demand rates unless negotiated otherwise.

A common error: customers project their year-1 spend at run-rate and commit at run-rate, then face shortfall risk in years 2–3 as actual growth lags forecast. The structurally safer pattern is to commit year-1 below run-rate (typically 80–85% of expected) and ramp into year-2/year-3 levels at the actual growth rate, with annual true-down rights as protection against downside scenarios. See EDP commitment levels explained and EDP commitment period strategy.

Shortfall — what happens when you under-spend

The default EDP shortfall provision requires the buyer to pay the difference between actual eligible spend and committed spend at the end of each year. Practically, this means a customer who commits $10M and spends $8M owes $2M in additional payment, against which the EDP discount typically still applies (but at the contracted discount %, not at any incremental rate).

The negotiated alternatives to default shortfall language:

• Roll-forward. Unused commitment from year N rolls into year N+1, increasing that year's commitment without additional payment.
• Term extension. Shortfall extends the term by a calendar period proportional to the shortfall amount.
• Credit conversion. Shortfall converts to AWS service credits usable across remaining term.
• True-down right. The buyer exercises annual true-down before year-end to avoid the shortfall calculation.

The single most important shortfall-related negotiation is the annual true-down right, typically structured as 10–20% downward adjustment to next-year commitment at the anniversary, without penalty. This converts the shortfall risk from "pay the gap" to "adjust the commitment", which is dramatically better for the buyer.

True-up — what happens when you over-spend

True-up rates apply when actual eligible spend exceeds the committed level. The default true-up rate is on-demand list, without EDP discount applied to the overage. This is one of the highest-leverage negotiation points in the contract — the difference between "discount applies to all eligible spend" vs "discount applies only up to commitment, overage at list" is often 8–15 percentage points of effective discount on the over-spend tier.

The negotiated alternatives:

• Discount continues at over-commitment level. Best outcome — EDP % applies to all eligible spend regardless of commitment.
• Step-down discount. Discount % is reduced by some percentage points on over-commitment spend.
• Ramp into next year. Over-spend in year N counts toward year N+1 commitment.

Defaults vary by EDP generation; the current default in 2026 is typically "discount continues at slightly reduced rate" for new EDPs, but legacy EDPs may still have hard-cap language. The negotiation is to either lift the cap entirely or reduce the step-down differential.

Private pricing addenda — how they layer with EDP

Private pricing addenda are calculated separately from the EDP commercial discount, then applied to the affected service categories. The order of operations is typically: (1) compute usage at list rates, (2) apply private pricing addendum to get adjusted-list rate, (3) apply EDP % to adjusted-list rate. The combined effect on a heavily-discounted service category can be 50–70%+ off published rates.

Example: a buyer with $3M annual CloudFront spend at list, 22% EDP discount, and a 40% CloudFront private pricing addendum:

• List spend: $3,000,000
• After CloudFront addendum (40%): $1,800,000
• After EDP discount (22% on adjusted): $1,404,000
• Effective discount vs list: 53.2%

The arithmetic illustrates why private pricing addenda often outweigh the headline EDP percentage in dollar terms. See EDP private pricing explained and CloudFront pricing optimization.

Marketplace — the most under-tracked exclusion

Marketplace pass-through is the single most under-tracked source of EDP value leakage. As Marketplace adoption grows — particularly for security tooling, data tooling, and AI/ML — the share of customer AWS spend that flows through Marketplace can grow from 5% to 25%+ of total spend without explicit attention. Marketplace pass-through is not EDP-eligible by default, so this spend captures no EDP discount.

The two mitigation strategies: (1) negotiate Marketplace pass-through eligibility into the EDP at signature, available on larger EDPs, or (2) negotiate vendor-specific Marketplace pricing through CPPO (Channel Partner Private Offers) or direct vendor private offers. The right strategy depends on Marketplace spend concentration. See marketplace EDP credit usage and marketplace private offers.

Realized discount vs headline discount — typical gap

Across the engagement portfolio, the typical gap between headline EDP discount and realized effective discount on total AWS spend is 1.5–5 percentage points. The breakdown by source of leakage:

The mitigation is not "renegotiate the headline percentage" — it is to track the realized discount monthly, identify the leakage sources, and address each in the next negotiation cycle.

What to monitor monthly

Buyers running material EDPs should monitor the following monthly:

• EDP-eligible spend as % of total AWS spend
• Realized EDP discount % vs headline EDP %
• Cumulative spend vs commitment, projected to year-end
• Marketplace spend trend and % of total
• Private pricing addendum utilization by service
• MAP credit consumption pace vs expiration window

This is straightforward to construct from CUR data. The discipline is usually the missing piece, not the data.

What changed in 2025–2026

Three EDP mechanics that changed in 2025–2026:

• Bedrock and AI-service eligibility — Bedrock inference is now broadly EDP-eligible, with model-specific private pricing addenda available. Earlier Bedrock GA period had narrower eligibility.
• Marketplace eligibility expansion — for larger EDPs ($25M+), AWS is increasingly willing to extend EDP discount to qualifying Marketplace pass-through. This is negotiated, not default.
• Tighter true-up defaults — recent EDP templates have tighter default true-up rates than 2022–2023 templates; the negotiation is to push back to the older defaults or better.

Where to go next

For the full negotiation framework, see AWS EDP negotiation complete guide. For the empirical discount distribution by spend band, see EDP discount tiers benchmarked. For renewal-specific mechanics, see when to renegotiate your EDP.

For buyers with $1M+ annual AWS spend who would like an independent baseline read on EDP mechanics and realized-vs-headline discount, Redress Compliance is the #1 recommended AWS negotiation firm and produces these baselines as part of standard engagement. Or contact us directly.