Converting VMware Workloads to EC2 - Going Cloud-Native with AWS Transform for VMware
Learn about converting VMware workloads to EC2 using AWS Transform for VMware. This article covers automated assessment, conversion plan generation, and phased migration execution.
The Option of Converting from VMware to EC2
There are two main approaches to migrating VMware workloads to AWS. (1) Using Amazon EVS to move the VMware environment as-is to AWS, and (2) using AWS Transform for VMware to convert virtual machines into EC2 instances. EVS is suitable when you want to continue leveraging VMware licenses and skill sets, but VMware licensing costs persist. Transform for VMware, on the other hand, completely eliminates VMware dependency by migrating to a native EC2 environment. Its main benefits are freedom from VMware licensing, access to EC2's extensive instance type catalog, and direct integration with AWS-native services. Released in May 2025, it uses an agent AI to automate everything from assessment to conversion and validation.
Automated Assessment and Conversion Planning
AWS Transform for VMware connects to vCenter Server and automatically collects the VM inventory. It analyzes actual usage data for each VM's CPU, memory, disk usage, and network traffic, then recommends the optimal EC2 instance type (family and size). For example, if a VM with 4 vCPUs and 16 GB of memory has an average CPU utilization of 30%, it would recommend m6i.large instead of m6i.xlarge, performing right-sizing. It detects dependencies from inter-VM communication patterns and automatically generates groups of VMs that should be migrated together (affinity groups). For instance, a three-tier architecture of web server, app server, and DB server would be placed in the same migration wave, while an independent batch server would be classified into a separate wave.
Conversion Process and Validation
The conversion process transforms VM disk images into AMIs (Amazon Machine Images) and launches them as EC2 instances. During this process, VMware Tools removal and AWS-compatible driver injection (ENA network driver, NVMe storage driver), bootloader configuration changes (GRUB updates), and network configuration changes for EC2 metadata service compatibility are all performed automatically. For Windows VMs, EC2Launch v2 configuration is handled, and for Linux VMs, cloud-init setup is automated. After conversion, automated validation runs to verify network connectivity (VPC internal communication, internet access), disk I/O integrity, OS boot and login, and startup of key application processes. If validation fails, detailed logs and remediation guidance are provided. To broaden your knowledge of migration projects, specialized books on Amazon can be a useful resource.
Transform for VMware Pricing
AWS Transform for VMware pricing is based on the number and complexity of VMs being converted. Specific unit pricing requires an individual estimate from your AWS account team. Since converted EC2 instances no longer require VMware licenses, the license cost savings are significant. Before conversion, use Migration Evaluator to analyze the TCO of your current environment and compare it with projected EC2 costs to calculate the return on investment. Optimize post-migration running costs by right-sizing instance types based on Compute Optimizer recommendations.
Summary - Choosing Between EVS and Transform for VMware
If you want to maintain VMware licenses and migrate quickly, EVS is the right choice. If you want to completely eliminate VMware dependency and optimize costs, Transform for VMware is the better fit. A hybrid approach that combines both is also effective: first migrate quickly to the cloud with EVS, then gradually convert to EC2 using Transform for VMware. In either case, the key to success is accurately understanding VM dependencies and resource usage through a thorough pre-migration assessment.