AWS Enterprise Discount Programme (EDP) discount tiers run 5 to 25 percent on net AWS spend, with the highest tier requiring 5-year terms and $50M+ annual commit. Private Pricing Agreements add another 5 to 15 percent on specific services. Marketplace purchases burn down EDP commit at full value but at less favourable economics than direct AWS spend. Exit penalties can exceed 75 percent of remaining unused commit if the EDP is terminated early. This pillar documents the full AWS EDP commercial surface for 2026 buyers.
Inside This Pillar
- What an AWS EDP actually is
- EDP discount tiers
- Ramping commit structure
- Multi-year terms
- Exit penalties
- Private Pricing Agreements
- AWS Marketplace credit
- Support cost treatment
- Interaction with Reserved Instances and Savings Plans
- Common EDP commercial mistakes
- Negotiation framework
- Renewal economics
What an AWS EDP actually is
An AWS Enterprise Discount Programme contract is a multi-year commitment to spend a defined annual amount on AWS services in exchange for a percentage discount on that spend. The contract is signed between the customer and AWS, separate from the standard AWS Customer Agreement that governs day-to-day use of AWS services. The EDP discount applies to most AWS services with specific exclusions documented in the contract.
EDP is sometimes called the "AWS Enterprise Agreement" by analogy with Microsoft's EA, though AWS does not officially use that term. Functionally, EDP plays the same role: it converts a public, variable per-service price list into a contracted private price for a defined customer over a defined term. The commercial substance is unchanged from one EDP to another. What varies is the discount percentage and the contract clauses.
EDP discount tiers
EDP discount percentages correlate with annual commit and term length. AWS does not publish the discount table. The bands below reflect typical negotiated outcomes observed in advisor-led EDP deals during 2024 to 2026.
| Annual commit | 3-year EDP discount | 5-year EDP discount | Add-on PPA potential |
|---|---|---|---|
| $1M to $3M | 5 to 8 percent | 7 to 10 percent | 0 to 5 percent |
| $3M to $10M | 8 to 12 percent | 10 to 15 percent | 3 to 8 percent |
| $10M to $25M | 12 to 17 percent | 15 to 20 percent | 5 to 10 percent |
| $25M to $50M | 15 to 20 percent | 18 to 23 percent | 8 to 13 percent |
| $50M+ | 18 to 22 percent | 22 to 27 percent | 10 to 15 percent |
Discount tiers are not strict thresholds. AWS will sometimes negotiate above-tier discounts for strategic customers where the customer represents a competitive win against Azure or GCP, has an unusually high public profile, or is willing to make commercial concessions on AWS-favoured services (Bedrock, SageMaker, AWS-published software via Marketplace).
Ramping commit structure
Most enterprise EDPs use a ramping commit structure where the annual committed amount grows year over year. A 5-year EDP at a $5M Year 1 commit might ramp to $7M, $9M, $11M, and $13M in subsequent years, with total commitment $45M. The ramp accommodates the customer's expected AWS growth and lets AWS lock in the multi-year commitment without forcing the customer to commit Year 5 dollars in Year 1.
Ramping commits create two commercial risks. The first is the ramp acceleration trap: AWS sales teams sometimes propose aggressive ramps (50 percent year-on-year) that the customer's actual AWS adoption does not support, leading to forfeited commit in later years. The second is the ramp negotiation lag: customers who hit Year 4 of a 5-year EDP and realise they will not reach the Year 5 commit have limited remediation options because AWS will not reduce the committed amount mid-term without major concession.
Multi-year terms
EDP terms are 3-year or 5-year by default. AWS occasionally offers 1-year EDPs for customers below $1M commit but at minimal discount (3 to 5 percent). The 5-year term produces the highest discount but extends the customer's commitment exposure. The 3-year term is the typical enterprise sweet spot, balancing discount realisation against commitment risk.
The term-length trade-off: moving from 3-year to 5-year EDP typically adds 4 to 6 percent additional discount on annual commit. Over five years at $10M annual commit, the additional discount is worth $2.0M to $3.0M cumulative. The trade-off is the two additional years of commitment exposure, including the risk of AWS pricing changes, AWS service deprecations, and customer business changes that reduce AWS consumption. For customers with stable AWS growth trajectories, 5-year is the better economic choice. For customers with uncertain AWS futures or active multi-cloud strategies, 3-year preserves optionality at a known cost.
Exit penalties
EDP exit penalties are the contract's most punitive clause and the most commonly overlooked at signing. The standard exit clause requires the customer to pay the unused remaining commit at full value if the EDP is terminated early. A customer in Year 2 of a 5-year $10M ramping EDP who terminates at end of Year 2 owes the cumulative unfunded commit of $33M plus any contractual penalties.
Mitigations exist but require explicit contract language. AWS will sometimes agree to a "step-down" clause allowing the customer to reduce annual commit by 25 to 40 percent under specific conditions (M&A divestiture, business unit closure, demonstrated AWS service issues). AWS will rarely agree to a true exit clause without large concession. Buyers should negotiate the step-down clause as the primary mitigation and treat the EDP as a binding multi-year obligation.
Private Pricing Agreements
Private Pricing Agreements (PPAs) are service-specific discount layers that can be added on top of an EDP. PPAs apply to individual services where the customer has unusually high consumption or where AWS wants to incentivise adoption of a strategic service. Common PPAs cover EC2 compute (typically 5 to 12 percent additional), S3 storage (3 to 8 percent), DynamoDB (5 to 10 percent), and Bedrock (8 to 15 percent in 2026 as AWS pushes AI adoption).
PPAs stack with EDP discount, with the EDP discount applied first to the public price, then the PPA discount applied to the EDP-discounted price. A 20 percent EDP discount plus a 10 percent PPA produces a 28 percent total discount, not 30 percent, because the discounts compound rather than add. The compound math matters when comparing PPA proposals.
AWS Marketplace credit treatment
AWS Marketplace purchases burn down EDP commit at full value. A customer with a $10M annual EDP commit who purchases $3M in Marketplace software during the year uses $3M of their commit on Marketplace, leaving $7M for direct AWS service consumption. This produces an apparent benefit (Marketplace purchases count toward the commit) but creates a hidden cost: Marketplace purchases do not receive the EDP discount or any PPA discount.
The pattern that destroys money: a customer with a 20 percent EDP discount makes a $1M Marketplace purchase that burns down $1M of commit. The customer pays the full $1M to the Marketplace vendor and AWS records $1M against the commit. The customer received zero EDP discount on the $1M. The equivalent direct AWS spend would have produced $800K net cost ($1M minus 20 percent), saving $200K.
| $1M spend type | EDP discount applied | Net cost | Commit burndown |
|---|---|---|---|
| Direct AWS service (EC2, S3, RDS) | 20 percent | $800,000 | $800,000 (post-discount) |
| AWS Marketplace software | 0 percent | $1,000,000 | $1,000,000 |
| AWS-published service (Bedrock, SageMaker) | 20 to 28 percent (with PPA) | $720,000 to $800,000 | Variable |
The buyer-side discipline is to consolidate software purchases on direct AWS services where possible and to negotiate Marketplace-specific discount lanes where Marketplace consumption is unavoidable. AWS will sometimes offer "Marketplace discount programs" that apply 5 to 15 percent off Marketplace prices for specific vendors, partially offsetting the no-EDP-discount problem.
Support cost treatment
AWS Support fees apply on top of EDP discount, not as part of the discounted amount. Business Support costs 10 percent of monthly AWS spend (minimum $100 per month). Enterprise Support costs 10 percent of monthly AWS spend for the first $150K, then declining percentages for higher spend (7 percent up to $500K, 5 percent up to $1M, 3 percent beyond, with a $15K minimum).
Enterprise Support is mandatory for EDP customers and is the lever that produces real value for active enterprise AWS workloads (named TAM, four-hour response SLAs on production issues, AWS Architecture Reviews, Trusted Advisor full feature access). Customers running production workloads on AWS should budget Enterprise Support at 3 to 5 percent of total AWS spend for typical enterprise scale.
Interaction with Reserved Instances and Savings Plans
EDP applies to net AWS spend after Reserved Instances (RI) and Savings Plans (SP) discounts. A customer with a 20 percent EDP discount and a 1-year compute Savings Plan at 45 percent discount produces a compound discount of approximately 56 percent on covered compute spend (20 percent EDP applied to the 55 percent net-of-SP rate). The math compounds, not adds.
The optimisation question is whether to use Savings Plans or Reserved Instances within an EDP. The general rule is that Savings Plans produce slightly lower discount than Reserved Instances but allow flexibility across instance families, regions, and operating systems. For workloads with steady-state utilisation and known instance types, 3-year Reserved Instances at full upfront produce the highest discount (72 percent on EC2 standard, layered with EDP). For workloads with variable mix, Compute Savings Plans at 1-year or 3-year (54 to 66 percent discount) produce better realised value because they cover more of the actual spend.
Common EDP commercial mistakes
Five mistakes account for most EDP overspend. The first is committing on Year 1 forecasts that are too aggressive. AWS sales teams build commit projections around adoption goals that may not materialise. Customers should build their own internal forecast and commit at 80 to 90 percent of that forecast, not 100 percent.
The second is failing to negotiate Marketplace exclusion or Marketplace discount programmes. Default contracts treat Marketplace at 0 percent EDP discount, which destroys value as cloud-native software shifts to Marketplace distribution.
The third is missing the step-down clause in the exit terms. The default contract has no step-down. A negotiated step-down clause is the customer's only realistic remediation if commit projections prove wrong.
The fourth is layering Reserved Instances poorly. Customers who buy 3-year all-upfront RIs at the start of an EDP can be locked into specific instance families even if their workload mix changes. The Savings Plan flexibility is usually worth the small discount differential.
The fifth is failing to negotiate PPA layers at the same time as the base EDP. Adding a PPA after the EDP is signed produces a worse negotiated rate than including it in the original deal because the customer has surrendered the commitment negotiating position.
Negotiation framework
The buyer-side EDP negotiation framework follows four phases. Phase 1: baseline (months 1 to 2). Build an internal AWS consumption forecast for the next 3 to 5 years independent of AWS sales input. Identify the services that will dominate spend and the services that justify PPA negotiation. Quantify Azure and GCP alternative pricing for the same workloads.
Phase 2: competitive engagement (months 2 to 4). Engage Azure and GCP with the same workload profile. Get written competitive proposals. Use them as the credible alternative throughout the AWS negotiation, not as a bluff.
Phase 3: AWS negotiation (months 3 to 5). Open with a commit proposal 20 to 30 percent below AWS's initial discount proposal expectation. Negotiate the discount, the ramp, the PPA layer, the Marketplace treatment, the step-down clause, the support cost treatment, and the renewal terms in parallel rather than sequentially.
Phase 4: contract close (month 5 to 6). Verify the final contract language against negotiated terms before signing. Pay particular attention to exit clauses, ramp formulas, PPA mechanics, and renewal options. Most EDPs that go wrong in operation went wrong in contract language at signature.
Renewal economics
EDP renewal typically begins 9 to 12 months before term end. AWS proposes a continuation EDP with a modest discount increase (1 to 3 percent above current rate) and a new multi-year ramp. The buyer-side renewal preparation is identical to the original negotiation: baseline, competitive alternative, parallel negotiation. Customers who treat renewal as a routine extension typically receive 5 to 10 percent less discount than they could have negotiated.
For the broader cloud commercial framework, see AWS EDP negotiation, AWS Savings Plans, AWS vs Azure vs GCP pricing, cloud contracts guide, cloud renewal strategy, multi-cloud strategy, and the AWS vendor hub. For an engagement on an active AWS EDP negotiation, see cloud contract negotiation or software licensing advisory.