Cloud Continuity Guide — Data Center Infrastructure

AWS VMware Cloud on AWS (VMC): Deployment Architecture and Use Cases

A comprehensive guide to AWS VMware Cloud on AWS covering deployment architecture, use cases, and integration strategies. Learn how VMC serves as the transitional path for VMware workloads moving to the cloud while maintaining full compatibility with existing operations.

16 min read
VMware Cloud AWS Hybrid Cloud Infrastructure Modernization

AWS VMware Cloud on AWS (VMC) runs VMware vSphere natively on AWS infrastructure, providing a direct path for VMware workloads to move to the cloud without application refactoring, disk format conversion, or operations team retraining. VMC maintains full VMware compatibility — vCenter, ESXi, vSAN, NSX — while eliminating on-premises hardware and licensing costs.

Within the AIM infrastructure modernization strategy, VMC serves a specific operational role: it's the transitional path for workloads that aren't ready to migrate off VMware entirely. While Nutanix AHV handles the majority of workload migration on-premises, VMC ensures no VMs get stranded during the transition. Every workload gets a defined path forward, whether that's immediate migration to a new hypervisor or a staged transition through VMC.

The key distinction is that VMC is not a permanent destination — it's infrastructure continuity that buys time for strategic application modernization. Organizations use VMC to break the dependency between infrastructure refresh cycles and application refactoring timelines. You can eliminate on-premises VMware licensing and hardware immediately while building the capability to re-platform applications over a longer timeline.

VMC is not a standalone strategy — it's one component of the broader AIM infrastructure modernization program that includes on-premises hypervisor consolidation, storage modernization, and cloud adoption. The key is understanding how VMC integrates with other AIM modernization initiatives to create a cohesive path forward for all workloads.

The integration starts with workload classification during the AIM assessment phase. Every workload in the environment is evaluated and classified: migrate to alternative hypervisor (typically the majority), move to VMC (VMware-dependent workloads), re-platform to cloud-native services (applications ready for modernization), or retire/replace (end-of-life systems). This classification determines which workloads take which path — no VM is left without a plan.

For workloads migrating to alternative hypervisors on-premises, platforms like Nutanix AHV provide the target environment with integrated storage, networking, and management. The migration process uses tools like Nutanix Move to convert VMs from VMware to AHV, handling the technical conversion while maintaining application compatibility. This path typically handles 70-80% of most organizations' VM estates — general-purpose workloads that don't have deep VMware dependencies.

Key Takeaways

1
VMC serves as a transitional path for VMware-dependent workloads, not a permanent cloud destination
2
The platform eliminates on-premises VMware licensing and infrastructure costs while maintaining full operational compatibility
3
Integration with broader modernization programs ensures all workloads have defined migration paths
4
Deployment patterns should align with specific use cases — parallel migration, DR, burst capacity, or migration staging
5
Unified operations across hybrid environments prevent operational fragmentation and maintain migration momentum
6
Economic evaluation must include eliminated infrastructure costs and operational overhead, not just direct VMC pricing

Explore Related Solutions

FAQs
How is VMC different from AWS Elastic VMware Service (EVS)?

VMware Cloud on AWS (VMC) is a joint offering between VMware and AWS that provides VMware's SDDC stack running on AWS infrastructure. AWS Elastic VMware Service (EVS) was AWS's attempt to create a native VMware service, but it was discontinued in 2024. VMC remains the primary option for running VMware workloads on AWS infrastructure.

Does VMC eliminate all VMware licensing costs?

VMC includes VMware licensing in its consumption-based pricing — you stop paying Broadcom directly for the workloads running on VMC. However, the VMware licensing cost is embedded in the VMC hourly rate. The economics are typically favorable compared to on-premises renewal costs, especially when you factor in eliminated hardware, power, cooling, and operational overhead.

Can workloads on VMC access on-premises resources?

Yes. VMC environments connect to your on-premises infrastructure via AWS Direct Connect or VPN. This enables hybrid workflows where some workloads run on VMC, others on AHV on-premises, and both access shared storage, databases, or application services across environments.

Is VMC intended to be permanent?

Within the AIM strategy, VMC is a transitional path — not a permanent destination. It buys time for VMware-dependent workloads while you build the capability to refactor or re-platform them. Some organizations may keep specific workloads on VMC long-term if the economics and operational model work, but the goal is to systematically reduce VMware dependency over time.

How does IVI manage VMC alongside on-premises infrastructure?

Aegis co-managed operations span both on-premises and cloud environments. The same operational model — performance monitoring, incident response, configuration management, lifecycle operations — applies to VMC workloads as it does to Nutanix, Pure Storage, and Arista infrastructure on-premises. Your team gets unified operational visibility across all environments.

Planning a VMware Cloud Migration Strategy?

IVI helps enterprises evaluate VMC as part of comprehensive infrastructure modernization programs, ensuring every workload has an optimal migration path.

Start a VMware Assessment