Use private IP for data replication - Application Migration Service

Use private IP for data replication

Choose the Use private IP option if you want to route the replicated data from your source servers to the Staging Area Subnet through a private network with a VPN, AWS Direct Connect, VPC peering, or another type of existing private connection.

Choose Do not use private IP if you do not want to route the replicated data through a private network.

Important

Data replication will not work unless you have already set up the VPN, AWS Direct Connect, or VPC peering in the AWS Console.

Note

If you selected the Default subnet, it is highly unlikely that the Private IP is enabled for that Subnet. Ensure that Private IP (VPN, AWS Direct Connect, or VPC peering) is enabled for your chosen subnet if you wish to use this option.

Note

You can safely switch between a private connection and a public connection for individual server settings choosing the Use private IP or Do not use private IP option , even after data replication has begun. This switch will only cause a short pause in replication, and will not have any long-term effect on the replication.

Note

Choosing the Use Private IP option will not create a new private connection.

You should use this option if you want to:

  • Allocate a dedicated bandwidth for replication;

  • Use another level of encryption;

  • Add another layer of security by transferring the replicated data from one private IP address (source) to another private IP address (on AWS).