An energy utility company is migrating physical on-premises servers hosting critical control systems to AWS using AWS Application Migration Service (MGN). Due to regulatory compliance, all replication traffic must remain private and must not traverse the public internet. A AWS Direct Connect connection is established between the on-premises data center and an AWS Transit Gateway in a shared services account. The Transit Gateway routes traffic to a dedicated Migration VPC where the staging area subnet is located. The AWS MGN Replication Agent will be installed on each on-premises server. Which network and service configuration must be implemented to ensure that the replication traffic is kept entirely private and replication completes successfully?
- Configure the AWS MGN Replication Template to use private IP routing. Create Interface VPC Endpoints for the AWS MGN service inside the Staging VPC, and configure the on-premises DNS to resolve the MGN service endpoints to these private IPs. Allow inbound traffic on TCP port 1500 to the staging area subnets from the on-premises network, and allow outbound traffic on TCP port 443 from the source servers to the MGN Interface VPC Endpoints.Answer
- BConfigure the AWS MGN Replication Template to use private IP routing. Create Interface VPC Endpoints for the AWS MGN service inside the Staging VPC. To ensure maximum security, configure the Staging VPC security groups to allow inbound traffic on TCP port 443 from the on-premises network, but block all other inbound traffic including TCP port 1500 to prevent unauthorized block-level data access.
- CConfigure the AWS MGN Replication Template to use public IP routing. Establish a Public Virtual Interface (VIF) on the Direct Connect connection to route replication traffic to the public endpoints of AWS MGN, and configure a NAT Gateway in the Staging VPC to route return traffic from the replication servers back to the on-premises network.
- DConfigure the AWS MGN Replication Template to use private IP routing. Create Interface VPC Endpoints for the AWS MGN service in a shared services VPC associated with a Route 53 Private Hosted Zone for the service endpoints, but do not associate this Private Hosted Zone with the Staging VPC to avoid overlapping DNS resolution conflicts with the on-premises domain controllers.