A company is planning to migrate its on-premises VMware vSphere virtual machines (VMs) to native Amazon EC2 instances using AWS Application Migration Service (MGN). The migration network path must utilize an existing AWS Direct Connect connection with a backup Site-to-Site VPN. The company's compliance policy mandates that replication traffic must be encrypted and remain entirely within a private network path without traversing the public internet. The migration requires a Recovery Point Objective (RPO) of less than minutes and a replication cutover window with less than minutes of downtime. During the initial agent deployment, the replication status remains in the 'Establishing connection' state, and data replication cannot start. Security groups and network ACLs are configured to allow HTTPS traffic (TCP port 443) to AWS endpoints. Which network configuration modification will resolve the replication connection issue while adhering to all compliance constraints?
- Configure the on-premises firewall and the staging area security groups to allow inbound and outbound traffic over TCP port 1500, and enable the use of private IP addresses for data replication in the AWS MGN replication template.Cevap
- BConfigure a Direct Connect public virtual interface to establish connectivity to the AWS MGN public endpoints, and configure the staging area security groups to allow inbound traffic on TCP port 443.
- CAssociate the AWS MGN service endpoints with a Route 53 Private Hosted Zone in a central shared services account, and configure the replication template to use public IP addresses over the Direct Connect private virtual interface.
- DConfigure a Direct Connect Gateway directly to handle the transitive routing of replication traffic between the on-premises VMware environment and the staging VPC, and ensure that TCP port 8080 is open in the on-premises firewall.