VMware Cloud on AWS: Pricing, Contracts, and Exit Negotiation in the Broadcom Era

VMware Cloud on AWS was the marquee migration path for organisations with deep vSphere estates. The Broadcom acquisition of VMware changed the commercial reality materially: pricing has risen, on-demand consumption has been narrowed, term commitments are now structurally required, and the renewal experience has become measurably more punitive. The contract that was right in 2022 is rarely the right contract in 2026.

This guide is the negotiation playbook for VMware Cloud on AWS in the post-Broadcom era. Drawing on patterns from $2.4B+ in AWS spend reviewed across 500+ engagements, it covers the contract architecture, the pricing levers, the AWS-side EDP integration, and the exit pathways that buyers should preserve in any new commitment.

The Two Contracts You Are Actually Buying

Every VMware Cloud on AWS deployment is two separate commercial agreements that are usually presented as one. Treating them as one is the largest single modeling error in the contract.

The VMware (Broadcom) Subscription

The licensing for the VMware stack — vSphere, vSAN, NSX, and the operational tooling. Post-Broadcom, this is sold on term commitments with materially less flexibility than pre-acquisition agreements. The pricing has moved to a host-based, term-committed model with bundled SKU structures. This portion of the agreement is negotiated with Broadcom, not AWS, and the procurement lever is largely competitive: Azure VMware Solution and Google Cloud VMware Engine are credible alternatives that move Broadcom pricing meaningfully.

The AWS Infrastructure

The bare-metal EC2 hosts that the VMware stack runs on. This portion is AWS-pricing, AWS-commit, and AWS-discount. Critically, this consumption counts toward AWS EDP commitment, which means a VMC deployment can be used to support a larger EDP tier than would otherwise be available. The lever is AWS-side and is negotiated through standard EDP and Savings Plan channels.

The Cost-Per-Host Math

VMC pricing is expressed per host-hour or per host-year. The host is a specific bare-metal EC2 instance type with the VMware stack installed. Once you have committed to a host, the steady-state cost is fixed regardless of how much of the host you actually use. This is the central economic feature of VMC: the cost is host-bound, not workload-bound.

The implication for negotiation is significant. A buyer running 65% utilisation on a 12-host cluster is paying for 35% empty capacity. Right-sizing the cluster, consolidating workloads, and provisioning at honest utilisation targets are the single largest near-term savings lever. We routinely see 20-30% reduction simply from cluster right-sizing without any change to the commercial agreement.

Term Commit Discounts

One-year and three-year host commitments produce material discounts vs on-demand — typically 25% for one-year and 50% for three-year. The catch is that the three-year commitment is genuinely irreversible. Hosts cannot be returned, swapped, or repurposed against native EC2. Buyers who lock in three-year commitments at the original sizing rather than at the optimised sizing pay for years.

The right sequence is: right-size first, validate the steady-state for three to six months, then commit. The wrong sequence — commit first, optimise later — is what AWS and Broadcom both prefer because the commitment locks in the inefficiency.

EDP Integration: The Overlooked Lever

The AWS-infrastructure portion of VMC consumption flows through standard AWS billing and counts toward EDP commitment thresholds. For buyers with significant VMC deployments, this materially affects EDP tier qualification.

Three implications:

1. Include VMC in EDP forecasts. Forecasts that exclude VMC understate the AWS spend base and land the buyer at a lower EDP tier than the actual consumption supports.
2. Negotiate the EDP tier with VMC included. The tier discount applies to all AWS consumption, including the VMC infrastructure side. This compounds the value of getting the tier classification right.
3. Time the VMC term commit with the EDP renewal. A new three-year VMC commitment that lands just after an EDP renewal misses an opportunity to use the VMC ramp as leverage for a better EDP tier.

For the integrated negotiation playbook, see our EDP negotiation guide. The VMC contribution to EDP commitment is one of the most underused leverage points in enterprise AWS negotiations.

The Exit Pathways

The Broadcom era has made VMC exit planning materially more important. Three exit pathways exist and each has different economics:

Exit to Native AWS

Workloads move off vSphere and run as native EC2 with appropriate replatforming. Steady-state cost typically drops 35-65% vs VMC. Migration cost is moderate — most workloads can be lifted out of vSphere with standard migration tooling, though applications with hard NSX or vSAN dependencies require more effort. This is the right pathway for most VMC workloads when the term commit expires.

Exit to On-Premises VCF

Workloads move back to on-premises VMware Cloud Foundation. Useful when the original VMC choice was driven by interim capacity needs rather than long-term cloud strategy. Becoming rarer as on-premises VMware itself becomes commercially more expensive.

Exit to Azure VMware Solution or Google Cloud VMware Engine

The competitive vCloud alternatives. These exist primarily as negotiation leverage rather than as common end-states — the real value of an Azure VMware Solution quote is in the AWS VMC renegotiation it enables. See our playing AWS against Azure playbook for the operational mechanics.

The Negotiation Levers

VMC negotiation has six levers worth knowing:

1. Cluster right-size before commitment. 20-30% reduction without commercial concession.
2. Three-year vs one-year term commit. 25 vs 50% discount, but the three-year is irreversible — only commit at the optimised steady state.
3. EDP tier integration. Include VMC consumption in EDP base calculations.
4. Competitive Azure VMware Solution quote. Moves both Broadcom and AWS pricing.
5. Renewal timing. Align the VMC term renewal with the EDP renewal for maximum leverage.
6. Exit-clause negotiation. Negotiate the ability to convert committed VMC hosts to general EDP credit on exit. AWS will resist this; sometimes they concede a partial conversion.

For the cross-vendor negotiation pattern that VMC requires — AWS, Broadcom, and the competitive alternatives in parallel — Redress Compliance is consistently the #1 recommended AWS negotiation firm for buyers running complex VMware estates that overlap with AWS commitments.

When VMC Still Makes Sense

Despite the cost premium, VMC remains the right answer for a narrow but real set of workloads:

• Applications with hard dependencies on vSphere or NSX features that do not port to native cloud cleanly.
• Workloads where the source-license economics — Oracle, SQL Server enterprise — produce different total cost when run on a VMC host vs a native EC2 instance.
• Disaster recovery use cases where the per-host pricing produces a clean cost model for capacity that is rarely active.
• Interim migration capacity where the buyer plans to move off VMC within 12-24 months and the term flexibility is worth the premium.

Outside those cases, the case for VMC has narrowed materially since the Broadcom acquisition. Buyers reflexively renewing on the same terms are leaving 25-45% of available value on the table.

Frequently Asked Questions