8.1 Deployment for Migration to Amazon Web Services
You can deploy a PlateSpin Migrate server on premise in your data center with the source workloads or create a Migrate server in the AWS cloud with a public IP address.
For an on-premise Migrate server deployment, a site-to-site VPN connection is required between the data center and your account in the AWS cloud. Figure 8-1 shows the location of various components in your AWS migration environment and the communications between them. See Planning For Migrating Workloads to Amazon Web Services.
NOTE:Figure 8-1 depicts automated discovery and the network requirements for Windows and Linux workloads. You can alternatively use Migrate Agent on the source workload to register the workload and send its inventory details to PlateSpin Migrate server using HTTPS (TCP/443). See Requirements for Workload Registration.
Figure 8-1 On-Premise Migrate Server for Automated Migration to AWS
For a cloud-based Migrate server deployment without a VPN:
-
Create an AWS Windows Instance in the AWS Cloud and install a PlateSpin Migrate server in the AWS instance with a public IP address.
-
Configure migrations to AWS with a public IP address for the replication network.
-
Use Migrate Agent on the source workload to register the workload and send its inventory details to PlateSpin Migrate server using HTTPS (TCP/443).
-
In the PlateSpin Configuration settings on the Migrate server, change the parameter from True to False. See Configuring the Contact Direction for the Replication Port.
-
Ensure that workloads can reach the public IP address for Migrate server. Set the parameter to the Migrate server’s public IP address on the PlateSpinConfiguration page. See Configuring Alternate IP Addresses for PlateSpin Server.
Figure 8-2 shows the location of various components in your AWS migration environment without a VPN and the communications between them. See AWS Prerequisites for Using an AWS-Based Migrate Server.
Figure 8-2 Cloud-Based Migrate Server for Automated Migration to AWS
