AWS EDP Negotiation:
Enterprise Discount Program Tactics 2026

The AWS Enterprise Discount Program (EDP) is the primary commercial vehicle for large enterprise AWS cost reduction. Unlike public pricing, Reserved Instances, or Savings Plans — which are self-service mechanisms — EDP is a privately negotiated agreement between an enterprise and AWS that provides a volume discount on all AWS services in exchange for a committed annual spend level. For enterprises spending $1M or more annually on AWS, EDP negotiation is the single highest-impact commercial action available. This guide is part of our Cloud FinOps negotiation guide and covers everything buyers need to know to negotiate an EDP effectively.

EDP negotiations are fundamentally different from standard software contract negotiations. AWS's commercial team has more pricing flexibility than most enterprise software vendors, pricing information is less transparent (there are no published EDP discount tables), and the negotiating dynamic is more relationship-oriented. Understanding these differences — and the specific mechanics of EDP — is essential to achieving the best commercial outcome.

What Is the AWS EDP?

The AWS Enterprise Discount Program is a bilateral agreement between AWS and an enterprise customer that provides a negotiated percentage discount on all qualifying AWS service consumption in exchange for a committed minimum annual spend. EDP is not publicised by AWS — enterprise customers are typically introduced to the program by AWS account teams when spend reaches a threshold level (typically $1M+ annually) or when the customer signals interest in a long-term committed pricing arrangement.

EDP has several key characteristics that distinguish it from other AWS discount mechanisms. First, it applies as a percentage discount on all qualifying services — unlike RIs or Savings Plans, which apply to specific service types, EDP reduces the cost of every qualifying AWS service consumed. Second, EDP commitment is measured in dollars of qualifying spend, not in specific service units — the commitment is that you will spend at least $X on AWS services per year. Third, EDP agreements typically run for 1–5 years, with most enterprises negotiating 3-year terms. Fourth, EDP discounts stack with RI and Savings Plan discounts in most configurations — your RIs reduce the base cost, and EDP then reduces that further.

EDP vs. Reserved Instances vs. Savings Plans

EDP, Reserved Instances, and Savings Plans are complementary mechanisms that work best when combined strategically. Reserved Instances provide the deepest discounts on specific instance types but require accurate forecasting. Savings Plans provide flexible compute discounts without instance-level commitment. EDP provides a portfolio-level discount across all services that neither RIs nor Savings Plans cover. The combined effect of all three mechanisms — when properly sized and structured — provides the most cost-effective cloud operating model for large enterprises.

A critical point that many enterprises miss: EDP and RI/Savings Plan discounts typically stack. Your effective cost on EC2 instances, for example, might be: on-demand rate × (1 - RI discount) × (1 - EDP discount). The RI discount applies first to the on-demand rate; the EDP discount then applies to the already-discounted RI rate. This stacking means that the true effective discount of combining a 3-year RI with EDP can approach 80–85% of the original on-demand rate for the most stable, high-volume workloads.

EDP Mechanics: How Discounts Work

EDP discount mechanics are more nuanced than a simple percentage off the bill. Several mechanisms determine how your EDP discount is applied and whether you achieve the expected commercial outcome.

The EDP Credit Mechanism

Most EDP agreements use a credit mechanism rather than a direct price reduction. AWS applies credits to your monthly bill equivalent to the negotiated discount percentage applied to qualifying spend. These credits appear as line items on your AWS bill and reduce the net amount due. The credit mechanism means the headline discount is not always reflected in the unit price of individual services — the discount appears as a portfolio-level credit rather than as reduced line-item pricing. This can create confusion in FinOps tooling that does not properly account for EDP credits in per-service cost calculations.

Qualifying Spend Definition

Not all AWS spend qualifies for EDP discounts. Typically excluded are: AWS Support plans (Business or Enterprise Support), AWS Marketplace purchases (unless explicitly included through marketplace EDP provisions), certain third-party data fees, and some professional services. The definition of qualifying spend in your EDP agreement directly affects both the commitment level you need to reach (since non-qualifying spend does not count toward the commitment) and the discount savings you achieve. Negotiating to include as much of your actual spend as possible in the qualifying category is an important part of EDP structuring.

