Migrating Windows and Linux EC2 instance to VMware Cloud on AWS using vCenter Converter

Products

VMware Cloud on AWS

Issue/Introduction

With the release of vCenter Converter 6.4, it is now possible to migrate AWS EC2 instances to VMs on VMware Cloud on AWS SDDCs. This new version is compatible with vSphere 8.0 and introduces the capability to convert AWS EC2-based workloads into VMware VMs running on vSphere.

vCenter Converter 6.4 supports the conversion of workloads based on MS Hyper-V and AWS EC2. It also allows for conversion between different VMware virtual formats such as Workstation and Fusion. Supported virtual workloads include Windows, Linux Ubuntu, CentOS, and Red Hat Enterprise Linux.

However, it's important to note that vCenter Converter 6.3 does not support the conversion of EC2 instances on VMware Cloud on AWS.

During the migration process, there are some aspects that vCenter Converter 6.4 does not handle.

These include network security rules, monitoring, and backup reconfiguration for the newly converted VMs. Additionally, it does not cover OS and application licensing for the converted VMs.

Other means of connecting to EC2 instances, like Elastic IP (EIP), are also not addressed.

After migrating an EC2 instance to VMware Cloud on AWS using vCenter Converter, it's essential to update the VM's IP address as vCenter Converter Standalone does not provide L2 network migration. You should also update any infrastructure that points to the new IP, including DNS and associated load balancers.

If the source VM is not stateless, it is recommended to shut down the applications running on the source instance during the migration process to prevent data loss.

To summarize, vCenter Converter 6.4 enables the migration of EC2 instances to VMware Cloud on AWS, but it's important to consider the aspects that it does not cover, such as network security rules, monitoring, backup reconfiguration, licensing, and alternative means of connection. Additionally, updating the IP address and related infrastructure is necessary, and caution should be exercised with stateful source VMs to avoid data loss.

Symptoms:

Converting an EC2 ubuntu Linux into VMC fails

Resolution

Sample Conversion Process for a Linux and Windows EC2 Instance

Using Remote Desktop (RDP) connect to your Windows Converter Server VM
Launch the VMware vCenter Converter Standalone Client
Choose “Connect to local server.”
Click on “Convert Machine.”
Choose either “Remote Windows machine” or “Remote Linux machine” (as appropriate).

For Windows systems:
If the vCenter Converter agent was set up with something other than the default listener (TCP/9089) you must specify the port in the “IP address or name” input field. For example 192.168.1.10:443. If you utilized the default listener port, you may elide the port number (ex: 192.168.1.10)
Authentication is username/password only.

For Linux systems:
If your Linux system is using a non-standard SSH server port (something other than TCP/22 you must specify the port in the “IP address or name” input field. For example: 192.168.1.10:2222. If you utilized the standard SSH server port, you may elide the port number (ex: 192.168.1.10)
Authentication is username/password or username plus private key (with optional passphrase). Please be mindful of any security implications if you choose to copy your private SSH key for your EC2 instance to this system.

Select VMware Infrastructure Virtual Machine as the destination type.
Enter your SDDC vCenter’s fully qualified domain name (for example: vcenter.sddc-A-B-C-D.vmwarevmc.com), username (ex: [email protected]), and password.

If you are using Connected VPC method, you must select proxy mode.
If you are using the SDDC Groups method, do not select proxy mode.

When configuring the destination for your pending converted VM, be mindful to select only resources you have access to (ex: Workload Datastore and Workloads folder) to avoid permission errors.
Review the virtual hardware properties of the pending converted VM to ensure it uses the converted VM network established in an earlier setup.

Note: the migration process does not shut down the source EC2 VM.

Post conversion:

Validate the converted VM.
Install VMware Tools
Shut down the source EC2 instance and direct any applications to the new VM.

Workaround:

N/A

Additional Information

https://customerconnect.vmware.com/downloads/get-download?downloadGroup=VCENTER_STANDALONE_640_BETA

https://vmc.techzone.vmware.com/resource/designlet-migrating-aws-ec2-instances-vmware-cloud-aws-using-vcenter-converter-64#summary-and-considerations

Impact/Risks: