A company is migrating its on-premises servers to AWS using AWS Application Migration Service (MGN) over a Site-to-Site VPN. The target environment includes a staging area VPC and a target VPC. The migrated servers in the target VPC must resolve internal DNS names hosted in a Route 53 private hosted zone within a shared services VPC. Which two configurations are required to ensure successful data replication and proper name resolution?
- Allow outbound TCP port 1500 traffic from the on-premises source servers to the replication servers in the staging area VPC.Answer
- Associate the private hosted zone in the shared services VPC with the target VPC after the migration.Answer
- CAllow inbound TCP port 1500 traffic from the staging area VPC to the on-premises source servers.
- DRely on Transit Gateway routing to transitively resolve DNS queries in the target VPC without associating the private hosted zone.
- EDeploy a single NAT Gateway in the staging area VPC to route all outbound replication management traffic to the internet.
Answer
Allow outbound TCP port 1500 traffic from the on-premises source servers to the replication servers in the staging area VPC, and associate the private hosted zone in the shared services VPC with the target VPC after the migration.
Data replication with AWS Application Migration Service requires the on-premises source servers to establish outbound connections to the replication servers in AWS on TCP port 1500. Additionally, Route 53 Private Hosted Zones require explicit association with any VPC that needs to resolve records within that zone.
Step-by-Step Solution
Key Concept
AWS MGN network port requirements and Route 53 Private Hosted Zone associations.