micro focus platespin migrate on the aws cloud...templates to deploy key technologies on aws,...
Post on 11-Aug-2020
3 Views
Preview:
TRANSCRIPT
Page 1 of 20
Micro Focus PlateSpin Migrate on the AWS Cloud
Quick Start Reference Deployment
March 2019
Last update: April 2020 (revisions)
Mehendran Thangavel, Micro Focus
Scott Kellish, Vinod Shukla, AWS Quick Start team
Visit our GitHub repository for source files and to post feedback,
report bugs, or submit feature ideas for this Quick Start.
Contents
Overview ....................................................................................................................................2
PlateSpin Migrate on AWS ........................................................................................................ 2
Cost and licenses ....................................................................................................................... 4
Architecture ...............................................................................................................................4
Planning the deployment ......................................................................................................... 6
Specialized knowledge............................................................................................................... 6
AWS account ............................................................................................................................. 6
Technical requirements ............................................................................................................. 6
Deployment options .................................................................................................................. 7
Deployment steps ...................................................................................................................... 7
Step 1. Sign in to your AWS account ......................................................................................... 7
Step 2. Obtain a license .............................................................................................................8
Step 3. Launch the Quick Start .................................................................................................8
Option 1: Parameters for deploying PlateSpin Migrate server into a new VPC .............. 10
Option 2: Parameters for deploying PlateSpin Migrate server into an existing VPC ..... 12
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 2 of 20
Step 4. Test the deployment .................................................................................................... 16
Best practices for using PlateSpin Migrate on AWS ............................................................... 16
Security .................................................................................................................................... 17
FAQ .......................................................................................................................................... 17
Send us feedback ..................................................................................................................... 18
Additional resources ............................................................................................................... 18
Document revisions ................................................................................................................. 19
Overview
This Quick Start was created by Micro Focus, Inc. in collaboration with Amazon Web
Services (AWS).
Quick Starts are automated reference deployments that use AWS CloudFormation
templates to deploy key technologies on AWS, following AWS best practices.
This Quick Start reference deployment guide provides step-by-step instructions for quickly
and easily deploying Micro Focus PlateSpin Migrate on the AWS Cloud. It is intended for
users who want to use the AWS CloudFormation templates to automate the deployment
and configuration of PlateSpin Migrate on the AWS Cloud.
PlateSpin Migrate on AWS
With PlateSpin Migrate, you can migrate heterogeneous workloads across x86-based
physical, virtual machine, and cloud infrastructure such as AWS in your data center. You
can either deploy PlateSpin Migrate on premises in your data center with the source
workloads or on the AWS Cloud. This Quick Start helps you to quickly deploy and configure
PlateSpin Migrate on the AWS Cloud.
PlateSpin Migrate decouples the workload infrastructure from its software (operating
system, applications, and data) to allow any-to-any migrations, such as the following:
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 3 of 20
Physical to Virtual (P2V)
Virtual to Virtual (V2V)
Virtual to Physical (V2P)
Physical to Physical (P2P)
Physical to Cloud (P2C)
Virtual to Cloud (V2C)
Cloud to Physical (C2P)
Cloud to Virtual (C2V)
Figure 1: Workload migration operations
With PlateSpin Migrate, you can:
Easily discover workloads and hosts in your environment.
Efficiently configure, run, and test workloads, before the actual cutover.
Continuously monitor the status of workload migration.
Increase migration speed and success ratios, which help reduce the costs of your
migration projects.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 4 of 20
Cost and licenses
You are responsible for the cost of the AWS services used while running this Quick Start
reference deployment. There is no additional cost for using the Quick Start.
The AWS CloudFormation template for this Quick Start includes configuration parameters
that you can customize. Some of these settings, such as instance type, will affect the cost of
deployment. For cost estimates, see the pricing pages for each AWS service you will be
using. Prices are subject to change.
Tip After you deploy the Quick Start, we recommend that you enable the AWS Cost
and Usage Report to track costs associated with the Quick Start. This report delivers
billing metrics to an S3 bucket in your account. It provides cost estimates based on
usage throughout each month, and finalizes the data at the end of the month. For
more information about the report, see the AWS documentation.
This deployment uses a Bring Your Own License (BYOL) model for the PlateSpin Migrate
server. For information about PlateSpin Migrate licensing, see “Working With Your
PlateSpin Migrate Server” > “Configuring PlateSpin Migrate Server” > “PlateSpin Migrate
Product Licensing” in the PlateSpin Migrate User Guide on the PlateSpin Migrate
documentation website.
To request a trial license, perform the following steps:
1. Go to the PlateSpin Migrate product page, and then choose Free trial.
2. When you are prompted, sign in using your Micro Focus Customer Center account. If
you do not have an account, choose Create an Account, and provide the requested
information.
3. To download and install PlateSpin Migrate, follow the instructions on the Evaluation
download page. The activation code that you need to license PlateSpin Migrate is
displayed in red on the page.
Architecture
Deploying this Quick Start for a new virtual private cloud (VPC) with default parameters
builds the following PlateSpin Migrate server environment in the AWS Cloud.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 5 of 20
Figure 2: Quick Start architecture for the PlateSpin Migrate server on AWS
The Quick Start sets up the following:
A highly available architecture that spans two Availability Zones.*
A VPC configured with public and private subnets according to AWS best practices, to
provide you with your own virtual network on AWS.*
In the public subnets, managed NAT gateways to allow outbound internet access for
resources in the private subnets.*
In one of the public subnets, an Amazon Elastic Compute Cloud (Amazon EC2) instance
with a fully configured PlateSpin Migrate server instance set up on Microsoft Windows
Server.
A security group for the PlateSpin Migrate server instance to restrict access to port 443
(HTTPS).
A security group for the target workloads in AWS to restrict access to only necessary
ports and protocols such as port 22 (SSH), port 443 (HTTPS), and port 3725 (TCP).
An AWS Identity and Access Management (IAM) role with a policy that has fine-
grained, minimal permissions needed for PlateSpin Migrate conversions to AWS.
* The template that deploys the Quick Start into an existing VPC skips the components
marked by asterisks and prompts you for your existing VPC configuration.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 6 of 20
Planning the deployment
Specialized knowledge
This Quick Start assumes familiarity with PlateSpin Migrate to perform migrations. For
information about performing migrations with PlateSpin Migrate, see the PlateSpin
Migrate User Guide on the PlateSpin Migrate documentation website.
This deployment guide also requires a moderate level of familiarity with AWS services. If
you’re new to AWS, visit the Getting Started Resource Center and the AWS Training and
Certification website for materials and programs that can help you develop the skills to
design, deploy, and operate your infrastructure and applications on the AWS Cloud.
AWS account
If you don’t already have an AWS account, create one at https://aws.amazon.com by
following the on-screen instructions. Part of the sign-up process involves receiving a phone
call and entering a PIN using the phone keypad.
Your AWS account is automatically signed up for all AWS services. You are charged only for
the services you use.
Technical requirements
Before you launch the Quick Start, your account must be configured as specified in the
following table. Otherwise, deployment might fail.
Resources If necessary, request service limit increases for the following resources. You might need
to do this if you already have an existing deployment that uses these resources, and you
think you might exceed the default limits with this deployment. For default limits, see
the AWS documentation.
AWS Trusted Advisor offers a service limits check that displays your usage and limits
for some aspects of some services.
Resource This deployment uses
VPCs 1
Elastic IP addresses
For NAT gateways - 2
For the PlateSpin Migrate
server - 1 (Optional)
IAM roles 1
Amazon EC2 instances 1
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 7 of 20
Regions For a current list of supported Regions, see AWS Regions and Endpoints in the AWS
documentation.
Key pair Make sure that at least one Amazon EC2 key pair exists in your AWS account in the
Region where you are planning to deploy the Quick Start. Make note of the key pair
name. You’ll be prompted for this information during deployment. To create a key pair,
follow the instructions in the AWS documentation.
If you’re deploying the Quick Start for testing or proof-of-concept purposes, we
recommend that you create a new key pair instead of specifying a key pair that’s already
being used by a production instance.
IAM permissions To deploy the Quick Start, you must log in to the AWS Management Console with IAM
permissions for the resources and actions the templates will deploy. The
AdministratorAccess managed policy within IAM provides sufficient permissions,
although your organization may choose to use a custom policy with more restrictions.
Deployment options
This Quick Start provides two deployment options:
Deploy the PlateSpin Migrate server into a new VPC (end-to-end
deployment). This option builds a new AWS environment consisting of the VPC,
subnets, NAT gateways, security groups, and other infrastructure components, and then
deploys the PlateSpin Migrate server into this new VPC.
Deploy the PlateSpin Migrate server into an existing VPC. This option
provisions the PlateSpin Migrate server in your existing AWS infrastructure.
The Quick Start provides separate templates for these options. You can configure CIDR
blocks, instance types, and PlateSpin Migrate server settings, as discussed later in the
guide.
Deployment steps
Step 1. Sign in to your AWS account
1. Sign in to your AWS account at https://aws.amazon.com with an IAM user role that has
the necessary permissions. For details, see Planning the deployment earlier in this
guide.
2. Make sure that your AWS account is configured correctly, as discussed in the Technical
requirements section.
3. Use the Region selector in the navigation bar to choose the AWS Region where you want
to deploy the PlateSpin Migrate server on AWS.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 8 of 20
4. Create a key pair in your preferred Region. This key pair is required to log in to your
PlateSpin Migrate server deployed in the AWS Cloud.
5. This Quick Start uses the PlateSpin Migrate AMI to deploy the PlateSpin Migrate server
in the selected Region.
Step 2. Obtain a license
This deployment uses a Bring Your Own License (BYOL) model for the PlateSpin Migrate
server. For information about PlateSpin Migrate licensing, see“Working With Your
PlateSpin Migrate Server” > “Configuring PlateSpin Migrate Server” > “PlateSpin Migrate
Product Licensing” in the PlateSpin Migrate User Guide on the PlateSpin Migrate
documentation website.
To request a trial license, perform the following steps:
1. Go to the PlateSpin Migrate product page, and then choose Free trial.
2. When you are prompted, sign in using your Micro Focus Customer Center account. If
you do not have an account, choose Create an Account, and provide the requested
information.
3. The Evaluation download page opens. This page provides all the information you need
to download and install PlateSpin Migrate. The activation code that you need to license
PlateSpin Migrate is displayed in red on this page.
Step 3. Launch the Quick Start
Note You are responsible for the cost of the AWS services used while running this
Quick Start reference deployment. There is no additional cost for using this Quick
Start. For full details, see the pricing pages for each AWS service you will be using in
this Quick Start. Prices are subject to change.
1. Choose one of the following options to launch the AWS CloudFormation template into
your AWS account. For help choosing an option, see deployment options earlier in this
guide.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 9 of 20
Deploy the PlateSpin Migrate server
into a new VPC on AWS
Deploy the PlateSpin Migrate server
into an existing VPC on AWS
Important When you’re deploying the PlateSpin Migrate server into an existing
VPC, you will be prompted for your VPC settings when you launch the Quick Start.
Ensure that your VPC has the following:
- A public subnet, if the PlateSpin Migrate server will be accessed directly from the
internet and the option Assign persistent public IP address is set as Yes.
- A private subnet that has a route to the internet via a NAT gateway or a hybrid
connection back to your on-premises network, if the option Assign persistent
public IP address is set as No.
Each deployment takes about 30 minutes to complete.
2. Check the Region that’s displayed in the upper-right corner of the navigation bar, and
change it if necessary. This is where the network infrastructure for the PlateSpin
Migrate server will be built. The template is launched in the US East (N.Virginia) Region
by default.
3. On the Select Template page, keep the default setting for the template URL, and then
choose Next.
4. On the Specify Details page, change the stack name if needed. Review the parameters
for the template. Provide values for the parameters that require input. For all other
parameters, review the default settings and customize them as necessary.
In the following tables, parameters are listed by category and described separately for
the two deployment options:
– Parameters for deploying the PlateSpin Migrate server into a new VPC
– Parameters for deploying the PlateSpin Migrate server into an existing VPC
When you finish reviewing and customizing the parameters, choose Next.
• new VPC
• workloadDeploy • workload onlyDeploy
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 10 of 20
OPTION 1: PARAMETERS FOR DEPLOYING THE PLATESPIN MIGRATE SERVER INTO A NEW
VPC
View template
License agreement:
Parameter label
(name) Default Description
License agreement
(LicenseAgreement)
— I have read and agree to the license terms for Micro Focus PlateSpin
Migrate. You must answer “I agree.”
VPC network configuration:
Parameter label
(name) Default Description
Availability Zones
(AvailabilityZones)
Requires
input
The list of Availability Zones to use for the subnets in the VPC.
Select any two. This Quick Start uses the first two zones from your
selected list.
VPC CIDR
(VPCCIDR)
10.0.0.0/16 The CIDR block for the VPC. This CIDR block must be in the form
x.x.x.x/16-28.
Private subnet 1 CIDR
(PrivateSubnet1CIDR)
10.0.0.0/19 The CIDR block for the private subnet 1 located in Availability Zone
1. The CIDR block parameter must be in the form x.x.x.x/16-28.
Private subnet 2
CIDR
(PrivateSubnet2CIDR)
10.0.32.0/19 The CIDR block for the private subnet 2 located in Availability Zone
2. CIDR block parameter must be in the form x.x.x.x/16-28.
Public subnet 1 CIDR
(PublicSubnet1CIDR)
10.0.128.0/20 The CIDR block for the public DMZ subnet 1 located in Availability
Zone 1. CIDR block parameter must be in the form x.x.x.x/16-28.
Public subnet 2 CIDR
(PublicSubnet2CIDR)
10.0.144.0/20 The CIDR block for the public DMZ subnet 2 located in Availability
Zone 2. CIDR block parameter must be in the form x.x.x.x/16-28.
PlateSpin Migrate server configuration:
Parameter label
(name) Default Description
Migrate server version
(MigrateServerVersion)
2020.2 The version of the PlateSpin Migrate server to be provisioned. Lists
the latest two supported versions of the PlateSpin Migrate server.
Choose the version of the PlateSpin Migrate server that you want to
deploy on the AWS Cloud.
Key pair name
(KeyPairName)
Requires
input
The name of an existing EC2 key pair, which allows you to securely
connect to your instance after it launches. This is the key pair you
created in your preferred Region; see the Technical requirements
section.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 11 of 20
Parameter label
(name) Default Description
Instance type
(MigrateServer
InstanceType)
t3.large The Amazon EC2 instance type for your PlateSpin Migrate server.
Assign persistent
public IP address
(AssignElasticIP)
Yes By default, a persistent public IP address (Elastic IP address) is
created and associated with the PlateSpin Migrate server. Choose No
to prevent accessing the PlateSpin Migrate server directly from the
internet.
Replication access
CIDR
(ReplicationAccess
CIDR)
Requires
input
The CIDR IP range that is permitted HTTPS (443/TCP) access to the
PlateSpin Migrate server for agent registration, and source
replication data traffic (3725/TCP) access to the replicating
workloads in the cloud. This CIDR IP range must contain all source
workloads to be migrated. The CIDR block parameter must be in the
form x.x.x.x/x.
Management access
CIDR
(ManagementAccessCIDR)
Requires
input
The CIDR IP range that is permitted RDP (3389/TCP) and HTTPS
(443/TCP) access to the PlateSpin Migrate server, and RDP
(3389/TCP) or SSH (22/TCP) access to the migrated workloads in the
production or test environment, for administrative purposes. The
CIDR block parameter must be in the form x.x.x.x/x.
Target workloads
interconnect CIDR
(TargetWorkloads
InterconnectCIDR)
Requires
input
The CIDR IP range that is permitted all-traffic (0-65535/UDP,TCP)
access to migrated workloads in the production or test environment.
The CIDR block parameter must be in the form x.x.x.x/x.
Email ID
(SNSTopicMailID)
None The email ID to which AWS CloudWatch alarm notifications about
the PlateSpin Migrate server will be sent.
Hostname
(MigrateServer
Hostname)
psmigrate The hostname (up to 15 characters) for your PlateSpin Migrate server.
This name can contain alphanumeric characters and hyphens. It
should start with a letter and should not end with a hyphen.
Admin username
(MigrateAdminUsername)
psadmin The user name for the PlateSpin Migrate server admin account. This
name can contain 5 to 25 alphanumeric characters.
Admin password
(MigrateAdminPassword)
Requires
input
The password for the PlateSpin Migrate server admin account. It can
contain 8 to 32 alphanumeric characters and symbols.
Re-enter the admin
password
(MigrateAdminConfirm
Password)
Requires
input
The password confirmation for the PlateSpin Migrate server admin
account.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 12 of 20
AWS Quick Start configuration:
Parameter label
(name) Default Description
Quick Start S3 bucket
name
(QSS3BucketName)
aws-quickstart The S3 bucket name for the Quick Start assets. The Quick Start
bucket name can include numbers, lowercase letters, uppercase
letters, and hyphens (-). It cannot start or end with a hyphen (-).
Quick Start S3 bucket
Region
(QSS3BucketRegion)
us-east-1 The AWS Region where the Quick Start S3 bucket
(QSS3BucketName) is hosted. When using your own bucket, you
must specify the bucket Region.
Quick Start S3 key
prefix
(QSS3KeyPrefix)
quickstart-
microfocus-
platespin/
The S3 key name prefix used to simulate a folder for your copy of
Quick Start assets, if you decide to customize or extend the Quick
Start for your own use. Quick Start key prefix can include numbers,
lowercase letters, uppercase letters, hyphens (-), and forward slashes
(/).
OPTION 2: PARAMETERS FOR DEPLOYING THE PLATESPIN MIGRATE SERVER INTO AN
EXISTING VPC
View template
License agreement:
Parameter label
(name) Default Description
License agreement
(LicenseAgreement)
- I have read and agree to the license terms for Micro Focus
PlateSpin Migrate. You must answer “I agree.”
VPC network configuration:
Parameter label
(name) Default Description
VPC ID
(VPCID)
Requires input The ID of your existing VPC to launch the PlateSpin Migrate
server instance.
Subnet ID
(SubnetID)
Requires input The subnet ID for launching the PlateSpin Migrate server.
PlateSpin Migrate server configuration:
Parameter label
(name) Default Description
Migrate server version
(MigrateServerVersion)
2020.2 The version of the PlateSpin Migrate server to be provisioned.
Lists the latest two supported versions of the Migrate server.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 13 of 20
Parameter label
(name) Default Description
Choose the version of the PlateSpin Migrate server that you want
to deploy on the AWS Cloud.
Key pair name
(KeyPairName)
Requires input The name of an existing EC2 key pair, which allows you to
securely connect to your instance after it launches. This is the key
pair you created in your preferred Region; see the Technical
requirements section.
Instance type
(MigrateServer
InstanceType)
t3.large The Amazon EC2 instance type for your PlateSpin Migrate
server.
Assign persistent
public IP address
(AssignElasticIP)
Yes By default, a persistent public IP address (Elastic IP address) is
created and associated with the PlateSpin Migrate server. Choose
No to prevent accessing the PlateSpin Migrate server directly
from the Internet.
Important If you choose No, you must ensure that the
PlateSpin Migrate server is provisioned in a private subnet that
has a route to the internet via a NAT gateway or a hybrid
connection back to your on-premises network. Otherwise, the
provisioning of the PlateSpin Migrate server fails with a
“timeout” error. See the FAQ section.
Replication access
CIDR
(ReplicationAccessCIDR)
Requires input The CIDR IP range that is permitted HTTPS (443/TCP) access to
the PlateSpin Migrate server for agent registration, and source
replication data traffic (3725/TCP) access to the replicating
workloads in the cloud. This CIDR IP range must contain all
source workloads to be migrated. The CIDR block parameter
must be in the form x.x.x.x/x.
Management access
CIDR
(ManagementAccessCIDR)
Requires input The CIDR IP range that is permitted RDP (3389/TCP) and
HTTPS (443/TCP) access to the PlateSpin Migrate server, and
RDP (3389/TCP) or SSH (22/TCP) access to the migrated
workloads in the production or test environment, for
administrative purposes. The CIDR block parameter must be in
the form x.x.x.x/x.
Target workloads
interconnect CIDR
(TargetWorkloads
InterconnectCIDR)
Requires input The CIDR IP range that is permitted all-traffic (0-
65535/UDP,TCP) access to migrated workloads in the
production or test environment. The CIDR block parameter must
be in the form x.x.x.x/x.
Email ID
(SNSTopicMailID)
None The email ID to which AWS CloudWatch alarm notifications
about the PlateSpin Migrate server will be sent.
Hostname
(MigrateServerHostname)
psmigrate The hostname (up to 15 characters) for your PlateSpin Migrate
server. This name can contain alphanumeric characters and
hyphens. It should start with a letter and should not end with a
hyphen.
Admin username
(MigrateAdminUsername)
psadmin The user name for the PlateSpin Migrate server admin account.
This name can contain 5 to 25 alphanumeric characters.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 14 of 20
Parameter label
(name) Default Description
Admin password
(MigrateAdminPassword)
Requires input The password for the PlateSpin Migrate server admin account. It
can contain 8 to 32 alphanumeric characters and symbols.
Re-enter the
admin password
(MigrateAdmin
ConfirmPassword)
Requires input The password confirmation for the PlateSpin Migrate server
admin account.
AWS Quick Start configuration:
Parameter label (name) Default Description
Quick Start S3 bucket
name
(QSS3BucketName)
aws-quickstart
The S3 bucket name for the Quick Start assets. The Quick Start
bucket name can include numbers, lowercase letters, uppercase
letters, and hyphens (-). It cannot start or end with a hyphen (-).
Quick Start S3 bucket
Region
(QSS3BucketRegion)
us-east-1 The AWS Region where the Quick Start S3 bucket
(QSS3BucketName) is hosted. When using your own bucket, you
must specify the bucket Region.
Quick Start S3 key prefix
(QSS3KeyPrefix)
quickstart-
microfocus-
platespin/
The S3 key name prefix used to simulate a folder for your copy of
Quick Start assets, if you decide to customize or extend the Quick
Start for your own use. The Quick Start key prefix can include
numbers, lowercase letters, uppercase letters, hyphens (-), and
forward slashes (/).
5. On the Options page, you can specify tags (key-value pairs) for resources in your stack
and set advanced options. When you’re done, choose Next.
6. On the Review page, review and confirm the template settings. Under Capabilities,
select the two check boxes to acknowledge that the template will create IAM resources
and that it might require the capability to auto-expand macros.
7. Choose Create to deploy the stack.
8. Monitor the status of the stack. When the status is CREATE_COMPLETE, the
deployment of the PlateSpin Migrate server is complete.
9. Use the URLs displayed in the Outputs tab for the stack to view the resources that were
created.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 15 of 20
Figure 3: Sample PlateSpin Migrate server outputs after successful deployment
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 16 of 20
Step 4. Test the deployment
To connect to the PlateSpin Migrate server instance deployed in AWS:
1. In the Outputs tab of the master stack, choose the value of the public or private URL to
launch the PlateSpin Migrate Web Interface. If you chose to assign a persistent public IP
address to the PlateSpin Migrate server, then use the public URL.
2. Log in to the PlateSpin Migrate Web Interface using the Administrator user name and
password configured for the PlateSpin Migrate server.
3. (Optional) To permanently resolve the browser security exception, perform the
following steps to install the PlateSpin CA certificate:
a. Copy the PlateSpin CA certificate file (PlateSpinCA.cer) from the C:\cfn\ folder
on the PlateSpin Migrate server to a temporary location on the computer that you
are using to launch the Web Interface.
b. Double-click the certificate file and follow the prompts to install the certificate into
the Trusted Root Certification Authorities store on the computer.
c. (For Mozilla FireFox browser only) To import the certificate into the certificate store
of the browser, go to Tools > Options > Privacy & Security > Certificates >
View Certificates > Authorities and click Import to browse to and open the
PlateSpinCA.cer file, and then click OK.
d. Restart the browser window.
4. Add the PlateSpin Migrate server license.
5. Perform workload migrations. For more information about performing migrations, see
“Executing Migrations” in the PlateSpin Migrate User Guide on the PlateSpin Migrate
documentation website.
Best practices for using PlateSpin Migrate on AWS
The best practices that apply to using PlateSpin Migrate in your data center also apply to
using PlateSpin Migrate on AWS. You must adopt these best practices when you configure
migration jobs to AWS to help prevent the migration jobs from failing. For more
information, see “Preparing Your Migration Environment” > “Prerequisites for Migration to
Amazon Web Services” > “Best Practices for Configuring a Migration Job to Amazon Web
Services” in the PlateSpin Migrate User Guide on the PlateSpin Migrate documentation
website.
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 17 of 20
Security
To help you safeguard your data and increase security, PlateSpin Migrate recommends
some security best practices. For more information, see “Overview and Planning” >
“Planning Your Workload Migrations” > “Security and Privacy” in the PlateSpin Migrate
User Guide on the PlateSpin Migrate documentation website.
FAQ
Q. I encountered a CREATE_FAILED error when I launched the Quick Start.
A. If AWS CloudFormation fails to create the stack, we recommend that you relaunch the
template with Rollback on failure set to No. (This setting is under Advanced in the
AWS CloudFormation console, Options page.) With this setting, the stack’s state will be
retained and the instance will be left running, so you can troubleshoot the issue. (For
Windows, look at the log files in %ProgramFiles%\Amazon\EC2ConfigService and
C:\cfn\log.)
Important When you set Rollback on failure to No, you will continue to incur
AWS charges for this stack. Please make sure to delete the stack when you finish
troubleshooting.
For additional information, see Troubleshooting AWS CloudFormation on the AWS
website.
Q. I encountered a size limitation error when I deployed the AWS CloudFormation
templates.
A. We recommend that you launch the Quick Start templates from the links in this guide or
from another S3 bucket. If you deploy the templates from a local copy on your computer or
from a non-S3 location, you might encounter template size limitations when you create the
stack. For more information about AWS CloudFormation limits, see the AWS
documentation.
Q. When I use the Quick Start template to launch the PlateSpin Migrate server in an
existing VPC, the provisioning of the PlateSpin Migrate server in the AWS Cloud fails with a
“timeout” error after waiting a minimum of 30 minutes.
A. If you chose No for the Assign persistent public IP address option when deploying
a PlateSpin Migrate server in an existing VPC, this typically indicates that you launched the
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 18 of 20
PlateSpin Migrate server into a subnet that does not have a route to the internet, via a NAT
gateway or a hybrid connection back to your on-premises network. As part of its
initialization, the PlateSpin Migrate server requires access to Amazon S3.
Q. I encountered the following error: CREATE_FAILED AWS::EC2::NatGateway
NATGateway =0">Nat Gateway is not available in this Availability Zone. What should I do?
A. Use a different Availability Zone to re-create the stack.
Send us feedback
To post feedback, submit feature ideas, or report bugs, use the Issues section of the
GitHub repository for this Quick Start. If you’d like to submit code, please review the Quick
Start Contributor’s Guide.
Additional resources
AWS resources
Getting Started Resource Center
AWS General Reference
AWS Glossary
AWS services
AWS CloudFormation
Amazon EC2
IAM
Amazon VPC
PlateSpin Migrate documentation
https://www.microfocus.com/documentation/platespin/platespin-migrate/
Other Quick Start reference deployments
AWS Quick Start home page
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 19 of 20
Document revisions
Date Change In sections
April 2020 Included the Quick Start S3 bucket Region
parameter in the AWS Quick Start configuration
section
Option 1: Parameters for
deploying PlateSpin Migrate
server into a new VPC
Option 2: Parameters for
deploying PlateSpin Migrate
server into an existing VPC
December 2019 Included a new parameter to specify the version
of the Migrate server that you want to deploy on
the AWS Cloud.
PlateSpin Migrate server
configuration tables in:
Option 1: Parameters for
deploying PlateSpin Migrate
server into a new VPC
Option 2: Parameters for
deploying PlateSpin Migrate
server into an existing VPC
July 2019 Migrations to AWS China Regions is now
supported.
Technical requirements
Deployment steps
May 2019 Migrations to AWS GovCloud is now supported. Technical requirements
Deployment steps
Included steps on how to permanently resolve the
browser security exception when you launch the
PlateSpin Migrate Web Interface.
Test the deployment
Updated the figure displaying the Outputs to
match the new AWS Console. The instructions
reflect the latest version of the AWS
CloudFormation console.
Launch the Quick Start
March 2019 Initial publication —
Amazon Web Services – PlateSpin Migrate on the AWS Cloud April 2020
Page 20 of 20
© 2020, Amazon Web Services, Inc. or its affiliates, and Micro Focus. All rights reserved.
Notices
This document is provided for informational purposes only. It represents AWS’s current product offerings
and practices as of the date of issue of this document, which are subject to change without notice. Customers
are responsible for making their own independent assessment of the information in this document and any
use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether
express or implied. This document does not create any warranties, representations, contractual
commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities
and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of,
nor does it modify, any agreement between AWS and its customers.
The software included with this paper is licensed under the Apache License, Version 2.0 (the "License"). You
may not use this file except in compliance with the License. A copy of the License is located at
http://aws.amazon.com/apache2.0/ or in the "license" file accompanying this file. This code is distributed on
an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.
top related