The Challenge: An EDP Built for Growth That Stalled
In 2022, a Fortune 500 financial services company signed a 5-year AWS Enterprise Discount Program agreement committing to $220M in total cloud spend. At the time, the IT leadership team projected aggressive workload migration—moving 70% of on-premises infrastructure to AWS within 36 months. The EDP was sized accordingly, with year-over-year spend ramps of 28%, 32%, and 35%.
By mid-2024, the migration had materially slowed. Regulatory pressures from their prudential regulator had delayed the movement of core banking workloads to the cloud. A board-level risk review further restricted certain data categories from moving to shared public cloud infrastructure. The company was 31% behind its EDP spend ramp, accumulating a growing liability of unused committed spend that AWS was tracking closely.
With $94M in remaining EDP commitment over 30 months and a realistic spend trajectory of $75M, the organization faced $19M in shortfall penalties—unless they could renegotiate the agreement. Their internal team, without prior EDP restructuring experience, had attempted two rounds of preliminary discussions with AWS that went nowhere. AWS's response was to offer modest private pricing discounts on new services in exchange for extending the commitment, which did nothing to address the underlying trajectory gap.
They engaged us with a clear brief: restructure the EDP to align with realistic spend, eliminate the shortfall penalty exposure, and secure better service-level pricing across their primary workload categories.
Situation Summary
Original EDP: $220M over 5 years | Signed 2022 | Year 3 at risk
Spend shortfall: 31% behind ramp target | $19M penalty exposure
Primary workloads: EC2 compute, RDS, S3, Redshift, SageMaker
Regulatory constraint: Core banking systems excluded from cloud migration
Outcome: EDP restructured to $162M | Shortfall eliminated | $18.7M net savings
Our Approach: Reframing the Negotiation
AWS EDP renegotiations are deliberately difficult. AWS's account teams are incentivized on total committed spend, not on customer satisfaction. The standard AWS playbook when a customer misses ramp targets is to offer superficial concessions—extra credits, minor service discounts—while preserving the core commitment structure. Breaking through this requires understanding what AWS actually values in an enterprise account beyond raw spend.
Phase 1: Spend Archaeology and Forecast Modelling (Weeks 1–3)
We began with a forensic breakdown of the client's actual AWS consumption across all linked accounts. The first finding was significant: approximately $14M of the committed EDP spend was allocated to services with no private pricing discounts—the client was consuming these services at effectively list price despite the EDP.
Second, we identified three emerging workload categories—SageMaker for model training, Amazon Bedrock for LLM inference, and Amazon QuickSight for regulatory reporting—that were growing rapidly and had not been included in the original EDP's discount schedule. These services had become meaningful spend categories in 2023 and 2024, but the client was consuming them at standard rates with no EDP attribution.
We built a 36-month spend model with three scenarios: a conservative regulatory-constrained scenario, a base case, and an accelerated migration scenario contingent on regulatory approval. This model showed AWS that the client could credibly reach $162M–$175M in spend over the remaining term—significantly below the committed $220M, but not the floor that AWS had assumed.
Phase 2: Establishing Negotiation Leverage (Weeks 4–7)
Before approaching AWS with restructuring proposals, we prepared two pieces of leverage that we knew AWS would respond to.
Multi-cloud analysis. We documented the client's options with Azure and Google Cloud for their two largest workload categories. The analysis showed that Azure had materially improved its financial services compliance posture (including FedRAMP equivalents for UK PRA requirements) and could absorb the regulatory-constrained workloads at comparable cost. This was not a bluff—the client genuinely had viable alternatives for 35% of their projected AWS spend.
AWS strategic value articulation. We simultaneously prepared a briefing document for AWS leadership that articulated why this client was worth restructuring for: they were building an AI/ML infrastructure that would generate significant SageMaker and Bedrock consumption over 2025–2028, they had a C-suite mandate to expand cloud adoption once regulatory barriers were resolved, and they were a reference customer in the financial services vertical that AWS values for its enterprise sales motion. The message was: this is a customer worth accommodating.
Phase 3: Structured Renegotiation with AWS (Weeks 8–12)
We initiated formal restructuring discussions directly with AWS's Enterprise accounts team at VP level, bypassing the client's day-to-day account manager who had neither the authority nor incentive to propose substantive changes. This direct engagement is critical in AWS EDP negotiations—the account manager's role is to protect existing commitments, not restructure them.
Our opening position:
- Commitment reduction: Reset total EDP commitment to $162M reflecting realistic spend trajectory
- Shortfall waiver: Waive all shortfall calculations to date and reset ramp targets
- Service expansion: Add SageMaker, Bedrock, and QuickSight to the discounted services schedule
- Discount improvement: Increase existing EC2 and RDS discounts by 8–12 percentage points to reflect updated commitment
AWS's initial counter-position was to offer a 12-month extension with a 15% reduction in commitment, keep all existing discount rates, and add only SageMaker to the schedule. This would have reduced the shortfall exposure but not eliminated it, and provided no meaningful pricing improvement.
Over three rounds of structured negotiation, we used the multi-cloud analysis to demonstrate credible alternatives for the contested workloads. We also introduced evidence of competitor pricing from two comparable institutions that had recently completed EDP negotiations—showing AWS that their proposed discount rates were below market for accounts of this size and growth trajectory.
Phase 4: Final Agreement (Weeks 13–14)
The final restructured EDP:
- Total commitment reduced to $162M over the remaining 30 months
- All historical shortfall calculations waived with no penalty
- New ramp targets reset to achievable levels (no cliff risk)
- EC2 On-Demand discount improved from 18% to 26%
- RDS discount improved from 14% to 22%
- SageMaker, Bedrock, and QuickSight added to schedule at 15%, 12%, and 18% respectively
- S3 storage discount improved from 8% to 13%
- Annual business review obligations clarified and limited to 2 sessions per year
Why AWS Agreed to Restructure
Strategic account risk. AWS's enterprise account team recognized that forcing shortfall penalties on a client with genuine regulatory constraints—constraints that AWS's own compliance teams could verify—would damage the relationship permanently and accelerate multi-cloud adoption. The regulatory story was credible and documented.
AI/ML consumption pipeline. The SageMaker and Bedrock growth trajectory was compelling. AWS could model that this client's AI workloads would likely exceed $40M over the next 3 years. Adding those services to the EDP at discounted rates actually accelerated their adoption—a net win for AWS consumption.
Competitive intelligence. Showing AWS evidence of competitor pricing from comparable institutions forced them to defend their proposed rates on the merits. The pricing comparison demonstrated that their initial counter-proposal was below market, which weakened their negotiating position on the discount schedule.
Outcomes & Financial Impact
Direct savings—commitment reduction: The $58M reduction in total EDP commitment ($220M to $162M) eliminated the shortfall penalty exposure entirely, saving approximately $11.2M in penalties that would have been due under the original agreement structure.
Direct savings—improved pricing: The enhanced discount schedule on EC2, RDS, S3, and newly added services generates an estimated $7.5M in additional savings over the restructured term compared to the prior discount rates. The Bedrock discount alone, applied to projected AI inference workloads, accounts for $2.1M of this figure.
Total net savings: $18.7M against a consulting engagement fee that represented less than 4% of the total value delivered.
Operational impact: The client's FinOps team gained clear, achievable commitment targets aligned to their actual migration plan. The removal of the cliff-risk ramp structure eliminated the quarterly pressure to over-consume in order to meet artificial milestones.
Strategic position: The client now has an EDP structure that accommodates their regulatory constraints while providing a clear on-ramp for expanded cloud consumption once those constraints are resolved. They have also established a direct relationship with AWS leadership at VP level, which will be critical for their next renewal cycle.
Key Lessons: AWS EDP Negotiation Principles
This engagement reinforced several principles that apply broadly to AWS EDP negotiations:
The account manager is not your ally in restructuring. AWS account managers are measured on committed spend. Any restructuring that reduces commitment is a loss for their individual performance metrics. Effective EDP renegotiation requires direct engagement with AWS leadership who can authorize exceptions.
Multi-cloud analysis is your most valuable leverage. AWS prices heavily on perceived switching cost. Demonstrating genuine, documented alternatives for core workloads shifts the negotiation from "how do we accommodate you" to "how do we keep you."
New services are the bridge. AWS will often accept commitment restructuring more readily if the client commits to consuming new services (SageMaker, Bedrock, Data Transfer, etc.) that have high growth trajectories. Framing the restructuring as "rebalancing our commitment toward our actual workload roadmap" rather than "reducing our commitment" changes the tone of the negotiation.
Benchmark pricing across accounts. AWS applies differential pricing based on account team, region, and negotiating history. Enterprise customers who have not compared their EDP discount schedules against market benchmarks are almost certainly leaving money on the table. In this engagement, benchmarking was the single most impactful data point we brought to the negotiation.
Is Your AWS EDP Aligned to Your Actual Roadmap?
Most large enterprises signed their AWS EDP commitments in 2021–2023 based on migration projections that have since shifted. If your actual cloud consumption is tracking below your committed ramp, you have a restructuring opportunity—but AWS will not initiate the conversation.
We have negotiated EDP restructurings with AWS, Azure, and Google Cloud on behalf of enterprises across financial services, healthcare, manufacturing, and the public sector. Each engagement begins with a no-obligation assessment of your current position and realistic savings opportunity.
Request a Confidential EDP Assessment →Request a Confidential AWS Contract Review
We'll review your current EDP agreement and identify restructuring opportunities within 5 business days.
Related Resources
Enterprise Cloud Contract Framework 2026 →
Comprehensive guide to negotiating EDP, MACC, and CUD agreements across AWS, Azure, and Google Cloud.
Complete AWS Vendor Intelligence →
EDP structure, discount benchmarks, AWS account team incentives, and negotiation checkpoints for all AWS service categories.
Cloud Contract Negotiation Services →
How we structure cloud contract engagements, from initial spend analysis through final agreement and ongoing optimization.
Related: Google Cloud CUDS Renegotiation →
How a global retailer renegotiated its Google Cloud committed use discounts and saved $11.4M across a 3-year term.