Commitment Shortfall Provisions

If your actual qualifying spend falls below the committed minimum, EDP agreements typically include a shortfall penalty or require payment of the committed amount regardless of actual consumption. The shortfall provision is one of the most commercially significant terms in an EDP agreement and should be negotiated carefully. Standard AWS EDP shortfall provisions require payment of 100% of the committed annual amount even if actual spend is lower. Negotiating reduced shortfall penalties — or a proportional payment mechanism that reduces the shortfall consequence — is achievable for large commitments and significantly reduces the financial risk of over-committing.

EDP Discount Benchmarks by Commitment Level

AWS does not publish EDP discount schedules. The following benchmarks are based on IT Negotiations' analysis of EDP agreements negotiated across our client base. They represent achievable discounts for well-prepared buyers with credible multi-cloud alternatives — not the average discount that unprepared buyers achieve.

Annual Commitment	Typical First Offer	Achievable Discount	Notes
$1M – $2M	3–5%	7–12%	Limited leverage; Azure/GCP threat most effective
$2M – $5M	5–8%	12–18%	Meaningful discount territory; competitive framing important
$5M – $10M	8–12%	18–25%	Strong leverage; enterprise account team has real discount authority
$10M – $25M	10–15%	22–30%	Strategic account status; escalated pricing approval available
$25M+	12–18%	28–35%+	AWS executive involvement; PPA bundling typically achievable

The gap between "typical first offer" and "achievable discount" in the table above represents the incremental value of skilled negotiation. For a $10M EDP commitment, the difference between accepting the first offer (10–15% discount) and negotiating to the achievable level (22–30%) is $700K–$1.5M in annual savings. Over a 3-year EDP term, that is $2.1M–$4.5M in cumulative savings — from the same commitment level, with the same workloads.

What Qualifies for EDP Credits?

The negotiation of what counts as qualifying EDP spend is more commercially significant than most buyers realise. Maximising the qualifying spend definition increases both the value of your commitment (more spend counts toward the minimum) and the savings achieved (more spend receives the EDP discount). Key areas to negotiate into qualifying spend include:

• AWS Support fees: Standard EDP excludes support plan fees from both commitment counting and discount application. Negotiating support fees into the qualifying category (or negotiating a separate support discount) can add 5–15% of total AWS spend to the qualifying base.
• AWS Marketplace purchases: Software purchases through AWS Marketplace are increasingly significant for enterprises. Including marketplace spend in EDP qualifying categories (through the AWS Marketplace EDP integration) allows marketplace purchases to burn down EDP commitments and receive the EDP discount.
• Reserved Instance fees: How RI fees count against EDP commitments varies by agreement. In some configurations, RI fees count toward commitment but do not receive additional EDP discounts (since they already have RI discounts). Clarifying this interaction in the EDP contract is important for accurate commitment modelling.
• Data transfer fees: Data egress fees are qualifying in most EDP agreements and receive the EDP discount. Negotiating egress fee inclusion in qualifying spend is typically straightforward but should be explicitly confirmed.

Private Pricing Agreements (PPAs)

AWS Private Pricing Agreements are service-specific pricing arrangements that provide deeper discounts on individual AWS services beyond the portfolio-level EDP discount. PPAs are negotiated for high-volume services where your consumption justifies service-specific commercial terms. Common PPA candidates include EC2, S3, RDS, CloudFront, and increasingly Amazon Bedrock (generative AI).

PPAs and EDP interact in two ways: PPAs may provide discounts that are applied before or after EDP credits (the stacking order affects the net savings), and PPA discounts may be counted differently in EDP commitment tracking. The combination of EDP + PPA for a major service can achieve effective discounts of 40–60% below on-demand list pricing — significantly greater than either mechanism alone.

PPA negotiations are typically more technical than EDP negotiations, requiring service-level usage data and forecasts. AWS's service-specific teams (EC2, S3, database specialists) are involved alongside the enterprise account team. The negotiation timeline for PPAs is typically longer — allow 6–8 weeks for complex PPA negotiations versus 2–4 weeks for EDP alone.

Managing Commitment Over/Under Risk

