12.10 Prerequisites for C2C Migration from AWS to Oracle Cloud infrastructure

PlateSpin Migrate supports migration of workloads from Amazon Web Services EC2 Cloud to Oracle Cloud Infrastructure.

12.10.1 Deployment for C2C Migration from AWS to Oracle Cloud Infrastructure

For migration of workloads from Amazon Web Services EC2 Cloud to Oracle Cloud Infrastructure, deploy the PlateSpin Migrate server in the target Oracle Cloud environment. No VPN is required between the participating sites. Internet access and public IP addresses are required. Figure 12-1 shows the location of various components in your AWS, Oracle Cloud, and data center migration environments and the communications between them.

A public IP address is required for the source workload to register the workload with the cloud-based Migrate server using secure communications over the public Internet. For deployment information, see Figure 12-1, Cloud-Based Migrate Server for Automated Migration from AWS to Azure with No VPNs

Figure 12-12 Cloud-Based Migrate Server for Automated Migration from AWS to Oracle Cloud with No VPNs

12.10.2 Requirements for Migrating Workloads to Oracle Cloud

To prepare your target Oracle Cloud Infrastructure environment, review the following information in Requirements for Migrating Workloads to Oracle Cloud Infrastructure:

Ensure that the source workload is supported by the target Oracle Cloud configuration.

12.10.3 Requirements for Migrating Workloads from AWS to Oracle Cloud

Deploy a PlateSpin Migrate server in the target Oracle Cloud infrastructure environment. Ensure that your non-VPN migration environment meets the Requirements for C2C Non-VPN Migrations.

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 Enabling Root User Credentials for Source Linux Workloads in AWS.