2.2 Deploying PlateSpin Migrate Server in AWS

You can use the AWS Quick Start to quickly and easily deploy PlateSpin Migrate server on the AWS Cloud, or install Migrate server on a virtual host that you have set up for that purpose.

2.2.1 About PlateSpin Migrate Support for AWS Quick Start

PlateSpin Migrate supports AWS Quick Start to help you quickly and easily deploy PlateSpin Migrate server on the AWS Cloud. For more information about the Quick Start, see Micro Focus PlateSpin Migrate on AWS.

NOTE:The AWS Quick Start for this release will be available shortly after General Availability of this release and is available until after General Availability of the next release when PlateSpin Migrate releases the updated version of the Quick Start.

2.2.2 Deploying a Migrate Server Image in AWS

PlateSpin Migrate supports the AWS Quick Start to help you quickly and easily deploy PlateSpin Migrate server on the AWS Cloud. For more information about the Quick Start, see Micro Focus PlateSpin Migrate on AWS.

NOTE:

  • The AWS Quick Start for this release will be available shortly after General Availability of this release and is available until after General Availability of the next release when PlateSpin Migrate releases the updated version of the Quick Start.

  • For PlateSpin Migrate servers deployed through the AWS Quick Start, Migrate installs Microsoft SQL Server 2017 Express Edition for the PlateSpin database and generates a password for the SQL system administrator (sa) user. For improved security, we recommend that you modify the password for this user after the deployment is complete. For information, see Section 1.7, Modifying the Password for the SQL Server Express System Administrator User.

You can alternatively install Migrate server on your own virtual host in AWS. See Section 2.2.3, Checklist for Manually Deploying a Migrate Server in the AWS Cloud.

2.2.3 Checklist for Manually Deploying a Migrate Server in the AWS Cloud

Use the checklist in Table 2-5 to manually deploy a PlateSpin Migrate server in the cloud without a site-to-site VPN between your premises and the cloud environment.

Table 2-5 Checklist for Manual Migrate Server Deployment in the AWS Cloud

Task

Remark

  1. Ensure that your cloud account is configured and available.

See Table 2-1, AWS Account Requirements in Cloud Account.

  1. In your cloud account, create a network security group in the location where you will create the virtual host, then configure ports needed for the Migrate server.

See Section 2.1.3, Required Network Security Group Settings for PlateSpin Migrate Server.

  1. Create a Windows VM in your cloud account to use as the PlateSpin Migrate server host.

The target VM must meet the requirements in Section 1.1.1, System Requirements for PlateSpin Server.

  1. Install prerequisite software on the server host.

See Section 1.2, Installing Prerequisite Software.

  1. Install PlateSpin Migrate server on the server host with a public IP address.

See Section 1.3, Installing PlateSpin Migrate Software Components.

NOTE:PlateSpin requires a public IP address only if a site-to-site VPN is not available.

  1. Perform post-installation tasks on the Migrate server host.

  1. Set a secure custom password for the SQL system administrator user (sa).

    See Modifying the Password for the SQL Server Express System Administrator User.

  2. Disable TLS 1.0 and 1.1 protocols for the Windows operating system on the PlateSpin Migrate server host.

    See Section 1.8, Configuring TLS Protocols for Migrate Hosts.

  1. Configure PlateSpin advanced settings for the cloud-based Migrate server, depending on your intended use.

See Table 2-9, PlateSpin Configuration Settings for PlateSpin Migrate Server in the Cloud.

  1. Configure the AWS settings for the Migrate server in AWS.

See Configuring Advanced PlateSpin Settings for AWS.

  1. Configure the Windows instance for the Migrate virtual host to use Amazon Time Sync Service.

Amazon Time Sync Service uses NTP to synchronize the time for the cloud instance to the Amazon Region where it is deployed. Refer to Configuring Network Time Protocol in the Amazon Elastic Compute Cloud: User Guide for Windows Instances.