The new Amazon EC2 VM Import Connector is a virtual appliance (vApp) plug-in for VMware vCenter. Once installed, you can import virtual machines from your VMware vSphere infrastructure into Amazon EC2 using the GUI that you are already familiar with. This feature builds on top of the VM Import feature that I blogged about late last year.
The Connector stores separate AWS credentials for each vCenter user so that multiple users (each with separate AWS accounts) can use the same Connector. The account must be subscribed to EC2 in order to use the Connector.
You can download the Connector from the AWS Developer Tools page. You'll need to make sure that you have adequate disk space available, and you'll also need to verify that certain network ports are open (see the EC2 User Guide for more information). The Connector is shipped as an OVF template that you will deploy with your vSphere Client.

After you've installed and configured the Connector, you can import any virtual machine that needs the following requirements:
- Runs Windows Server 2008 SP2 (32 or 64 bit).
- Currently turned off.
- Uses a single virtual hard drive (multiple partitions are OK) no larger than one terabyte.
Importing is a simple matter of selecting a virtual machine and clicking on the Import to EC2 tab:

The import process can take a couple of hours, depending on the speed and utilization of your Internet connection. You can monitor the progress using the Tasks and Events tab of the vSphere Client.
As is always the case with AWS, we started out with a core feature (VM Import) and are now adding additional capabilities to it. Still on the drawing board (but getting closer every day) are additional features such as VM Export (create a virtual machine image from an EC2 instance or AMI), support for additional image formats and operating systems.
-- Jeff;


Feature request:
Make EC2 VM Import Connector work with VMware vSphere client. We run a few ESXi hosts without vCenter. I tried the EC2 VM Import Connector today on our VMware vSphere client and registering failed.
Posted by: Jayan Kandathil | March 04, 2011 at 01:40 PM
I may be wrong but as the vApp plug-in is running in VMware vCenter wouldn't it make more sense to call the function/tab "Export to EC2" instead of "Import to EC2"? The current name seems a little bit AWS-centric to me.
Otherwise: Amazing!
Posted by: Karsten | March 05, 2011 at 04:48 AM
Any timeframe on when the export feature will be ready?
Posted by: eske | March 08, 2011 at 02:10 PM
Is there any update on AWS plans to have the Import Connector supported on VSphere 5? It seems odd that VSphere4 is supported but not V5.
Posted by: M Hendrickse | March 21, 2012 at 04:31 AM