Name: VMware Cloud on AWS
Brand: Amazon Web Services (AWS)
Rating: 4.3 (153 reviews)

Published Oct 13, 2026

01Common complaints

1. If a planned full migration off VMware is expected within 12–24 months - In these cases, direct migration to native cloud services (EC2/EKS or equivalent) may be more cost-effective than an interim managed VMware footprint. 2. If procurement via existing AWS commit/spend programs is critical - The end of AWS resale may require engagement with Broadcom/VMware or resellers, which can complicate purchase and renewal workflows for some organizations. 3. If transparent, self-serve pricing and broad third-party review coverage are required for fast benchmarking - Public review volume for this specific managed offering can be limited on some platforms, and pricing discovery often requires formal quotes. 4. If cloud-native elasticity and lowest-cost per-VM economics are the primary objectives - A managed VMware footprint on dedicated hosts can behave more like a private cloud footprint with less per-VM elasticity than cloud-native primitives.

Deal disqualifiers (poor fit)

Strict budget constraints requiring lowest-cost compute
Strategic plan to exit VMware licensing exposure quickly
Workloads already modernized to containers or cloud-native architectures where managed VMware offers limited value

Commercial and lifecycle limitations

AWS no longer resells VMC on AWS as of April 30, 2024; purchasing and renewal pathways may require engagement with Broadcom/VMware or resellers.
Public discussion indicates concerns about on-demand purchasing flexibility in some commercial models; confirm current terms with the vendor.

Review-signal limitations

Limited review volume on some public review platforms makes it difficult to quantify typical satisfaction and operational responsiveness from a broad sample.

Strategic risk context

Market commentary has discussed broader VMware market dynamics since the Broadcom acquisition; these macro trends may influence vendor strategy and customer expectations, but they do not directly predict outcomes for every customer.

02Why they buy

Evidenced characteristics and consistent market narratives

Operates VMware SDDC software on AWS bare-metal infrastructure as a managed service; provides a VMware operational model on AWS infrastructure.
Reduces immediate application refactoring by enabling lift-and-shift migration of vSphere-based workloads.

Claims that require scrutiny

Broad statements about industry transformation, being "most secure," or having the "most functionality" are vendor marketing claims and should be validated with service-bound SLAs, security attestations, and feature comparisons.

Areas where competitors may have advantages

Pricing transparency and public calculators: Some competitors publish clearer pricing pages and cost tools which can simplify initial TCO modeling.
Competitive messaging from other cloud providers may emphasize cost or integration benefits for their specific platforms; treat competitor comparisons as marketing unless independently verified.

03Field reports

Review-platform availability and limitations

Public review volume on some platforms is limited; review sites may indicate insufficient volume for statistically robust buying insight.
Gartner Peer Insights maintains a listing for the product but portions of Gartner’s content may be gated.

Community sentiment (public discussion boards) — themes and illustrative examples

Community discussions highlight purchasing and licensing impacts from the resale change and a range of operational experiences. Themes include: - Procurement concerns following the end of AWS resale - Questions about on-demand purchasing flexibility under current commercial terms - Anecdotal reports describing architectural validation and operational continuity from some users Note: community postings are anecdotal; current contract terms and vendor communications should be verified for purchasing decisions.

Why customers choose it (recurring reasons referenced in public discussions)

Ability to migrate workloads to AWS without immediate application refactoring
Reuse of existing virtualization operational practices and vSphere tooling
Hybrid connectivity patterns such as L2 extension for specific migration scenarios

Why some customers leave or avoid it (churn drivers cited in public sources)

Licensing uncertainty and perceived cost increases following vendor ownership changes
Procurement friction due to changes in resale and purchasing pathways

Vendor/partner-reported value studies

Partner and vendor channel materials reference third-party studies and customer success stories. These materials often present positive outcomes; organizations should request study methodologies and data to validate applicability to their environment.

AWS-provided migration/adjacent narratives

- AWS has published guidance on migration pathways that include rehosting to EC2 using migration services and an AWS-operated VMware offering (AWS EVS) that runs VMware Cloud Foundation on AWS infrastructure. These alternative options are relevant to procurement and long-term application modernization strategies. Critical note: Vendor case studies and launch announcements typically focus on favorable outcomes and may not reflect median customer experiences. Request independent validation and assess whether case study assumptions apply to your environment.

