Question

Difficulty: HardInfrastructure Migration with AWS Application Migration Service (MGN)

A logistics company is migrating 1818 legacy route optimization virtual machines from an on-premises VMware vSphere cluster to AWS using AWS Application Migration Service (MGN). The replication traffic must flow privately over an existing AWS Direct Connect connection with a private virtual interface (VIF) terminated at an AWS Transit Gateway. The Transit Gateway connects to a Staging Area VPC. A dedicated Shared Services VPC hosts central Route 53 Private Hosted Zones (PHZs) and Route 53 Resolver endpoints. The company's security policy prohibits any public internet access for the source VMs and the staging environment.

During the initial replication phase, the migration team observes that the MGN Replication Agents installed on the source VMs fail to establish data replication with the Replication Servers in the Staging Area VPC, although control plane connectivity to the MGN endpoints is established.

Which combination of configuration steps will resolve the replication failure and ensure the migration succeeds over the private path in accordance with the security policy?

  1. A
    Bypass the Transit Gateway by establishing a new public virtual interface on the Direct Connect connection to route replication traffic directly to the MGN public endpoints, configure the Staging Area VPC route tables to point to the Direct Connect Gateway as the next hop, and allow TCP port 15001500 on the Staging Area VPC network access control lists.
  2. B
    Configure the Staging Area VPC security groups to allow inbound traffic on TCP port 15001500, but restrict the Route 53 Private Hosted Zone associations exclusively to the Shared Services VPC to maintain centralized DNS management, relying on conditional forwarders on the on-premises DNS servers pointing to Route 53 Resolver inbound endpoints.
  3. Configure the Staging Area VPC security groups to allow inbound traffic on TCP port 15001500 from the on-premises subnet range, associate the Route 53 Private Hosted Zones for the MGN and EC2 interface endpoints with the Staging Area VPC, and verify that the Transit Gateway route tables contain appropriate routes for transitive traffic between the on-premises network and the Staging Area VPC.Answer
  4. D
    Configure the Staging Area VPC security groups to allow inbound traffic on TCP port 443443 for data replication, deploy a single NAT Gateway in a single Availability Zone of the Staging Area VPC to route outbound data replication traffic, and associate the Route 53 Private Hosted Zone with the target workload VPC.

Answer

Configure the Staging Area VPC security groups to allow inbound traffic on TCP port 15001500 from the on-premises subnet range, associate the Route 53 Private Hosted Zones for the MGN and EC2 interface endpoints with the Staging Area VPC, and verify that the Transit Gateway route tables contain appropriate routes for transitive traffic between the on-premises network and the Staging Area VPC.
To establish private replication using AWS Application Migration Service (MGN) over Direct Connect and Transit Gateway, the replication agents installed on the source servers must transfer data blocks to the MGN Replication Servers over TCP port 15001500. Therefore, the Staging Area VPC security group must allow inbound TCP port 15001500 from the on-premises subnet. Additionally, because the architecture uses PrivateLink (interface VPC endpoints) for private MGN and EC2 API access, the associated Route 53 Private Hosted Zones must be associated with the Staging Area VPC so that replication servers can resolve service endpoints to private IPs. Finally, Transit Gateway routing must be correctly configured to enable communication between the on-premises network and the Staging Area VPC.

Step-by-Step Solution

1
Configure the security groups in the Staging Area VPC.
Inbound TCP port 15001500 is allowed from the on-premises subnet range containing the source VMs.
The MGN replication agent transmits replicated data blocks to the staging replication servers over TCP port 15001500. Without this open, data replication stalls.
2
Associate the Route 53 Private Hosted Zones with the Staging Area VPC.
The replication servers and resources in the Staging Area VPC can resolve AWS service endpoints privately via AWS PrivateLink.
To maintain a private-only network path, MGN and EC2 API calls must go through interface endpoints. The hosted zones must be associated with the Staging VPC to enable DNS resolution.
3
Verify and configure AWS Transit Gateway route tables.
Bidirectional routing is established between the on-premises network (via Direct Connect) and the Staging Area VPC.
Replication data must traverse the private network path. The Transit Gateway requires correct route propagation and association to allow the VMs to reach the Staging VPC.

Key Concept

Establishing private, secure data replication using AWS Application Migration Service over a hybrid network path.
Rate this question