The AWS Enterprise Discount Program (EDP) is Amazon's primary mechanism for giving large-spend customers predictable pricing in exchange for committed annual spend. If your organisation spends $1M or more per year on AWS — or expects to — the EDP is almost certainly on your roadmap.
But here's what most procurement teams don't know: the EDP terms AWS first presents are rarely the best terms available. Discount levels, ramp structures, service credits, and contract flexibility vary enormously depending on how well your team negotiates. This guide, informed by our enterprise cloud discount negotiation guide, walks through everything you need to extract maximum value from your AWS EDP commitment.
For broader cloud cost strategy context, see our cloud cost optimisation pillar guide. For AWS-specific saving tactics beyond the EDP, our AWS cost optimisation strategies article covers the full spectrum.
AWS EDP discounts typically range from 5% to 25%+ depending on commitment size and negotiation skill. The difference between a poorly negotiated and well-negotiated EDP at $5M annual spend can be $500K–$1.25M per year. The right advisory support pays for itself many times over.
What Is the AWS Enterprise Discount Program?
The AWS EDP (formally called the Enterprise Discount Program, though AWS often references it as a "Private Pricing" arrangement) is a contractual commitment to spend a defined minimum amount on AWS services over a multi-year period — typically 1 to 5 years — in exchange for a discount applied across eligible spend.
Unlike Reserved Instances or Savings Plans, the EDP is a top-line discount applied to your AWS bill at the account or consolidated billing level. It does not require you to pre-select instance types or services. This makes it highly flexible — and highly negotiable.
EDP vs Other AWS Commitment Mechanisms
Before entering EDP negotiations, it's worth understanding how the EDP sits in relation to other AWS discount mechanisms. Our detailed AWS Savings Plans vs Reserved Instances comparison covers the service-level tools. The EDP sits above these — it is a commercial discount on top of whatever service-level commitments you already have.
| Mechanism | Commitment Type | Flexibility | Typical Discount | Best For |
|---|---|---|---|---|
| EDP | Total spend commitment | Very high — any service | 5–25%+ | $1M+ annual spenders |
| Savings Plans (Compute) | $/hr compute spend | High — any instance family | 17–54% | Predictable compute workloads |
| Reserved Instances | Specific instance type | Low — locked to type/region | 20–72% | Stable, known instance needs |
| Spot Instances | None (market price) | Very high | 50–90% | Fault-tolerant workloads |
| Private Pricing (per-service) | Volume by service | Medium | 10–40% | High-spend on specific services (SageMaker, Bedrock, etc.) |
The EDP and service-level commitments (RIs, Savings Plans) stack. A well-structured commitment portfolio layers EDP on top of Savings Plans and RIs to maximise effective discount rates. See our cloud commitment portfolio strategy guide for the stacking methodology.
EDP Eligibility and Minimum Thresholds
AWS does not publish formal EDP eligibility thresholds, and these shift over time. Based on market intelligence as of 2026:
| Annual AWS Spend Tier | EDP Accessibility | Typical Minimum Commitment | Notes |
|---|---|---|---|
| Under $500K | Generally not available | N/A | Focus on Savings Plans and RIs instead |
| $500K – $1M | Possible with growth trajectory | $500K+/year | AWS may engage if strong growth signal |
| $1M – $5M | Standard EDP entry range | $1M/year minimum | Base discounts typically 5–12% |
| $5M – $20M | Core EDP tier | $5M/year | Discounts typically 10–18%; more negotiation leverage |
| $20M – $100M | Strategic EDP | $20M+/year | Discounts 15–25%; executive involvement |
| $100M+ | Custom programme | Custom | Bespoke terms; AWS executive sponsors assigned |
These thresholds are indicative. In practice, AWS's appetite to offer EDP terms is influenced by your growth rate, strategic fit (e.g., migration from on-premises or from a competitor cloud), and the competitive dynamic — particularly whether Azure or GCP are active alternatives. For competitive leverage tactics, see our cloud vendor negotiation leverage guide.
EDP Discount Benchmarks by Commitment Level
The following benchmarks are derived from market intelligence across enterprise EDP negotiations. These represent achievable outcomes for organisations with effective negotiation support — not AWS's opening positions.
| Annual Commitment | Term | AWS Opening Offer | Achievable with Good Negotiation | Strong Competitive Leverage |
|---|---|---|---|---|
| $1M | 3 years | 5–7% | 8–12% | 12–15% |
| $3M | 3 years | 7–10% | 12–16% | 16–20% |
| $5M | 3 years | 9–12% | 14–18% | 18–22% |
| $10M | 3 years | 12–15% | 17–21% | 21–25% |
| $20M | 3 years | 15–18% | 20–24% | 24–28% |
| $50M+ | 3–5 years | 18–22% | 24–28% | 28%+ |
Note that these are programme discounts applied to eligible spend. Certain services (AWS Marketplace third-party products, AWS Support charges, data transfer for some services) may be excluded from EDP discount eligibility. Clarifying the exclusion list is one of the first negotiation levers.
Key EDP Contract Terms to Negotiate
Most organisations focus exclusively on the discount rate and miss the other contract terms that determine the actual value of the EDP. The following are the critical commercial and contractual terms to address.
1. Commitment Structure and Ramp
AWS will typically want a flat annual commitment. You should push for a ramp structure — lower commitment in Year 1, growing in Years 2 and 3. This de-risks overcommitment while AWS still gets the long-term revenue signal it needs. A typical acceptable ramp might be 70% / 100% / 130% over three years.
2. Shortfall Provisions
If you fall short of your committed spend, AWS will typically invoice the shortfall at the end of the year. Negotiate: (a) a shortfall buffer — a percentage of the commitment you are allowed to miss without penalty; (b) the right to roll shortfall forward into the next commitment year rather than pay immediately; and (c) a cap on shortfall invoicing if the shortfall results from an AWS service outage or pricing change.
3. Price Escalation Cap
The EDP discount is applied to list prices. If AWS raises list prices during your term, your effective cost goes up. Negotiate an annual price increase cap (typically 3–5% on services within scope) or a commitment to maintain current list prices for covered services.
4. Service Eligibility Scope
AWS's standard EDP may exclude certain services or apply different discount rates to different service categories. Negotiate to: expand the eligible service list to include high-growth services like Amazon Bedrock, SageMaker, and AWS Marketplace professional services; and ensure new services launched during the term are automatically included at the programme discount rate.
5. Credits and Migration Incentives
AWS will often provide migration credits, POC credits, or training credits alongside EDP commitments. These are often separate from the EDP discount rate — negotiate them in parallel. Migration credit packages of $100K–$500K are common for $5M+ EDP commitments. Our AWS credits negotiation guide covers this in depth.
6. SLA Provisions
Standard AWS SLAs provide service credits against future spend. In an EDP context, negotiate for: enhanced SLA commitments for critical services; credits applied against EDP commitment (not just future charges); and executive escalation paths for P1 incidents. See our AWS SLA negotiation guide for model language.
7. Termination and Exit Rights
Standard EDP terms offer limited exit rights. Negotiate: termination for cause provisions if AWS materially changes pricing or service terms; change-of-control provisions (particularly important pre-M&A); and data portability commitments that do not consume committed spend.
8. Marketplace Credit Applicability
If you procure third-party software through the AWS Marketplace, negotiate whether Marketplace spend counts toward your EDP commitment. AWS sometimes allows this, particularly for ISV Accelerate partners. It can meaningfully reduce your shortfall risk. Our AWS Marketplace private offers guide covers the ISV negotiation angle.
The 12-Month EDP Negotiation Timeline
EDP negotiations are not events — they are processes. The organisations that extract maximum value treat EDP renewal as a 12-month programme, not a 30-day sprint.
Run a comprehensive FinOps analysis of your AWS spend by service. Identify actual vs committed utilisation. Model realistic Year 1–3 growth. Simultaneously assess Azure MACC and GCP Commit terms to build genuine competitive alternatives. The strength of your BATNA determines your negotiating ceiling.
Initiate conversations with your AWS account team. Signal that you are evaluating your cloud commitment structure. This triggers AWS's internal EDP pipeline and gives you maximum runway to negotiate. Do not reveal your preferred outcome; ask AWS to "model some scenarios."
Request formal proposals from Azure and GCP. Share headline terms (not specifics) with AWS. AWS's response to competitive pressure is one of the strongest levers in EDP negotiation. Discounts can move 3–8 percentage points when AWS believes it is at genuine risk of losing workloads.
Go beyond the discount rate. Address all contract terms: ramp structure, shortfall, price escalation, service scope, credits, SLAs, exit rights. AWS's legal and commercial teams need time to approve non-standard terms — do not start this phase with less than 6 weeks remaining.
AWS's sales teams have quarterly targets. Signing at the end of Q1, Q2, or Q3 gives additional leverage. Quarter-end closings can unlock additional credits, improved discount rates, or better contract flexibility as AWS account executives work to close business.
10 Proven EDP Negotiation Tactics
AWS's discount model is stepped — larger commitments unlock higher discount tiers. Open by modelling your "stretch scenario" commitment level to see what discount tier it accesses. You can always negotiate down to a lower commitment with a higher-than-standard discount for that tier, citing the initial willingness to commit more.
Ask AWS to provide in writing the complete list of services, service categories, and charge types excluded from EDP discount eligibility. This list is often longer than expected. Use it to negotiate inclusion of specific high-spend services, and to re-baseline your effective discount rate — the rate on eligible-only spend is different from the all-in rate.
AWS Enterprise Support is charged as a percentage of your bill. If the EDP discount reduces your bill, your support charge also reduces — but support is typically excluded from EDP eligible spend. Negotiate a fixed-fee or discounted support arrangement alongside the EDP. This can save 10–20% of your total support cost.
AWS wants the revenue certainty of a 3–5 year term. Offer a longer term in exchange for a front-loaded discount improvement in Year 1. A 5-year term with a higher Year 1 discount may be more valuable than a 3-year term with standard rates, particularly if you have high-confidence growth projections.
If you are migrating workloads from on-premises or another cloud, document this migration roadmap. AWS will often unlock Migration Acceleration Program (MAP) funding, ProServ credits, and training credits in addition to EDP discounts for organisations with credible migration plans. These ancillary benefits can add 5–15% additional value on top of the base discount.
AWS's generative AI services (Amazon Bedrock, SageMaker JumpStart, Q Business) are among the fastest-growing spend categories. Many legacy EDP agreements exclude these services or apply lower discount rates. Explicitly negotiate for AI/ML services to be covered at the full EDP discount rate — and ensure any new AI services launched during the term are automatically included.
AWS Marketplace private offers allow ISV software pricing to count toward your EDP commitment. Negotiate a formal framework for requesting private offers from ISVs within your approved software stack. This can turn third-party software spend into EDP-qualifying spend, reducing shortfall risk and potentially unlocking a higher commitment tier.
AWS account teams operate within approval frameworks. When you can reference that peer organisations at your spend level have achieved better terms, this shifts the conversation from "is this possible?" to "what approval do you need?" Engage an advisor with market data, or use third-party benchmarking services, to anchor your demands in market reality.
Negotiate a clause requiring AWS to notify you if it offers materially better terms to organisations of comparable spend and profile. This prevents the common scenario where you sign an EDP only to discover that peers achieved significantly better terms. AWS will resist true MFN provisions, but you can often negotiate a right to re-open pricing discussions if the market moves materially.
AWS account teams negotiate EDP agreements every day. Most enterprise procurement teams negotiate one every 3–5 years. This information asymmetry is significant. An independent advisor with current market data and negotiation experience with AWS can typically improve outcomes by 3–8 percentage points — worth $150K–$800K per year at a $5M commitment. See our ranking of the best AWS negotiation consulting firms for vetted options.
EDP Negotiation Mistakes to Avoid
Mistake 1: Anchoring on the discount rate alone
Many procurement teams measure EDP success by the headline discount percentage. In practice, effective discount rate — discount on all spend including excluded services — is a better measure. A 15% discount that excludes 30% of your spend is worth less than a 12% discount that covers 95% of your spend.
Mistake 2: Committing before understanding your spend trajectory
AWS will often press for early commitment to secure your business. Committing before you have a robust 3-year spend model creates two risks: over-commitment (shortfall penalties) and under-commitment (leaving money on the table by not accessing higher discount tiers). Invest in FinOps analysis before entering EDP negotiations. Our FinOps enterprise guide covers the methodology.
Mistake 3: Not negotiating the ramp structure
A flat commitment over 3 years creates maximum shortfall risk in Year 1. AWS will typically accept a ramp (e.g., $3M / $5M / $7M over three years) without reducing the Year 3 discount. This structure gives you time to grow into the commitment while maintaining access to upper-tier discounts in later years.
Mistake 4: Treating EDP as a standalone negotiation
EDP negotiation should happen in the context of your full AWS relationship: training credits, ProServ agreements, Marketplace arrangements, support contracts, and service-level commitments (RIs, Savings Plans). AWS has budget across multiple cost centres. Negotiating these together often produces better outcomes than negotiating each independently.
Mistake 5: Missing the shortfall clause detail
Read the shortfall provisions carefully. Some EDP agreements require immediate payment of shortfall amounts; others allow credit against future charges. Some include a grace percentage; others are exact. The difference in commercial risk between these structures is significant, and many buyers sign without fully understanding the shortfall mechanics.
AWS EDP vs Azure MACC vs GCP Commit: A Quick Comparison
Understanding how AWS EDP terms compare to Azure MACC and GCP Commit strengthens your negotiating position. We cover this in depth in our AWS vs Azure vs GCP enterprise contract comparison. The headline differences:
| Feature | AWS EDP | Azure MACC | GCP Commit |
|---|---|---|---|
| Minimum entry | ~$1M/year | ~$1M/year | ~$1M/year |
| Discount mechanism | % off eligible spend | Credits applied to bill | % off eligible spend |
| Marketplace applicability | Negotiable | Yes (broader by default) | Limited |
| AI/ML service coverage | Negotiable (Bedrock) | Yes (Azure OpenAI) | Yes (Vertex AI) |
| Ramp structure | Negotiable | Standard ramp available | Negotiable |
| Shortfall treatment | Invoice (negotiable) | Consume credits | Invoice (negotiable) |
AWS Cloud Cost Optimisation White Paper
Download our expert guide covering EDP negotiation, Savings Plans stacking, and FinOps governance frameworks for enterprises spending $1M+ on AWS.
When to Use an EDP Negotiation Advisor
The question isn't whether an advisor adds value in EDP negotiations — market data consistently shows they do. The question is what kind of advisor to use.
AWS's own ProServ team can help with technical architecture but cannot help you negotiate against AWS. General procurement consultants may lack AWS-specific market intelligence. The most effective advisors are specialists who negotiate AWS EDP agreements regularly, have current benchmark data, and operate on a model where their fees are tied to outcomes.
Key criteria for selecting an EDP negotiation advisor:
- Current benchmark data on EDP discount rates for your spend tier
- Experience with AWS's internal approval process and which levers move outcomes
- Ability to model the full value equation: discount rate, exclusions, credits, ramp, shortfall, and ancillary benefits
- Gain-share or outcome-based fee options that align incentives
- No conflicts of interest with AWS (no reseller or partner revenue relationships)
Our ranking of the best AWS negotiation consulting firms evaluates advisors on all these criteria. Cloud cost optimisation firms are also relevant if you want broader FinOps capability alongside EDP negotiation support.