Network setting preparations

Staging area subnet

Before setting up AWS Application Migration Service (AWS MGN), you should create a subnet which will be used by the service as a staging area for data replicated from your source servers to AWS. You must specify this subnet in the replication settings template. You can override this subnet for specific source servers in the replication settings. While you can use an existing subnet in your AWS account, the best practice is to create a new dedicated subnet for this purpose. Learn more about replication settings.

Network requirements

The replication servers launched by AWS Application Migration Service (AWS MGN) in your staging area subnet need to be able to send data over TCP port 443 to the AWS MGN API endpoint at https://mgn.{region}.amazonaws.com/. Replace “{region}” with the AWS Region code you are replicating to, for example “us-east-1” .

The source servers on which the AWS Replication Agent is installed need be able to send data over TCP port 1500 to the Replication Servers in the Staging Area Subnet. They also need to be able to send data to AWS MGN's API endpoint at https://mgn.{region}.amazonaws.com/. Replace “{region}” with the AWS Region code you are replicating to, for example “us-east-1” .

Operational subnets

Test and cutover instances are launched in a subnet you specify in the Amazon EC2 launch template associated with each source server. The Amazon EC2 launch template is created automatically when you add a source server to AWS Application Migration Service.

Learn more about launching test and cutover instances.

Learn more about how Amazon EC2 launch templates are used.