EDP commitment risk is asymmetric: over-committing triggers shortfall penalties (you pay for spend you didn't consume); under-committing means you could have achieved a higher discount for the same spend. Managing this asymmetry requires both accurate consumption forecasting and contractual protections against forecast errors.

Consumption Forecasting for EDP

EDP consumption forecasting is more accurate when broken into stable and variable components. Stable workloads — production applications with predictable resource requirements, running 24/7 on EC2 with established RI coverage — can be forecast with 90%+ accuracy 12 months in advance. Variable workloads — data processing, development environments, new initiatives, generative AI — require more conservative forecasting. A reasonable approach: forecast stable workloads at 95% confidence and variable workloads at 70% confidence, then commit to the combined forecast at the 80th percentile. This typically sets commitment at 75–85% of expected consumption, providing a comfortable buffer against upside surprise.

Ramp Schedule Provisions

If your organisation is ramping AWS consumption (through a migration programme, new product launches, or acquisition integration), negotiate a ramp schedule in the EDP: lower commitment levels in Year 1 stepping up to full commitment in Year 2 or Year 3. AWS is generally receptive to ramp schedules for organisations with documented growth plans, as they secure long-term commitment in exchange for the ramp accommodation. A typical ramp structure might be: 70% of the 3-year average in Year 1, 100% in Year 2, 130% in Year 3 — reflecting a migration programme completing in Year 1–2 and reaching steady state in Year 3.

Shortfall Penalty Negotiation

The standard EDP shortfall provision requires payment of 100% of the committed amount even if actual consumption falls short. This is negotiable, particularly for large commitments. Target terms include: shortfall penalty of 50–70% of the uncommitted gap (rather than 100%), a cure period of 30–60 days in which you can increase consumption to avoid the shortfall fee, or a carry-forward mechanism that allows unused commitment from Year 1 to apply against Year 2's commitment (de facto rollover). AWS will not volunteer these terms, but they are achievable for commitments exceeding $5M annually with well-prepared buyers.

9 EDP Negotiation Tactics

The following tactics are the most impactful actions in an EDP negotiation, ranked roughly by leverage contribution. Applying 4–5 of these effectively will produce materially better outcomes than standard account team negotiations.

Tactic 1: Anchor High on Commitment, Demand Higher Discount

AWS's EDP discount scales with commitment size. If you are considering a $5M commitment, model the discount you would receive at $7M and $10M. If the incremental discount at $7M is significantly better (e.g., 18% vs. 14% at $5M), the incremental commitment cost might be more than offset by the incremental discount savings. This analysis — showing AWS that you have modelled larger commitments — also signals seriousness and financial sophistication that typically improves the account team's responsiveness.

Tactic 2: Use Azure and GCP as Active Alternatives

AWS account teams take competitive cloud alternatives seriously. Obtain a formal pricing proposal from Azure or GCP for equivalent workloads and share the headline pricing (not necessarily all the details) with AWS's account team. The most credible competitive threat for AWS is a documented workload assessment showing that specific workloads are portable to Azure or GCP — not just "we're evaluating other providers," but "we have identified $3M in workloads that are technically portable to Azure, and Azure has proposed a 20% discount for a 3-year migration commitment." This level of specificity triggers AWS's formal competitive response process.

Tactic 3: Negotiate the Qualifying Spend Definition Upfront

The qualifying spend definition is most negotiable during initial EDP discussions, before the deal structure is set. Once AWS has proposed a commitment level based on their estimate of your qualifying spend, changing the qualifying definition requires reopening the commitment calculation. Agree on the qualifying spend definition first, then establish the commitment level based on that agreed definition.

Tactic 4: Demand Escalation Protection

EDP agreements typically allow AWS to increase list prices annually. Since EDP discounts are applied as a percentage of list prices, an increase in list prices can inflate your gross AWS bill even if your consumption stays flat. Negotiate a provision that ensures the EDP discount is calculated against a consistent price basis — either by freezing the list price of major services for the EDP term, or by specifying that your net cost (after EDP credits) cannot increase by more than a defined percentage annually from factors other than consumption growth.

Tactic 5: Include Marketplace Spend in Qualifying Categories

AWS Marketplace spend is increasingly significant for enterprises using ISV software deployed on AWS. Negotiate marketplace spend inclusion in EDP qualifying categories early in the negotiation. This allows marketplace purchases to burn down EDP commitments, reducing shortfall risk, and may allow marketplace software to receive the EDP discount — depending on how the private offer is structured with the ISV.

Tactic 6: Request PPA Discussions for High-Volume Services

Identify your top 3–5 AWS services by spend and request PPA discussions for each, running in parallel with EDP negotiations. The combination of EDP + PPA proposals gives you multiple discount dimensions to optimise simultaneously. AWS's enterprise account team can typically facilitate PPA discussions, but the timeline for PPA approvals is longer than EDP — start early.

Tactic 7: Leverage AWS Support Cost as a Negotiation Item

AWS Enterprise Support is expensive — typically 10% of annual AWS spend (with a minimum and maximum). For enterprises with $5M+ in AWS spend, Enterprise Support can cost $300K–$500K annually. Negotiate a separate discount on AWS Support as part of the EDP package, or negotiate AWS support credits as sweeteners to close the EDP gap. AWS often provides professional services credits, training credits, or support discounts as deal sweeteners when the EDP commercial terms are close but not quite agreed.

Tactic 8: Use Quarter-End Timing

AWS's fiscal year ends December 31, with quarter-ends in March, June, and September. AWS's commercial team operates under quarterly quota pressure, and deals that close near quarter-end often achieve better terms than mid-quarter deals. Plan your EDP negotiation to reach final commercial agreement in the last 2–3 weeks of a quarter. This requires starting the negotiation 6–8 weeks before the target quarter-end to allow adequate time for commercial approval processes.

Tactic 9: Engage Independent Advisory for Negotiations Above $2M

For EDP negotiations involving $2M or more in annual commitment, the information asymmetry between AWS's commercial team (which negotiates EDPs daily) and an enterprise procurement team (which negotiates EDPs at most annually) is significant. An independent advisor with recent EDP benchmark data and experience in structuring EDP terms consistently achieves 5–15% better discounts than unadvised enterprise buyers at equivalent commitment levels. The advisory fee is almost always a fraction of the incremental savings achieved. See our AWS negotiation advisory service for how we approach EDP engagements.

AWS Marketplace and EDP Interaction

AWS Marketplace has grown from a software distribution channel into a strategically important commercial platform for enterprises. Over 350,000 software products are available, and private offers allow enterprise-specific pricing. The interaction between Marketplace and EDP creates commercial opportunities that most enterprise buyers do not fully exploit.

Marketplace Private Offers can be structured so that the net price paid by the enterprise includes the EDP discount — effectively applying your negotiated AWS discount to third-party software purchases. This requires coordination between the ISV, AWS, and your procurement team during the private offer structuring. The commercial benefit is significant: if you are paying $1M annually for ISV software through AWS Marketplace, and your EDP discount is 20%, the effective saving on that software purchase is $200K annually — achieved through the commercial structure rather than a separate software negotiation.

Marketplace spend that qualifies as EDP spend also reduces your shortfall risk. If your direct AWS consumption falls below commitment, qualified marketplace spend fills the gap. This dynamic makes Marketplace a genuine EDP risk management tool, not just a software procurement channel.

EDP Renewal Strategy

EDP renewals are typically less contentious than initial EDP negotiations, because both AWS and the enterprise have established a commercial relationship and have concrete consumption data to anchor the renewal discussion. However, renewal negotiations can still be significantly improved with preparation.

Key renewal priorities include: reviewing consumption against commitment for the expiring term (identifying whether you over- or under-consumed and why), updating your competitive alternatives assessment (AWS's pricing competitiveness may have changed relative to Azure or GCP since the previous negotiation), assessing whether your consumption mix has changed significantly (new services, new regions, or major migrations may change the optimal commitment structure), and establishing your growth forecast for the renewal term based on confirmed roadmap items rather than speculative projections.

Start EDP renewal discussions 6 months before expiry — ideally 9 months for large commitments ($10M+) that require more complex commercial approval processes. Renewal discussions that begin too late give AWS's commercial team the advantage of timeline pressure on the buyer side.