A solutions architect is migrating an on-premises physical server to AWS using AWS Application Migration Service (MGN). The replication traffic is configured to travel over a Site-to-Site VPN connection directly into the staging area subnet of the target VPC. The AWS Replication Agent has been successfully installed on the source server, but the replication status shows as disconnected, and data transfer cannot begin. Which of the following configuration changes will resolve the replication connectivity issue?
- Configure the on-premises firewall and the replication staging area security groups to allow traffic over TCP port 1500 between the source server and the replication servers.Answer
- BConfigure an AWS Transit Gateway to route the replication traffic transitively through a central transit VPC to bypass the Direct Connect Gateway routing limitations.
- CAssociate a Route 53 Private Hosted Zone with the target VPC to enable DNS resolution of the MGN service endpoints from the source server.
- DDeploy redundant NAT Gateways across multiple Availability Zones in the staging VPC to handle outbound replication data streams.
Answer
Configure the on-premises firewall and the replication staging area security groups to allow traffic over TCP port 1500 between the source server and the replication servers.
The correct action is to open TCP port 1500. During the migration process, the AWS Replication Agent on the source server communicates with the replication servers in the staging area over TCP port 1500 to perform data replication. Opening this port in both the on-premises firewall (outbound) and the staging area security groups (inbound) allows the replication stream to flow.
Step-by-Step Solution
Key Concept
AWS MGN Data Replication Port Requirements