Question

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

A university department is migrating its research analytics platform, which consists of 1212 physical servers, to AWS using AWS Application Migration Service (MGN). The migration must use a private network path over a 1 Gbps1\text{ Gbps} AWS Direct Connect connection with an AWS Transit Gateway. The AWS Replication Agent has been installed on the source servers, and the agent successfully establishes control plane communication with the MGN service endpoints. However, data replication is failing to initiate, and status logs indicate that the replication servers in the staging area VPC cannot receive replication data blocks from the source servers. Which action should the solutions architect take to resolve this issue and enable replication?

  1. A
    Configure a Direct Connect Gateway directly attached to the staging area VPC using a Private Virtual Interface (VIF) instead of Transit Gateway to route replication traffic.
  2. Allow inbound traffic on TCP port 1500 in the security groups of the staging area VPC and allow outbound traffic on TCP port 1500 from the on-premises firewall.Answer
  3. C
    Associate the Route 53 Private Hosted Zone used for the MGN API endpoints with the staging area VPC to resolve DNS queries for the replication servers.
  4. D
    Deploy a single NAT Gateway in the staging area VPC to route the replication traffic, and update the replication template to route all outbound replication traffic through it.

Answer

Allow inbound traffic on TCP port 1500 in the security groups of the staging area VPC and allow outbound traffic on TCP port 1500 from the on-premises firewall.
The correct answer correctly identifies that AWS MGN utilizes TCP port 1500 for the continuous replication of data blocks from the source server agent to the replication servers located in the staging area VPC. Opening this port in both directions resolves the data replication timeout while preserving the existing, functioning control plane channel over HTTPS.

Step-by-Step Solution

1
Analyze the connection status and identify which protocol/ports are failing.
The agent successfully connects to the MGN control plane (TCP port 443) but fails to replicate data blocks (TCP port 1500).
To isolate whether the issue is DNS, routing, or firewall/security group rules.
2
Check the requirements of the AWS Application Migration Service (MGN) for data replication traffic.
MGN requires TCP port 1500 to be open for data transfer between the replication agent on the source server and the replication servers in the staging area VPC.
To determine the required network port configuration for data replication.
3
Modify the relevant firewall and security group rules to permit traffic on TCP port 1500.
Outbound TCP port 1500 is allowed on the on-premises firewall, and inbound TCP port 1500 is allowed on the staging area VPC security groups.
To allow the Replication Agent to successfully stream data blocks to the replication servers.

Key Concept

AWS MGN uses TCP port 443 for control plane communication and TCP port 1500 for data replication.
Estimated Time:2m 0s
Rate this question