A digital media broadcasting company is migrating its on-premises video rendering workload consisting of servers to AWS using AWS Application Migration Service (MGN). The hybrid environment is connected via a dedicated AWS Direct Connect connection to an AWS Transit Gateway, which routes traffic to a dedicated staging VPC and a target production VPC. The migration must use a private replication channel over the Direct Connect connection. The solutions architect configures AWS MGN VPC interface endpoints in the staging VPC and associates them with the appropriate Route 53 Private Hosted Zone. Although the AWS Replication Agent is successfully installed on all source servers, the replication status remains stuck in the 'Initiating' state, and the console reports a connection timeout to the replication servers. Which action should the solutions architect take to resolve this replication connection failure?
- Ensure that the security group of the replication servers in the staging VPC allows inbound traffic on TCP port 1500 from the on-premises subnet, and verify that the on-premises network allows outbound traffic on TCP port 1500 to the staging area subnets.Cevap
- BReconfigure the Transit Gateway by replacing it with a Direct Connect gateway connected directly to the staging and production VPCs, enabling transitive routing of replication traffic between the staging subnets and the on-premises network.
- CAssociate the Route 53 Private Hosted Zone created for the MGN interface endpoints with the Transit Gateway's VPC attachment and configure a Route 53 Resolver outbound endpoint to forward queries to the on-premises DNS servers.
- DModify the staging VPC route tables to direct all replication traffic to a single NAT Gateway deployed in a public subnet of the staging VPC, ensuring the agent can reach the public IP addresses of the replication servers.