The original hyperscaler VMware service, and the one with the most post-acquisition question marks. Technically excellent, deeply AWS-integrated, expensive, and worth a hard look at the roadmap before you sign anything multi-year.
| Area | VMware on-prem (Broadcom) | VMware Cloud on AWS |
|---|---|---|
| Cost | Per-core subscription plus hardware, facilities, refresh cycles | Per dedicated bare-metal host (minimum cluster sizes apply); typically the most expensive of the hyperscaler VMware services. Eliminates hardware/facility spend; AWS EDP commitments can offset |
| Complexity | Known quantity | Low, full VMware SDDC (vSphere, vSAN, NSX), jointly operated infrastructure |
| Timeline | Renewal-driven | 2–6 months including SDDC and network design |
| Licensing model | Mandatory VCF subscription from Broadcom | Subscription per host, sold by Broadcom post-acquisition; commercial model has shifted, scrutinize terms |
| HA / DR features | Full vSphere HA/DRS/SRM under your control | Same stack plus stretched clusters across AZs and VMware Cloud DR options |
| Backup ecosystem | Universal vendor support | Veeam, Commvault, Druva support VMC; validate appliance placement and egress costs |
| VDI support | Horizon/Omnissa, Citrix | Horizon on VMC supported; not a common VDI destination, validate carefully |
| Container story | Tanzu (bundled) | Adjacent EKS and the broadest cloud-native service catalog in the market |
| Support quality | Broadcom support, widely reported declines | Broadcom-led with AWS infrastructure support underneath, the same support organization you may be trying to leave |
| Best fit | Estates with sunk hardware and stable footprints | AWS-committed orgs with EDP leverage that need workloads adjacent to EC2/S3/RDS |
There is no public rate card for VMware Cloud on AWS. Broadcom's own purchase options documentation states that on-demand host purchases are no longer available, that you must buy subscriptions in advance of deploying an SDDC or adding hosts, and that subscriptions come only through Broadcom direct sales or an authorized reseller. Self-service purchase is gone. The page carries no dollar figures at all. Checked August 31, 2026.
Be blunt about what that means for a business case. You cannot build a defensible VMC budget from public information, and every per-host VMC figure circulating on comparison sites is either someone's estimate or a leaked quote, not a published price. We are not going to invent one here. If VMC is genuinely on your shortlist, the only real number is a written quote with the renewal rate stated, not just the first term.
If the goal is running VMware on AWS rather than buying the VMC product specifically, Amazon Elastic VMware Service is the option with a public price. EVS runs VMware Cloud Foundation on EC2 bare-metal instances inside your own VPC, and you bring portable VCF licensing purchased from Broadcom, the same split you get with Azure VMware Solution and Google Cloud VMware Engine. The rates below are AWS's published US East (Ohio) prices from the Amazon EVS pricing page, checked August 31, 2026.
| Line item | On demand | 3-year savings plan, no upfront |
|---|---|---|
| i4i.metal host | $10.982 per host-hour | $5.08 per host-hour |
| EVS control plane | $0.92 per host-hour | $0.92 per host-hour |
| VPC Route Server endpoint | $0.2025 per endpoint-hour | $0.2025 per endpoint-hour |
The route server rate is the discounted one: AWS bills these endpoints at 73 percent off the standard $0.75, and an environment needs a pair of them. The control plane charge is per host and does not change with instance type.
These are AWS's own published worked examples, not our arithmetic: four i4i.metal hosts plus two route server endpoints in US East (Ohio), at 730 hours.
| Four-host EVS environment, Ohio | Hosts | Control plane | Route server | Monthly total |
|---|---|---|---|---|
| On demand | $32,067.44 | $2,686.40 | $295.67 | $35,049.51 |
| 3-year savings plan | $14,833.60 | $2,686.40 | $295.67 | $17,815.67 |
Committing for three years roughly halves the bill, which is the same lesson the AVS and GCVE rate cards teach. AWS states there are no minimum fees or upfront commitments for EVS, and every published example uses four hosts. If you cannot bring your own Windows Server licensing, AWS sells it through EVS at $0.046 per vCPU-hour, a flat rate that does not vary by region, and it adds up fast: the 384 vCPUs in AWS's own example cost $20,937 a month on their own.
One thing these totals do not include, and it matters: the portable VCF subscription from Broadcom. As with Azure VMware Solution and Google Cloud VMware Engine, Broadcom publishes no list price for it, so the AWS figures above are one half of a two-part bill. Get the VCF half quoted in writing before comparing any of these against a renewal or a managed VMware provider.
VMC is the natural fit when AWS is your committed cloud and your VMware workloads need to live next to AWS-native services. The integration is the deepest of the three hyperscaler options: SDDCs deploy directly into your AWS account structure, VMs reach EC2, S3, RDS, and Lambda over the connected VPC with no internet hop, and AWS Enterprise Discount Program commitments can help fund the move. The technology is mature, this was the first and most battle-tested hyperscaler VMware service, with HCX included for live migration, stretched clusters across availability zones, and a proven DR story via VMware Cloud DR.
Like its peers, it converts hardware refreshes and data-center leases into operating expense, and your vSphere team keeps its tools and runbooks intact.
Two issues deserve plain language. First, cost: VMC is typically the most expensive path on this site, and if your hardware is sunk, moving to it raises your run rate. Second, and unique to VMC, the commercial ground has shifted since Broadcom's acquisition: Broadcom took over selling the service directly, the AWS relationship was renegotiated publicly and messily, and buyers who chose VMC to reduce Broadcom exposure discover they've signed up for more of it, same vendor, same support organization, now wrapped in AWS infrastructure. If your goal is distance from Broadcom plus lower cost, a managed VMware provider (11:11 Systems, Expedient, TierPoint, and peers) at a typical 25–40% below Broadcom-direct achieves both with far less roadmap risk. If your goal is AWS adjacency specifically, fine, but get pricing-trajectory protections in the contract.
Tooling: HCX is included, bulk migration, live vMotion-based moves, and network extension so VMs keep their IPs through cutover. Downtime: depends on the migration method and workload. Validate live-migration eligibility, test dependencies, and plan maintenance and rollback windows before cutover. The real work: SDDC sizing against minimum host counts (small estates overbuy), Direct Connect or VPN design, NSX segmentation planning, egress cost modeling, and backup re-pointing. Contract diligence is part of the migration: given the post-acquisition changes, treat term length, renewal pricing mechanics, and service-continuity language as seriously as the technical runbook, and price AVS and GCVE in the same exercise for leverage. Retraining: minimal; vSphere skills carry over, plus AWS networking fundamentals. Timeline: 2–6 months is typical.
The roadmap uncertainty is real, not theoretical: the service's go-to-market changed hands after the acquisition, and long-term positioning between Broadcom and AWS remains a moving target. You're also not escaping anything, VMC keeps you on VMware software, sold by Broadcom, at premium pricing, with lock-in now spanning two vendors. Minimum cluster sizes make it poor value for small estates; egress fees and storage growth need modeling up front; and a future exit means either another VMware destination or the re-platforming you deferred. Of the three hyperscaler options, this is the one where we most strongly recommend independent eyes on the contract before signature.
For AWS-committed organizations with EDP leverage and a hard data-center exit date, VMC delivers the deepest AWS integration with a near-painless HCX migration. But if Broadcom distance or cost reduction is your motive, VMC accomplishes neither, evaluate it side by side with AVS, GCVE, and a managed VMware provider, and negotiate roadmap protections before committing years.
AWS is your strategic cloud, your workloads need EC2/S3/RDS adjacency, you have EDP commitments to apply, and you've secured contractual clarity on pricing and service continuity.
You want lower cost or less Broadcom exposure, a managed VMware provider at 25–40% below Broadcom-direct delivers both, without the post-acquisition roadmap bet.
It carries more roadmap uncertainty than AVS or GCVE. Broadcom took over direct selling of the service and the AWS relationship changed materially. It works well today, but get contractual clarity on pricing trajectory before multi-year commitments.
Usually not, it's typically the most expensive hyperscaler VMware service. The economics work when it eliminates a hardware refresh, facilities, or a DR site, and when AWS EDP commitments apply.
HCX is included: bulk and live vMotion-based migration with network extension, so most VMs move with little or no downtime and keep their IPs. Projects typically run 2–6 months.
Managed VMware providers like 11:11 Systems, Expedient, and TierPoint typically run 25–40% below Broadcom-direct, often below VMC host pricing, with none of the roadmap questions.
Comparing all eight paths? The top VMware migration solutions guide ranks every option by cost, effort, and fit.
We'll benchmark VMC against AVS, GCVE, and managed VMware provider quotes for your environment, and flag the contract terms that matter. Free, vendor-neutral, no reps.