Which solution meets these requirements?
Install the AWS Server Migration Service (AWS SMS) connector onto each physical machine. Use the AWS Management Console to select the servers from the server catalog, and start the replication. Once the replication is complete, launch the Amazon EC2 instances created by the service.
Install the AWS DataSync agent onto each physical machine. Use the AWS Management Console to configure the destination to be an AMI, and start the replication. Once the replication is complete, launch the Amazon EC2 instances created by the service.
Install the CloudEndure Migration agent onto each physical machine. Create a migration blueprint, and start the replication. Once the replication is complete, launch the Amazon EC2 instances in cutover mode.
Install the AWS Application Discovery Service agent onto each physical machine. Use the AWS Migration Hub import option to start the replication. Once the replication is complete, launch the Amazon EC2 instances created by the service.
Explanations:
AWS Server Migration Service (SMS) does not require installation of a connector on each physical machine. It is typically used for migrating virtualized servers (VMware, Hyper-V) to EC2 instances, not physical servers.
AWS DataSync is designed for transferring data (such as file systems) to AWS, but it does not handle the migration of physical servers or the conversion of workloads into EC2 instances.
CloudEndure Migration is designed for physical-to-cloud migrations. It installs an agent on each physical machine, replicates data continuously, and allows for a seamless cutover to EC2 instances when migration is complete.
AWS Application Discovery Service is used for collecting server data to help plan migrations, not for migrating or replicating servers. It doesn’t handle the actual server migration to EC2 instances.