A gaming publisher is migrating its legacy multiplayer matchmaking and lobby servers from an on-premises data center to AWS using AWS Application Migration Service (MGN). The hybrid network architecture consists of an AWS Site-to-Site VPN terminating on an AWS Transit Gateway that is attached to a staging VPC. The source servers are in a highly secure zone with no direct route to the public internet and must perform data replication strictly over the private VPN connection.
After installing the AWS replication agent on the source servers, the replication status shows as stalled, and the agent logs indicate a connection timeout when attempting to reach the replication servers in the staging VPC.
Which two configuration steps must the Solutions Architect perform to resolve this connectivity issue? (Select TWO.)
- Modify the AWS Application Migration Service staging area settings to use a private IP address for data routing, and configure the replication security group in the staging VPC to allow inbound traffic on TCP port 1500 from the on-premises subnet range.Cevap
- Configure the on-premises firewall to allow outbound traffic on TCP port 1500 to the staging VPC CIDR block, and verify that the Transit Gateway route tables have propagation or static routes configured for both the on-premises and staging VPC attachments.Cevap
- CDeploy a NAT Gateway in the staging VPC public subnet, update the staging subnet route tables to direct all 0.0.0.0/0 traffic to the NAT Gateway, and configure the on-premises firewall to accept incoming connections over TCP port 443.
- DCreate an Amazon Route 53 Private Hosted Zone for the Application Migration Service control plane interface VPC endpoint in the staging VPC, and associate the hosted zone with the on-premises DNS server to resolve replication target hostnames.
- EConfigure a Direct Connect Gateway directly attached to the staging VPC to handle transitive VPC-to-VPC traffic, and configure the source servers to route replication traffic over TCP port 8080.