A multinational retail e-commerce company is planning to migrate its core inventory management system and order processing services to AWS. The on-premises infrastructure consists of 350 VMware vSphere virtual machines (VMs) running supported versions of Red Hat Enterprise Linux (RHEL) and Windows Server, and 20 bare-metal physical servers running IBM AIX for legacy transaction ledger processing. Security compliance policies strictly prohibit direct outbound internet access from database and application subnets, requiring all outbound traffic to traverse a centralized forward proxy. The migration team needs to gather detailed configuration, performance metrics (CPU, RAM, disk I/O), network connection dependencies, and process-level information for planning. Additionally, they must track the migration status dynamically in AWS Migration Hub using both AWS and partner migration tools. Which two actions should a solutions architect recommend to collect the discovery data and configure tracking?
- Deploy the AWS Application Discovery Agent on the VMware VMs, configure the agents to use the centralized forward proxy for outbound communication, and associate the discovered servers with applications in AWS Migration Hub.Answer
- Use the Application Discovery Service import template to upload a CSV file with the configuration and performance details of the IBM AIX bare-metal servers, and integrate supported third-party migration tools with AWS Migration Hub to track the migration.Answer
- CDeploy the Application Discovery Agentless Collector on the VMware vSphere environment to discover both the VMware VMs and the IBM AIX bare-metal servers, bypassing the need for any local agent installation or CSV import.
- DDeploy the AWS Application Discovery Agent on all VMware VMs and IBM AIX bare-metal servers, and configure on-premises firewalls to allow direct outbound traffic over TCP port 1500 to the AWS Application Migration Service endpoint.
- EConfigure the Application Discovery Agentless Collector to collect network connection dependencies and process-level information for the VMware VMs, and establish an AWS Direct Connect gateway connection to route this metadata to AWS Migration Hub.