Question

A company is planning to migrate roughly 800 on-premises servers to AWS over the next 18 months. The infrastructure team knows the servers exist but has poor documentation about which applications run on them, how the servers communicate with each other, and their current CPU, memory, and network utilization patterns. Leadership wants a data-driven migration plan that groups servers into application move groups and rightsizes EC2 targets, but corporate security policy forbids installing any third-party software agents on the production VMware fleet. Which approach BEST meets these discovery and planning requirements?

Accepted Answer

Deploy the AWS Application Discovery Service Agentless Collector as a virtual appliance in vCenter to continuously collect utilization and network dependency data, then use Migration Hub to group servers into application move groups.

Answer

Install the AWS Application Discovery Agent on each of the 800 servers to gather detailed process-level and network connection data, and view results in Migration Hub.

Answer

Use AWS Migration Evaluator with a manual spreadsheet inventory provided by the infrastructure team, then estimate EC2 sizes based on documented specifications.

Answer

Enable AWS Application Migration Service (MGN) replication on all servers immediately so that CloudWatch metrics from the launched test instances reveal dependencies and utilization.