12.5 Prerequisites for C2C Migration from Azure to AWS

PlateSpin Migrate supports migration of workloads from Microsoft Azure Cloud to Amazon Web Services EC2 Cloud.

12.5.1 Deployment for C2C Migration from Azure to AWS

For migration of workloads from Microsoft Azure Cloud to Amazon Web Services EC2 Cloud, you can deploy a cloud-based PlateSpin Migrate server in Azure or in AWS.

Migrate Server in Azure

Deploy PlateSpin Migrate server from the Azure Marketplace in the source Azure environment. The Migrate server image in Azure Marketplace is preconfigured to support its host Azure IaaS environment: Azure global or the sovereign environments such as Azure China, Azure Germany, or Azure Government. When the Migrate Server and source workloads are in the same network security group, you can use Migrate discovery to add workload details to Migrate. Figure 12-2 shows the location of various components in your AWS, Azure, and data center migration environments and the communications between them.

NOTE:Figure 12-2 depicts source workloads and the Migrate server in the same network security group. If they are in different security groups, 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 Section 2.6.2, Requirements for Workload Registration and Section 19.7, Registering Workloads and Discovering Details with Migrate Agent.

Figure 12-2 Migrate Server in Azure for Automated Migration from Azure to AWS with No VPNs

Migrate Server in AWS

Deploy PlateSpin Migrate server in the target AWS environment. See Section 8.4, Deploying a Migrate Server Image in AWS .

You use Migrate Agent to register workloads with the cloud-based Migrate server using secure communications over the public Internet. Internet access and public IP addresses are required. Figure 12-3 show the location of various components in your AWS, Azure, and data center migration environments and the communications between them

NOTE:A reboot of the source Windows workload is required when you install, uninstall, or upgrade block-based transfer drivers. A reboot is not required for source Linux workloads.

Enable data transfer encryption to transfer data securely between the source workload in Azure and the PlateSpin Replication Environment in AWS over the public Internet.

Figure 12-3 Migrate Server in AWS for Automated Migration from Azure to AWS with No VPNs

12.5.2 Requirements for Migrating Workloads to AWS

To prepare your target AWS environment, review the following information in Section 8.2, Requirements for Migrating Workloads to Amazon Web Services:

Ensure that the source workload is supported by the target AWS configuration.

12.5.3 Requirements for Migrating Workloads from Azure to AWS

Deploy a PlateSpin Migrate server in the source Azure network environment or the target AWS network environment. Ensure that your non-VPN migration environment meets the Requirements for C2C Non-VPN Migrations.

Ensure that your migration environment meets these additional requirements:

  • In the PlateSpin Configuration settings on the Migrate server:

    • (Migrate Server in Azure) ServerIsHostedInCloud: Remove the value of azure from the ServerIsHostedInCloud parameter to enable the Add Target dialog to provide all target types for selection. When you set up the AWS target, select Amazon Cloud Region as the target type.

  • Azure automatically adds the Remote Desktop Protocol (RDP) port (TCP/3389) and Secure Shell (SSH) port (TCP/22) in the Azure Security Group for the source workload VMs. You must manually add other ports to the source workload’s Azure Security Group that are required by PlateSpin Migrate to provide migration services, such as Port 3725 for replication traffic and Port 443 for HTTPS traffic.

  • For information about workload login requirements for migration, see the Windows and Linux source workload login requirements in Table 19-2, Guidelines for Machine Type and Credentials for Source Workloads.