04Best fit

Company sizes

Organizations that commonly evaluate VMC on AWS tend to have:

Mid-market to very large enterprises
Large existing VMware footprints (substantial numbers of VMs)
Migration programs where refactoring is not feasible in the near term

Industries

Frequent industry adopters include:

Financial services and insurance
Healthcare and life sciences
Manufacturing
Public sector
Large retail organizations

Roles and personas

Infrastructure and virtualization teams (vSphere administrators)
Cloud platform engineering
Network engineering
Security and compliance teams
FinOps and procurement

Pain points addressed

Data center lease exit or hardware refresh avoidance
Disaster recovery extension or expansion
Temporary capacity needs while retaining VMware operational models
Maintaining legacy applications with minimal change during modernization planning

Qualification criteria (strong fit)

Requirement to preserve VMware operational semantics (vCenter, vMotion equivalents)
Need for adjacency to AWS services and networking (Direct Connect and similar)
Willingness to accept relatively higher operational costs in exchange for reduced refactoring effort

05The pitch

What the product does (objective value proposition)

VMware Cloud on AWS (VMC on AWS) is a managed VMware Software-Defined Data Center (SDDC) environment that runs VMware SDDC software on dedicated AWS bare-metal infrastructure. The service enables organizations to run vSphere-based workloads on AWS infrastructure with minimal refactoring of virtual machine images and can be connected to AWS services (storage, databases, analytics) through AWS networking. Important market change: Recently, AWS announced it no longer resells VMware Cloud on AWS; customers are expected to purchase or renew through Broadcom (the parent company of VMware). Existing subscriptions purchased via AWS may continue to be invoiced by AWS until the end of their term.

Target market and positioning

Primary target segments include: - Enterprise and upper mid-market organizations with substantial VMware estates - Organizations with hybrid cloud or data center evacuation requirements - Projects prioritizing lift-and-shift migrations with minimal application refactoring - Regulated environments that require established virtualization operations and governance The product is commonly evaluated against: - Replatforming applications to native AWS services (EC2, EKS) with refactoring - Equivalent managed VMware offerings from other public cloud providers (Azure VMware Solution, Google Cloud VMware Engine) - Alternative virtualization or hyper-converged solutions (Nutanix, OpenShift virtualization, Proxmox in some SMB contexts)

Get a comprehensive analysis of VMware Cloud on AWS including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 13, 2026

01Common complaints

If a planned full migration off VMware is expected within 12–24 months
- In these cases, direct migration to native cloud services (EC2/EKS or equivalent) may be more cost-effective than an interim managed VMware footprint.
If procurement via existing AWS commit/spend programs is critical
- The end of AWS resale may require engagement with Broadcom/VMware or resellers, which can complicate purchase and renewal workflows for some organizations.
If transparent, self-serve pricing and broad third-party review coverage are required for fast benchmarking
- Public review volume for this specific managed offering can be limited on some platforms, and pricing discovery often requires formal quotes.
If cloud-native elasticity and lowest-cost per-VM economics are the primary objectives
- A managed VMware footprint on dedicated hosts can behave more like a private cloud footprint with less per-VM elasticity than cloud-native primitives.

Deal disqualifiers (poor fit)

Strict budget constraints requiring lowest-cost compute
Strategic plan to exit VMware licensing exposure quickly
Workloads already modernized to containers or cloud-native architectures where managed VMware offers limited value

Commercial and lifecycle limitations

AWS no longer resells VMC on AWS as of April 30, 2024; purchasing and renewal pathways may require engagement with Broadcom/VMware or resellers.
Public discussion indicates concerns about on-demand purchasing flexibility in some commercial models; confirm current terms with the vendor.

Review-signal limitations

Limited review volume on some public review platforms makes it difficult to quantify typical satisfaction and operational responsiveness from a broad sample.

Strategic risk context

Market commentary has discussed broader VMware market dynamics since the Broadcom acquisition; these macro trends may influence vendor strategy and customer expectations, but they do not directly predict outcomes for every customer.

02Why they buy

Evidenced characteristics and consistent market narratives

Operates VMware SDDC software on AWS bare-metal infrastructure as a managed service; provides a VMware operational model on AWS infrastructure.
Reduces immediate application refactoring by enabling lift-and-shift migration of vSphere-based workloads.

