Which method would fulfill these requirements?
Set up a 1 Gbps AWS Direct Connect connection. Then, provision a private virtual interface, and use AWS Server Migration Service (SMS) to migrate the VMs into Amazon EC2.
Use AWS Application Discovery Service to assess each application, and determine how to refactor and optimize each using AWS services or AWS Marketplace solutions.
Export the VMs locally, beginning with the most mission-critical servers first. Use AWS Transfer for SFTP to securely upload each VM to Amazon S3 after they are exported. Use VM Import/Export to import the VMs into Amazon EC2.
Migrate mission-critical VMs with AWS SMS. Export the other VMs locally and transfer them to Amazon S3 using AWS Snowball. Use VM Import/Export to import the VMs into Amazon EC2.
Explanations:
Setting up a 1 Gbps AWS Direct Connect connection would be beneficial, but the existing 10 Mbps internet bandwidth is a limiting factor. Additionally, AWS Server Migration Service (SMS) is better suited for ongoing replication rather than bulk migrations. This approach would not meet the migration requirements effectively given the current constraints.
AWS Application Discovery Service is used for assessing applications and planning migrations. However, this option does not address the immediate need for transferring VMs to AWS within 3 months, nor does it account for the constraints of existing bandwidth. It focuses on refactoring rather than migration.
While exporting VMs and uploading them using AWS Transfer for SFTP could work, the method does not account for the mission-critical VMs that require minimized downtime. This option does not prioritize the migration of critical servers first, potentially leading to delays in getting them operational on AWS.
This option allows for the migration of mission-critical VMs using AWS SMS, ensuring minimal downtime. For the other VMs, exporting them locally and transferring to Amazon S3 using AWS Snowball is efficient and overcomes the bandwidth limitations. VM Import/Export allows for a straightforward import of the VMs into EC2, meeting the 3-month deadline effectively.
I figure that the answer is:
Migrate mission-critical VMs with AWS SMS. Export the other VMs locally and transfer them to Amazon S3 using AWS Snowball. Use VM Import/Export to import the VMs into Amazon EC2.