12.8 Prerequisites for C2C Migration from AWS to vCloud

PlateSpin Migrate supports migration of workloads from Amazon Web Services EC2 Cloud to VMware vCloud Director.

12.8.1 Deployment for C2C Migration from AWS to vCloud

For migration of workloads from Amazon Web Services EC2 Cloud to VMware vCloud Director, deploy a PlateSpin Migrate server on premise in your source network. VPN gateways are required between the data center and AWS and between the data center and vCloud. Figure 12-8 shows the location of various components in your AWS, vCloud, and data center migration environments and the communications between them.

Figure 12-8 Migrate Server on Premise for Migration from AWS to vCloud

You can alternatively deploy the PlateSpin Migrate server using the AWS Quick Start in the source AWS environment. No VPN is required. With the AWS server in the same network security group as the source workloads, you can use discovery to add workloads to AWS. Use data encryption to secure data for replications over the public Internet. Figure 12-9 shows the location of various components in your AWS, vCloud, and data center migration environments and the communications between them.

NOTE:Figure 12-9 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-9 Migrate Server in AWS for Migration from AWS to vCloud with No VPNs

12.8.2 Requirements for Migration to vCloud

To prepare your target vCloud environment, review the information in Section 10.2, Planning For Migrating Workloads to VMware vCloud Director.

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

12.8.3 Requirements for Migrating Workloads from AWS to vCloud

For source workloads in AWS:

  • AWS automatically adds the Remote Desktop Protocol (RDP) port (TCP/3389) and Secure Shell (SSH) port (TCP/22) in the AWS Security Group for the source workload VMs. You must manually add other ports to the source workload’s AWS 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 Windows workloads, use a user name and password.

  • For Linux workloads, use the root user or root equivalent user.

    In AWS, Amazon Linux AMIs by default enable the ec2user user name and PEM key credentials, and disable the root user name and password credentials. To use Migrate discovery to inventory workloads, you must enable root user access for the AWS source Linux workload. See Section 12.10, Enabling Root User Credentials for Source Linux Workloads in AWS.

To use an on-premise Migrate server for migration of workloads from AWS to vCloud:

  • Deploy a site-to-site VPN between your data center and your AWS environment.

  • Deploy a site-to-site VPN between your data center and your VMware vCloud Virtual Private Cloud.

  • Because you are using a VPN Gateway between the data center and AWS, you can use a private IP address for the Migrate server.

  • Migrate Agent is not required because a VPN is available, but it would also work. For network ports and firewall requirements for registration, see Section 2.6.2, Requirements for Workload Registration.

To use a cloud-based Migrate server for migration of workloads from AWS to vCloud without a VPN: