The Hidden AWS Discount Opportunity

When enterprises sign AWS Enterprise Discount Plans (EDPs, now called PPAs), they typically negotiate based on their current spend profile. But that profile is often artificially fragmented: subsidiaries operate on separate AWS accounts, business units have their own cloud budgets, and acquired companies haven't yet consolidated their infrastructure.

This fragmentation is costing you 5-10% in lost discounts. A company with $3M in fragmented AWS spend across three subsidiaries qualifies for the $2M-$5M tier (15-20% discount). Consolidated into a single commitment, that same company could hit the $5M+ tier (20-30% discount) and unlock an additional $300K-$600K annually.

But consolidation isn't just about aggregating spend. It's about timing, structuring, and protecting yourself in M&A scenarios where subsidiary carve-outs become critical.

Why Fragmented AWS Spend Costs More

AWS discount tiers are built on volume thresholds. Each tier has specific pricing breaks that AWS will defend aggressively during renegotiation.

  • $500K-$1M annual commit: 6-9% discount
  • $1M-$1.5M annual commit: 10-12% discount
  • $1.5M-$2M annual commit: 12-15% discount
  • $2M-$5M annual commit: 15-20% discount
  • $5M+ annual commit: 20-30%+ discount (varies)

The discount jumps at each threshold are substantial. Moving from $1M to $1.5M spend bumps you from 10-12% to 12-15%—a 3% absolute swing. But moving from $1.5M to $2M jumps you to 15%, and then to the $2M-$5M tier at 15-20%.

When your subsidiaries operate independently, each is locked into a lower tier. Subsidiary A with $1.2M annual spend gets 10-12% discount. Subsidiary B with $900K gets 6-9%. Subsidiary C with $500K also gets 6-9%. Combined, that's $2.6M at an average 8-10% discount ($208K-$260K savings).

Consolidated into a single $2.6M commitment, you're in the $2M-$5M tier at 15-20%, saving $390K-$520K annually. That's an additional $130K-$310K in pure discount uplift—just from consolidation.

"The largest AWS discount wins we've seen are not from aggressive negotiation tactics—they're from simple consolidation. Companies leaving subsidiary AWS spend on separate agreements are leaving millions on the table."

Identifying Consolidation Opportunities

Before you approach AWS with a consolidation proposal, map your entire AWS footprint. This includes:

Direct Subsidiaries and Acquired Companies

When you acquire a company, its AWS infrastructure rarely transitions immediately to your master AWS account. The acquired entity typically keeps separate AWS accounts for months or even years post-close, citing "operational continuity" or "minimal disruption risk." That's AWS staying out of your M&A integration—and keeping your spend fragmented.

Map all recently acquired companies and their AWS annual spend. If you acquired three companies in the last 18 months and their combined AWS spend is $2M+, consolidation should be a priority in your post-acquisition integration.

Business Unit and Division Budgets

Large enterprises often grant business units their own AWS accounts and budgets for autonomy. Finance loves this because it enables charge-back models (each BU pays for its own cloud). But it fragments your negotiating power with AWS.

Tally total AWS spend across all BUs, then model what happens if you consolidated to a single master account with linked member accounts (AWS Organizations).

Development, Staging, and Production Environments

Some enterprises run separate AWS accounts for dev, staging, and production (often for security or compliance isolation). This is operationally sound but economically inefficient. You can tighten this—for example, by keeping only production and pre-production in separate accounts, and collapsing dev/test into a shared account under your Organizations structure.

The M&A Catch: Acquisitions with Separate AWS Accounts

Consolidating subsidiary AWS spend is straightforward in theory but often blocked by M&A complexity in practice.

The Integration Timeline Mismatch

Your company acquires a subsidiary, but AWS contract consolidation requires moving that subsidiary's AWS account under your master Organizations account. IT integration timelines often slip past 90 days, which delays AWS EDP consolidation. Meanwhile, your EDP renegotiation window is approaching, and you're counting on consolidated spend that hasn't migrated yet.

Plan AWS consolidation as a formal post-acquisition milestone. Include it in your integration project plan with specific timelines and ownership. Don't assume it'll "just happen."

Tax and Legal Entity Separation

Some subsidiaries remain legal entities (for tax, compliance, or investor reporting reasons) even after acquisition. AWS Organizations allows linking accounts from different legal entities, but it requires explicit co-governance—your parent account is the "payer account" and the subsidiary account is a "member account."

AWS will consolidate spend across these structures for EDP pricing, but you need to negotiate the terms carefully: Who pays the bill? If the subsidiary account generates cost overruns, who's liable? If the subsidiary is later divested, what's the carve-out mechanism?

Cultural and Operational Resistance

The subsidiary's CTO wants to keep their own AWS account for operational independence. The finance team wants separate cost tracking. The security team worries about account-level isolation. All legitimate concerns, but they're delaying a consolidation that could save $200K+ annually.

Make the business case explicit: Show the subsidiary's AWS team how consolidated EDP pricing reduces their per-unit cloud costs, enabling them to build more infrastructure at the same budget. That reframes consolidation from "losing control" to "getting more resources."

How to Structure Consolidated AWS Organization

AWS Organizations is the mechanism that enables consolidation. It's free, and it aggregates spend across all linked accounts for discount purposes.

Master Account (Payer Account)

Set up one master AWS account that will be the EDP holder and the consolidated billing entity. This is typically your parent company's main AWS account. All subsidiary and BU accounts link under this master account via AWS Organizations.

Member Accounts (Linked Accounts)

Link all subsidiary, BU, and division accounts as member accounts under your master account. AWS aggregates all usage across these accounts for EDP pricing purposes.

You don't need to migrate workloads or consolidate infrastructure. Just link the accounts. AWS sees the consolidated spend profile and applies EDP pricing across the entire organization.

Reserved Instances and Savings Plans Sharing

One massive advantage of Organizations: Reserved Instances (RIs) and Savings Plans purchased in the master account automatically cover usage in any member account. This flexibility allows you to:

  • Buy RIs/SPs at the organization level, benefiting from larger pool discounts
  • Shift RI/SP coverage between accounts dynamically (if Subsidiary A reduces workloads, coverage can shift to Subsidiary B)
  • Simplify RI/SP management from "per-account" to "organization-wide"

This is a material cost advantage. You'd otherwise need to forecast each subsidiary's RI needs separately, risking under-purchasing (loss of discount) or over-purchasing (wasted capacity).

Enterprise Support Agreement Consolidation

AWS requires all EDP customers to purchase Enterprise Support. Typically, that's a single organization-wide Enterprise Support agreement ($15K+/year, depending on spend), rather than separate Support contracts for each subsidiary.

This consolidation of support also means unified case management, priority escalation, and TAM (Technical Account Manager) coverage across all accounts—a subtle but valuable operational benefit.

Subsidiary Carve-Out Protections

Here's the critical negotiation challenge: If you consolidate subsidiary AWS spend into your master EDP, and then later divest one of those subsidiaries, you face a massive shortfall risk.

Example: You consolidate four subsidiaries into a $6M annual EDP commitment at 25% discount ($4.5M spend at list price). Two years later, you divest Subsidiary D, which was contributing $1.5M of that spend. You're now short $1.5M against your $6M commitment and owe AWS the shortfall penalty: $1.5M.

Negotiate carve-out provisions into your EDP explicitly:

Subsidiary Exclusion Rights

Request language that allows you to remove a subsidiary account from the consolidated EDP if that subsidiary is divested, sold, or transferred, without triggering shortfall penalties on the remaining consolidated commitment.

Example language: "In the event Customer divests, sells, or transfers a subsidiary account linked to the consolidated EDP, Customer may terminate EDP coverage for that account effective upon the closing of such divestiture, and the annual commit shall be proportionally reduced by the divested account's contribution. No shortfall penalty shall apply to the termination of coverage for the divested account."

AWS will resist this because it acknowledges that your consolidated commitment isn't truly "sticky"—you might reduce it post-acquisition. But in deals with clear divestiture plans (e.g., you're buying and quickly flipping a division), this is worth negotiating.

Recommitment at Divested Levels

If AWS won't grant automatic carve-outs, negotiate a "recommitment trigger": if you divest a subsidiary, you can renegotiate the consolidated EDP to exclude that subsidiary's spend, rather than paying a shortfall.

This is weaker than carve-out rights (it still requires renegotiation and AWS goodwill), but it's better than being locked into a commitment you can't reduce.

Change of Control Clauses

If your company undergoes a major change of control (private equity acquisition, strategic merger, etc.), request the right to re-evaluate the consolidated EDP. Your acquirer may have different cloud strategies or existing AWS commitments, and forcing you to maintain a consolidated EDP from the previous regime could be untenable.

The Consolidation Timeline

Timing is critical. AWS EDP negotiations typically happen 90 days before your current agreement expires. If you're planning consolidation, it needs to be complete (with all subsidiary accounts linked and spend aggregated) well before that window opens.

T-12 Months: Identify and Quantify Opportunities

Map all subsidiary AWS spend. Model the impact of consolidation on your EDP tier. Identify any legal, compliance, or operational blockers to linking accounts.

If you're planning an acquisition, factor in AWS consolidation as a post-close integration milestone (6-month target).

T-9 Months: Plan and Execute Account Linking

Work with IT to link all subsidiary accounts under your master AWS Organizations account. This is operationally straightforward but often requires internal stakeholder alignment (security, finance, ops approvals).

Allow 4-6 weeks for technical execution and another 2-4 weeks for validation.

T-6 Months: Audit Consolidated Spend Profile

