You are responsible for a legacy web application whose server environment is approaching end of life You
would like to migrate this application to AWS as quickly as possible, since the application environment currently
has the following limitations:
The VM’s single 10GB VMDK is almost full
Me virtual network interface still uses the 10Mbps driver, which leaves your 100Mbps WAN connection
completely underutilized
It is currently running on a highly customized. Windows VM within a VMware environment:
You do not have me installation media
This is a mission critical application with an RTO (Recovery Time Objective) of 8 hours. RPO (Recovery Point
Objective) of 1 hour. How could you best migrate this application to AWS while meeting your business
continuity requirements?
A.
Use the EC2 VM Import Connector for vCenter to import the VM into EC2.
B.
Use Import/Export to import the VM as an ESS snapshot and attach to EC2.
C.
Use S3 to create a backup of the VM and restore the data into EC2.
D.
Use me ec2-bundle-instance API to Import an Image of the VM into EC2
Explanation:
https://aws.amazon.com/developertools/2759763385083070
https://aws.amazon.com/blogs/aws/ec2-vm-import-connector/
0
0
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.
0
0