A healthcare diagnostics company is planning to migrate its hybrid application portfolio to AWS. The on-premises environment consists of 100 VMware vSphere VMs running supported Linux and Windows operating systems, and 15 legacy physical bare-metal servers running IBM AIX that host core databases. A strict corporate compliance policy prohibits installing any third-party agent software on the bare-metal database servers. The migration team needs to map network dependencies (such as active TCP connections and process-level interactions) for the entire application portfolio and track the migration progress in a centralized dashboard. Which strategy should the solutions architect recommend to collect the necessary discovery data while complying with all constraints?
- ADeploy the AWS Agentless Collector as an OVA on VMware vCenter to discover both the VMs and the physical AIX servers, then configure network dependency mapping from the vCenter logs.
- BInstall the AWS Application Discovery Agent on both the VMware VMs and the physical AIX servers, and configure them to route traffic through an on-premises HTTPS proxy with SSL decryption to meet the security requirements.
- Deploy the AWS Application Discovery Agent on the VMware vSphere VMs to collect configuration, performance, and network connection data. For the bare-metal AIX servers, use the AWS Migration Hub Import template to manually upload server specification and dependency data, and track the migration of all servers in AWS Migration Hub.Cevap
- DDeploy the AWS Agentless Collector on VMware vCenter for VM discovery. For the bare-metal AIX servers, install the AWS Application Discovery Agent by utilizing the compatibility mode, and configure AWS Migration Hub to automatically merge the data.