Verify that AWS is correctly aggregating all account usage. Pull your organizations billing report and confirm that all subsidiary spend is captured.

This is also the time to lock in any organizational optimizations: consolidating RIs/SPs, aligning Reserved Instance purchases, unifying Enterprise Support agreements.

T-3 Months: Prepare EDP Renewal Proposal

Begin EDP negotiations with AWS. Lead with your consolidated spend profile and the improved tier positioning. Show AWS that consolidation is complete and sustainable.

Request that your EDP proposal includes carve-out and change-of-control provisions (from the previous section).

T-0: Execute and Lock In

Sign your new EDP with the consolidated structure, improved tier, and protective carve-out language.

Pitfalls and How to Avoid Them

Pitfall 1: Premature Consolidation Without Accounting for Growth

You consolidate subsidiaries into a $4M commitment, but two of them are hypergrowth divisions that hit $5M+ combined spend in year two. You're underwater on your EDP, and renegotiating is difficult because AWS knows you're locked in.

Solution: Model subsidiary growth separately before consolidating. If a subsidiary is growing 40%+ annually, consider keeping it on a separate, smaller commitment until growth stabilizes.

Pitfall 2: Ignoring Post-Consolidation Governance

After consolidation, subsidiary teams still operate their AWS accounts independently—they just happen to be linked. You have no visibility into whether they're optimizing costs, following architectural best practices, or flagging overspend.

Solution: Implement organizations-level cost allocation tags and FinOps governance. Track per-subsidiary AWS spend monthly. Tie subsidiary budget accountability to actual cost tracking.

Pitfall 3: Missing RI/SP Optimization Opportunities

You consolidate accounts but continue purchasing RIs separately per subsidiary. You leave the RI/SP sharing benefit of Organizations on the table.

Solution: After consolidation, audit existing RIs/SPs. Consolidate RI purchases at the organization level. Move to Savings Plans, which are more flexible than RIs and cover both compute and data transfer.

Pitfall 4: Failing to Negotiate Carve-Out Protection

You consolidate, improve your discount, and execute a 3-year EDP. Then, your company is acquired and the new owner wants to migrate some subsidiary workloads to their existing cloud contracts. You're locked into the consolidated EDP with no exit valve.

Solution: Negotiate carve-out rights upfront, especially if M&A is on the horizon or if you're consolidating recently acquired subsidiaries.

The Role of Staged Consolidation

If full consolidation is operationally or politically infeasible, consider staged consolidation: move the largest subsidiary or BU first, prove the benefits, and incrementally add others.

Example: Your company has four subsidiaries: A ($1.2M spend), B ($800K), C ($600K), D ($400K). Instead of consolidating all four immediately, consolidate A and B first ($2M, hitting the $2M-$5M tier). Once integrated and running smoothly, add C, then D.

Staged consolidation:

  • Reduces execution risk (fewer moving parts at once)
  • Proves the financial benefit to skeptical business unit leaders
  • Allows you to hit each new tier incrementally as you consolidate, rather than leaving money on the table

Consolidation and AWS Marketplace

One note on AWS Marketplace procurement: if you're consolidating subsidiary spend, remember that Marketplace purchases offset up to 25% of your EDP commit. If you're consolidating to a $5M EDP and using $1M in Marketplace spend, your effective cash commitment is only $4M (AWS credits the Marketplace spend against the commit, and you only pay on the overage beyond that).

Factor Marketplace behavior into your consolidation strategy. If a subsidiary heavily uses Marketplace ISVs, its "true" EDP commitment is lower than it appears.

Recommendations

  1. Audit your AWS spend now: Map all subsidiary, BU, and acquired company AWS accounts and their annual spend. Model the tier improvement from consolidation.
  2. Link accounts via Organizations: If you haven't already, set up AWS Organizations with your master account as the payer and all other accounts as members. This is free and operationally simple.
  3. Consolidate 6-12 months before EDP renewal: Time consolidation to be complete and stable before your EDP negotiation window opens. This shows AWS a mature, intentional approach.
  4. Negotiate carve-out provisions: If you're consolidating recently acquired or divest-able subsidiaries, build in language that allows you to remove them from the consolidated EDP without shortfall penalties.
  5. For enterprise consolidation efforts ($5M+ spend): Hire AWS EDP consolidation specialists to structure your deal and negotiate carve-out protections.
  6. Optimize RI and Savings Plans: After consolidation, consolidate your Reserved Instance and Savings Plan optimisation strategy to leverage cross-account sharing.
  7. Align with broader AWS strategy: Embed consolidation into your overall AWS multi-cloud negotiation and leverage strategy.

Related Resources

To deepen your consolidation and EDP negotiation strategy, explore these guides:

Ready to consolidate and improve your AWS discount structure?

Get a consolidation assessment from our team.
Start Assessment →