All posts
Migration

Leaving VMware Licensing Pressure on AWS: Amazon EVS vs Rehosting to EC2 vs Modernizing

By

October 25, 2026

6 min read

Amazon EVS runs VMware Cloud Foundation inside your VPC on bare-metal EC2, with your own Broadcom licences. Rehosting with AWS Application Migration Service drops VMware entirely. Modernizing takes longest and saves most. The cost, speed and risk of each.

VMware
Amazon EVS
Migration
AWS MGN
EC2

Broadcom's move to subscription-only VMware Cloud Foundation bundles pushed many companies to price an exit. On AWS there are three realistic paths, and most estates end up using more than one.

The three paths

Amazon EVS

Rehost to EC2

Modernize

What it is

VCF running in your VPC on bare-metal EC2 (i4i and i7i), managed through EVS

VMs converted to EC2 instances with AWS Application Migration Service

Workloads moved to containers, managed databases or serverless

VMware licences

Still required: bring your own VCF subscription

Not needed

Not needed

Speed

Fastest: vMotion and HCX, same tools and runbooks

Weeks per wave, mostly automated

Months per application

Operations change

Minimal

Moderate: EC2, AMIs, Systems Manager

Large

AWS cost

Bare-metal instances plus an EVS control plane fee ($0.92 per instance-hour in US East Ohio)

EC2, right-sized per VM

Usually lowest at steady state

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

When each fits

  • EVS: a data-center exit with a hard deadline, a team whose skills and tooling are VMware, or workloads that cannot be touched yet. It moves the hardware problem, not the licence problem. Treat it as a staging area.

  • Rehost: most general-purpose Windows and Linux VMs. AWS Application Migration Service is free for 90 days per server, replicates continuously and lets you test cutover before you commit. Right-size as you go; on-premises VMs are typically over-provisioned.

  • Modernize: the handful of applications that matter most and change most often, where containers or a managed database will pay back the effort.

How we run it

  1. Inventory and group VMs by application, owner and dependency. The dependency map decides the wave plan.

  2. Price all three paths per group, including the VCF subscription you would keep under EVS.

  3. Move the easy rehost waves first to build confidence and shrink the VMware footprint, and with it the next licence renewal.

  4. Use EVS only for what cannot move by the deadline, with an exit date written down.

  5. Modernize the few applications where the business case is clear, after they are safely on AWS.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.