AWS Negotiation Experts — EDP, RIs, Savings Plans & Enterprise Commit Strategy
Former AWS Enterprise Discount Program managers and senior cloud commercial leaders advising Fortune 500 buyers on Enterprise Discount Programs, Reserved Instances, Savings Plans, Private Pricing Addenda, Marketplace gating and Bedrock commits. We have negotiated over $740M of AWS contract value since the EDP programme matured.
What we know about AWS
AWS is the most disciplined hyperscaler on internal Deal Desk process and the most consistent on pricing framework. Their commercial architecture is built around a small set of approved discount levers (EDP, PPA, Marketplace EDP-eligibility, custom service-level discounts) governed centrally by the Worldwide Commercial Sales organisation. Three operational facts shape every AWS negotiation.
Q4 fiscal pressure
Amazon's fiscal year ends 31 December. AWS field reps and Strategic Account Managers carry annualised revenue targets and the most flexible PPA terms appear in the final two weeks of December. Q2 (April–June) is the secondary window. Mid-quarter deals routinely leave 4–9 incremental discount points on the table.
EDP commit framing
AWS reps frame the EDP as "commit-only-what-you-need" but score field performance on commit growth versus prior term. The result is a structural pressure to size commits aggressively. Our intake reviews find 22% average over-commitment versus actual run-rate.
Marketplace pass-through economics
Third-party software through AWS Marketplace counts toward EDP commit at 50–100% of spend depending on the SKU category. AWS retains a margin on every transaction. Marketplace gating is a powerful EDP-commit lever for customers with material third-party software spend.
AWS PPA discounts above the standard EDP framework require Worldwide Commercial Sales approval. The unlock is rarely a higher commit dollar number — it is a longer term, a competitive displacement narrative, or a Bedrock/AI services commit layered on top of compute. Specialised service commits unlock specialised PPA discounts that the field rep cannot authorise alone.
AWS's commercial model has also evolved sharply in 2025–2026 around AI services. Bedrock, SageMaker AI and the GPU instance families (P5, Trainium, Inferentia) are increasingly negotiated as separate commit pools that stack with the underlying compute EDP. Customers who treat AI workloads as additive to existing EDP commit are routinely over-paying versus customers who structure a dedicated AI commit with its own pricing terms.
The other structural shift is the increasing complexity of Savings Plans. The original Compute Savings Plans framework has been extended with SageMaker Savings Plans, Bedrock Savings Plans (preview), and EC2 Instance Savings Plans. Each carries different flexibility and different discount depth. Choosing the right Savings Plans mix versus RIs versus EDP commit can swing 8–14% of total cost without changing AWS consumption.
How AWS pressures the deal
Aggressive growth-curve commit sizing
AWS reps size EDP commits based on forward growth projections that exceed historical run-rate. Reps are measured on commit growth, not on commit utilisation, so over-sizing favours the rep. Average over-commitment in our intake: 22%.
Marketplace lock-in framing
Customers are encouraged to route third-party software purchases through Marketplace for "EDP credit". Once routed, the customer's negotiation leverage with the third-party ISV erodes, because the ISV now has an AWS sales channel and the customer has no direct billing relationship.
Bedrock token consumption opacity
Bedrock pricing varies by model and region with no published volume discount. Reps offer "custom token rates" for specific models conditional on AI commit dollar volume, but the underlying unit economics remain opaque.
Premium Support tied to spend
AWS Enterprise Support pricing is calculated as a tiered percentage of monthly AWS spend. As spend grows, support costs grow proportionally, even when support volume does not. Above $10M monthly AWS spend, support becomes a material commercial line.
Egress lock
Data egress fees from AWS to other clouds are positioned as standard. AWS now offers a 60-day egress fee waiver on exit (matching Microsoft and Google), but only on application, not by default. Multi-cloud architectures pay material monthly egress unless waived.
RIs as commit substitute
Customers reluctant to sign an EDP are offered "equivalent value via RIs". The unit-discount on RIs is often deeper than EDP but RIs are non-refundable and tied to specific instance types, transferring all utilisation risk to the customer.
How we negotiate AWS on your behalf
Run-rate-anchored commit sizing
We size EDP commit at the trailing 12-month run rate plus conservative growth, with negotiated ramp protection and break clauses tied to programme delivery rather than calendar dates.
Marketplace floor protection
We negotiate Marketplace Most-Favoured-Customer language requiring AWS Marketplace pricing to at least match the standalone ISV rate. Recovery typically 4–9% across material Marketplace spend.
AI commit unbundling
We structure Bedrock and SageMaker AI commits as separate pools with explicit per-token or per-hour rates, transparent volume tiers and conversion rights to standard EDP commit if usage falls below projection.
Support cost uncoupling
We model AWS Enterprise Support cost against third-party support alternatives, negotiate hard caps on percentage-of-spend formulae, and have routinely reduced AWS support spend 25–38% on accounts above $50M annual.
Egress as contractual right
We embed AWS's egress fee waiver as a contractual right rather than an applied benefit, extend it to inter-region migration and not just multi-cloud exit, and remove the 60-day cap where leverage permits.
Layered RIs + Savings Plans optimisation
We model the optimal mix of EDP commit, EC2 Savings Plans, Compute Savings Plans, SageMaker Savings Plans and Reserved Instances for the customer's consumption profile. Net saving versus single-instrument approach averages 7–11%.
Across 41 AWS engagements 2024–2026 with annual commits from $2M to $112M, our clients achieved an average 28% saving against AWS's opening EDP proposal. The largest dollar saving was $22.4M on a $112M three-year EDP for a Tier-1 financial services group; the highest percentage saving was 41% on a healthcare customer migrating from on-demand to a structured EDP with layered Savings Plans.
AWS EDP discount benchmarks 2026
| Annual EDP commit | Standard EDP discount | PPA discount uplift | Marketplace pass-through | Bedrock / AI commit |
|---|---|---|---|---|
| $1M–$5M | 6–10% | n/a | 50% credit | Standard rates |
| $5M–$20M | 10–15% | 2–5% | 50–100% credit | 5–12% discount |
| $20M–$50M | 15–20% | 4–8% | 100% credit | 10–18% discount |
| $50M+ | 18–26% | 6–12% | 100% credit with negotiated SKUs | 15–28% discount |
The four-phase AWS engagement
AWS engagements typically run 10–18 weeks from open to signed PPA. Engagements involving complex Marketplace gating, Bedrock structuring or competitive cloud alternatives extend to 16–22 weeks.
Consumption forensics
We pull twelve months of AWS billing exports, reconcile against RIs, Savings Plans and EDP utilisation, identify orphaned resources, untagged spend and over-provisioned commit. Average findings: 9–18% of spend recoverable through rightsizing alone, before any negotiation begins.
Commit and instrument modelling
We model EDP commit scenarios against layered RIs and Savings Plans alternatives, score AWS's likely concession appetite by quarter, and construct the credible Azure or GCP alternative position that becomes the negotiation counterweight.
Negotiation execution
We run the negotiation directly with the AWS Strategic Account Manager, Deal Desk and Worldwide Commercial Sales (when threshold-relevant). We script the cadence around AWS's published Deal Desk review windows to compress redline cycles.
Sustainment
We instal a monthly utilisation cadence, an automated EDP commit-tracking dashboard, a quarterly RI/Savings Plans rebalancing review, and a renewal pre-emption calendar (T-180). The next EDP negotiation begins six months before term, not 30 days before.
AWS case study
Tier-1 Financial Services Group — EDP Renewal with Marketplace and Bedrock Restructuring
The client, a Tier-1 European financial services group with 38,000 employees and $112M annual AWS spend, was approaching renewal of a three-year $98M Enterprise Discount Program with simultaneous pressure on a Bedrock commit and a Marketplace gating proposal for a major third-party security ISV. AWS's opening position was a $148M three-year EDP renewal with a separate $24M Bedrock commit and full Marketplace routing for the ISV. We ran 12 months of consumption forensics, identified 14% recoverable spend through rightsizing, structured a $118M three-year EDP with break clauses tied to programme delivery, unbundled the Bedrock commit into a transparent per-token framework with $14M minimum, and negotiated Marketplace Most-Favoured-Customer language for the ISV. Net contract value: $132M over three years versus AWS's opening $172M. Total saving: $22.4M plus $4.9M in support cost avoidance through Enterprise Support tier renegotiation.
Deepen your AWS negotiation position
Three publications and pages we recommend before opening any AWS EDP renewal or Bedrock commit.
AWS negotiation FAQ
How do I know if my company is ready for an AWS enterprise agreement?
Three readiness criteria matter most. First, 12 months of stable AWS consumption above approximately $1M annual run-rate, ideally with clear visibility on a forward growth trajectory. Second, an internal owner accountable for governance of AWS spend, reservation strategy and Marketplace gating. Third, a defensible competitive alternative (Azure, GCP, or hybrid) credible enough to influence AWS commercial framing. Below these thresholds, layered RIs and Savings Plans typically deliver better outcomes than a full EDP.
What happens if I overcommit on an AWS EDP?
AWS Enterprise Discount Program commits are dollar-volume commitments over a term (typically three years). If actual consumption falls below the commit, the customer owes AWS the shortfall as a true-up payment at term end. AWS does not refund unused commit. Average customer over-commitment in our intake reviews is 22%, and the unused commit becomes trapped capital. We size EDP commits at the 12-month observed run rate plus a conservative growth assumption, with negotiated ramp protection rather than aggressive forward growth.
What is the difference between AWS Reserved Instances and Savings Plans?
Reserved Instances commit to a specific instance type, region and operating system for one or three years, typically delivering 30–72% off on-demand pricing. Savings Plans commit to a dollar-per-hour spend across compute (EC2, Fargate, Lambda) for one or three years — more flexible than RIs but typically with slightly lower discount depth. Savings Plans suit dynamic workloads; RIs suit predictable workloads. Most customers benefit from a layered mix of both.
How are AWS EDP discounts structured?
EDP discounts apply as a percentage off list across qualifying AWS services for the duration of the commit. Standard discount tiers range from 6% at the lowest commit level to 20% or higher at strategic commit levels above $50M annual. Marketplace SKUs through AWS Marketplace count toward EDP commit with a different and typically lower discount tier. Bedrock and AI services have their own commit instruments that stack with EDP. See our cloud contract negotiation practice.
How long does an AWS EDP negotiation typically take?
From engagement open to signed contract, AWS EDP negotiations typically take 10–18 weeks. The longer engagements involve Private Pricing Addenda for specialised services, competitive alternative scoping, or complex Marketplace gating arrangements. AWS Deal Desk approval cycles run on a published cadence; planning around their internal review windows shortens the negotiation by 2–4 weeks.
What should I negotiate in a cloud enterprise discount program before committing?
The non-negotiable list is: ramp protection if actual consumption falls below forecast; break clauses tied to programme delivery milestones rather than annual minimums; Marketplace floor protection; egress waivers as contractual right rather than applied benefit; Enterprise Support cost caps; AI services commit transparency; and a customer-favourable definition of "qualifying spend" against the commit. Most customers negotiate only the headline discount percentage and surrender material value on the structural clauses.
Open a confidential AWS review
Whether you are preparing for EDP renewal, evaluating a Bedrock commit, or modelling the optimal mix of EDP, Savings Plans and RIs, we can model your position within 72 hours.
Request a Confidential Briefing