- You need to identify your AWS_ACCESS_KEY and AWS_SECRET_KEY
- Once you have that identified, place those in your environment variables, i.e, computer properties/etc
- Now Issue the following to covert your virtual instance:
- ovftool “C:\virtualinstance.vmx” “C:\ovf”
- Now comes the fun part. Navigate to your EC2 api tools and execute “ec2-import-instance virtualinstance.vmdk -f VMDK -t m1.small -a x86_64 -b ec2-data-import-export -o %AWS_ACCESS_KEY% -w %AWS_SECRET_KEY% –region us-east-1”
- You know should see, “Requesting volume size: 40 GB TaskType IMPORTINSTANCE TaskId import-i-fgnffe5k ExpirationTime 2014-02-18T15:36:07Z Status active StatusMessage Pending InstanceID i-45d4a364 DISKIMAGE DiskImageFormat VMDK DiskImageSize 10522068992 VolumeSi ze 40 AvailabilityZone us-east-1c ApproximateBytesConverte d 0 Status active StatusMessage Pending Creating new manifest at ec2-data-import-export/8d2010ca-cc64-4f16-967e-e90cc513 e3d4/Windows_Server_2008_R2_x64-disk1.vmdkmanifest.xml Uploading the manifest file Uploading 10522068992 bytes across 1004 parts 0% |————————————————–| 100% |==================================================|”
- Step 5 will run in the background and you can check on the status using, “ec2-describe-conversion-tasks import-i-fgnffe5k -O %AWS_ACCESS_KEY% -W %AWS_SECRET_KEY% –region us-east-1”
Sometimes you want to use your own configured virtual instance vs the images available in AWS. We’ll break down the highlevel steps in getting your VM from your datacenter to the Amazon Cloud.Most the images that get transferred uses S3 as its temp location for transferring. Once the above is completed, launch your instance and go to town.