Which solution will meet these requirements?
Use AWS Application Migration Service (CloudEndure Migration) to migrate the Windows servers to AWS. Create a Replication Settings template. Install the AWS Replication Agent on the source servers.
Use AWS DataSync to migrate the Windows servers to AWS. Install the DataSync agent on the source servers. Configure a blueprint for the target servers. Begin the replication process.
Use AWS Server Migration Service (AWS SMS) to migrate the Windows servers to AWS. Install the SMS Connector on the source servers. Replicate the source servers to AWS. Convert the replicated volumes to AMIs to launch EC2 instances.
Use AWS Migration Hub to migrate the Windows servers to AWS. Create a project in Migration Hub. Track the progress of server migration by using the built- in dashboard.
Explanations:
AWS Application Migration Service (CloudEndure Migration) is designed specifically for lift-and-shift migrations, allowing for minimal downtime. It supports replication of applications and data in real time, ensuring both encryption in transit and at rest, thus meeting the security policy. It also enables a quick cutover by allowing for testing of the migrated application before final cutover.
AWS DataSync is primarily designed for transferring large amounts of data to and from AWS storage services, not specifically for server migration. It doesn’t provide real-time replication and might result in longer downtime during migration compared to lift-and-shift solutions.
AWS Server Migration Service (AWS SMS) is suitable for migrating servers but may not be as efficient for minimizing downtime as CloudEndure. The process involves multiple steps, including replicating volumes to AMIs and launching EC2 instances, which may extend the cutover window.
AWS Migration Hub provides a centralized way to track migrations but does not perform the actual migration. It is more of a project management tool rather than a migration tool, which does not align with the company’s requirement for a direct migration solution with minimal downtime.
As I see it, the answer is:
Use AWS Application Migration Service (CloudEndure Migration) to migrate the Windows servers to AWS. Create a Replication Settings template. Install the AWS Replication Agent on the source servers.