Claims that require scrutiny

Broad statements about industry transformation, being "most secure," or having the "most functionality" are vendor marketing claims and should be validated with service-bound SLAs, security attestations, and feature comparisons.

Areas where competitors may have advantages

Pricing transparency and public calculators: Some competitors publish clearer pricing pages and cost tools which can simplify initial TCO modeling.
Competitive messaging from other cloud providers may emphasize cost or integration benefits for their specific platforms; treat competitor comparisons as marketing unless independently verified.

03Field reports

Review-platform availability and limitations

Public review volume on some platforms is limited; review sites may indicate insufficient volume for statistically robust buying insight.
Gartner Peer Insights maintains a listing for the product but portions of Gartner’s content may be gated.

Community sentiment (public discussion boards) — themes and illustrative examples

Community discussions highlight purchasing and licensing impacts from the resale change and a range of operational experiences. Themes include:

Procurement concerns following the end of AWS resale
Questions about on-demand purchasing flexibility under current commercial terms
Anecdotal reports describing architectural validation and operational continuity from some users

Note: community postings are anecdotal; current contract terms and vendor communications should be verified for purchasing decisions.

Why customers choose it (recurring reasons referenced in public discussions)

Ability to migrate workloads to AWS without immediate application refactoring
Reuse of existing virtualization operational practices and vSphere tooling
Hybrid connectivity patterns such as L2 extension for specific migration scenarios

Why some customers leave or avoid it (churn drivers cited in public sources)

Licensing uncertainty and perceived cost increases following vendor ownership changes
Procurement friction due to changes in resale and purchasing pathways

Vendor/partner-reported value studies

Partner and vendor channel materials reference third-party studies and customer success stories. These materials often present positive outcomes; organizations should request study methodologies and data to validate applicability to their environment.

AWS-provided migration/adjacent narratives

AWS has published guidance on migration pathways that include rehosting to EC2 using migration services and an AWS-operated VMware offering (AWS EVS) that runs VMware Cloud Foundation on AWS infrastructure. These alternative options are relevant to procurement and long-term application modernization strategies.

Critical note: Vendor case studies and launch announcements typically focus on favorable outcomes and may not reflect median customer experiences. Request independent validation and assess whether case study assumptions apply to your environment.

04Best fit

Company sizes

Organizations that commonly evaluate VMC on AWS tend to have:

Mid-market to very large enterprises
Large existing VMware footprints (substantial numbers of VMs)
Migration programs where refactoring is not feasible in the near term

Industries

Frequent industry adopters include:

Financial services and insurance
Healthcare and life sciences
Manufacturing
Public sector
Large retail organizations

Roles and personas

Infrastructure and virtualization teams (vSphere administrators)
Cloud platform engineering
Network engineering
Security and compliance teams
FinOps and procurement

Pain points addressed

Data center lease exit or hardware refresh avoidance
Disaster recovery extension or expansion
Temporary capacity needs while retaining VMware operational models
Maintaining legacy applications with minimal change during modernization planning

Qualification criteria (strong fit)

Requirement to preserve VMware operational semantics (vCenter, vMotion equivalents)
Need for adjacency to AWS services and networking (Direct Connect and similar)
Willingness to accept relatively higher operational costs in exchange for reduced refactoring effort

05The pitch

What the product does (objective value proposition)

Important market change: Recently, AWS announced it no longer resells VMware Cloud on AWS; customers are expected to purchase or renew through Broadcom (the parent company of VMware). Existing subscriptions purchased via AWS may continue to be invoiced by AWS until the end of their term.

Target market and positioning

Primary target segments include:

Enterprise and upper mid-market organizations with substantial VMware estates
Organizations with hybrid cloud or data center evacuation requirements
Projects prioritizing lift-and-shift migrations with minimal application refactoring
Regulated environments that require established virtualization operations and governance

The product is commonly evaluated against:

Replatforming applications to native AWS services (EC2, EKS) with refactoring
Equivalent managed VMware offerings from other public cloud providers (Azure VMware Solution, Google Cloud VMware Engine)
Alternative virtualization or hyper-converged solutions (Nutanix, OpenShift virtualization, Proxmox in some SMB contexts)

Get a comprehensive analysis of VMware Cloud on AWS including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →