AWS Prescriptive GuidanceMigrating workloads to the AWS

Cloud by using CloudEndure Migration

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

AWS Prescriptive Guidance: Migrating workloads to the AWS Cloud byusing CloudEndure MigrationCopyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved.

Amazon's trademarks and trade dress may not be used in connection with any product or service that is notAmazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages ordiscredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who mayor may not be affiliated with, connected to, or sponsored by Amazon.

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Table of ContentsIntroduction .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Architecture .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Preparing your environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Set up your CloudEndure account and users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Generate and use AWS Cloud credentials ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Configure your source and target network .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Network requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Communication over TCP port 443 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Proxy servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Migrating your workload .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Define replication settings for AWS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Install CloudEndure Agent on source machines .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Configure the target system Blueprint ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Testing the migration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Cutting over to AWS ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Best practices .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17FAQ ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Can I use my existing Windows licensing with CloudEndure Migration? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Can I use my existing Linux licenses with CloudEndure Migration? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19What is the required bandwidth for TCP port 1500 to replicate data? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Can I change the default disk type to SSD instead of Provisioned SSD in the Blueprint for the targetinstance? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20How can I route replication traffic when I have multiple leased lines in the source? Is thereconfiguration setting I can use in CloudEndure? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20What compression mechanism does CloudEndure use during replication? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20What does the CloudEndure machine conversion server do? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20What are the differences between conversion servers and replication servers? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Which AWS Regions does CloudEndure use for production and disaster recovery? .... . . . . . . . . . . . . . . . . . . . . . . . . . 21What is the effect of having a dedicated replication server? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Next steps .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Additional resources .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23AWS Prescriptive Guidance glossary .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Document history .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iii

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Migrating workloads to the AWSCloud by using CloudEndureMigration

Chandra Sekhar Yaratha and Harnath Valeti, Consultants, AWS Professional Services

November 2020 (last update (p. 31): January 2021)

This guide describes the process for migrating applications from a physical, virtual, or cloud-basedinfrastructure to the Amazon Web Services (AWS) Cloud by using CloudEndure Migration. It includes bestpractices and troubleshooting tips, which are also covered in the following video.

The following video covers CloudEndure Migration best practices and troubleshooting tips: BestPractices for migrating servers to AWS by using CloudEndure Migration

1

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

CloudEndure Migration is an agent-based tool that rehosts your applications on AWS. It supports self-service, highly automated, lift-and-shift migrations with minimal business disruption. You install theCloudEndure Agent on your source machines. The Agent replicates your applications and data in astaging area on AWS. After the initial replication, the CloudEndure Agent tracks and migrates changesfrom your source environment to the target staging area by using asynchronous, block-level datareplication, without causing downtime or affecting performance.

You can use CloudEndure’s self-service, web-based console to configure your target environment, tocheck for compatibility issues, and to validate that your applications are fully operational on AWS beforeyou cut over. After you rehost your workloads on AWS, you can restructure, rewrite, and re-architect yourapplications and take advantage of AWS services.

CloudEndure Migration supports both Microsoft Windows and Linux-based workloads (see supportedversions). For more information, see the CloudEndure Migration website.

This guide is for project managers, system administrators, and migration architects who are planning tomigrate their workloads to AWS. It describes the migration process, including preparing your source andtarget environments, configuring network settings, migrating your workloads, testing, and cutting over.If you’re planning a large-scale migration that involves rehosting thousands of servers, you can furtherautomate tasks by using CloudEndure Migration Factory (CEMF).

NoteAWS Application Migration Service (MGN) is the primary migration service recommendedfor lift-and-shift migrations to the AWS Cloud. Customers who currently use CloudEndureMigration or AWS Server Migration Service (AWS SMS) are encouraged to switch to MGN forfuture migrations.

2

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

ArchitectureCloudEndure Migration simplifies, expedites, and automates large-scale migrations to AWS. Continuousdata replication takes place in the background, without application disruption or performance impact,which ensures that data is synchronized in real time and minimizes cutover windows. When you initiatemigration cutover, CloudEndure runs a highly automated machine conversion and orchestration process,which reduces the potential for human error. After migration, even the most complex applications anddatabases run natively on AWS, without compatibility issues and with minimal IT skills necessary. Thefollowing diagram illustrates the migration process.

Benefits of using CloudEndure Migration include:

• Easy migration – You can run complex, large-scale migration projects rapidly, regardless of theapplication type, while significantly reducing risk.

• Increased uptime – You can maintain normal business operations throughout the replication process.CloudEndure Migration copies source machines continuously, without taking snapshots or writing anydata to disks. This means that there is minimal performance impact and no need to reboot machines.Continuous replication also makes it easy to conduct non-disruptive tests and shortens cutoverwindows.

• Reduced costs – CloudEndure Migration is a single tool for migrating any application or databasefrom any source infrastructure on supported operating systems to AWS. You can migrate legacyapplications, third-party applications, and line-of-business applications. There is no need to investin specialized cloud development, operating system or application-specific skills, or significant ITresources, which results in greatly reduced operational costs.

Migrating your workloads by using CloudEndure Migration involves four phases of activities:

A. Preparing your environment. Includes setting up your CloudEndure account, creating AWScredentials, and configuring your network.

B. Migrating your workload. Includes installing CloudEndure Agents and replicating your sourceenvironment in the AWS staging area.

C. Testing the migration. Includes verifying the target machine settings and validating that the targetmachines are operating correctly.

3

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

D. Cutting over to AWS. CloudEndure Migration automatically converts your machines to run natively onAWS.

These phases are illustrated in the following diagram and described in detail in the following sections.

4

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Set up your CloudEndure account and users

Preparing your environment

Before you use CloudEndure Migration, you have to make sure that your source and target environmentsare prepared and configured correctly. These preparations include setting a CloudEndure account,creating AWS credentials, defining network requirements, and opening the correct ports.

Steps:

• Set up your CloudEndure account and users (p. 5)

• Generate and use AWS Cloud credentials (p. 6)

• Configure your source and target network (p. 7)

Set up your CloudEndure account and usersBefore you start your migration, follow these steps:

1. Subscribe to CloudEndure Migration in AWS Marketplace, where it's available as a SaaS contractdirectly through your existing AWS account.

2. Create an account in CloudEndure. For instructions, see Registering to CloudEndure Migration in theCloudEndure documentation.

3. Add users. The account owner and account administrators can manage users and projects inthe CloudEndure User Console. For information about inviting and managing users, see UserManagement in the CloudEndure documentation.

4. Create and configure a CloudEndure project. Log in to the CloudEndure User Console and follow thesteps provided in Working with Projects in the CloudEndure documentation.

For project type, select Migration.

5

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Generate and use AWS Cloud credentials

NoteMake sure that you have sufficient migration licenses for your project.

Generate and use AWS Cloud credentialsBefore you install CloudEndure Agents, you must create the AWS Identity and Access Management (IAM)credentials required to configure the CloudEndure User Console, and collect the access key and secretaccess key for the CloudEndure users in your organization. Follow these steps:

1. Sign in to your AWS account.2. Create a policy for CloudEndure in your AWS account, using the code from https://

docs.cloudendure.com/Content/IAMPolicy.json. For more information about this step, see theCloudEndure documentation.

6

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Configure your source and target network

3. Create a new IAM user and generate AWS credentials, which consist of an access key ID and a secretaccess key. For more information, see the CloudEndure documentation and the IAM documentation.

4. In the CloudEndure User Console, choose Setup & Info, AWS Credentials.

5. Add the access key ID and secret access key you created in the previous step into the correspondingfields and save.

Configure your source and target networkIn the target environment on AWS, prepare a subnet to use as the CloudEndure staging area. Use aprivate subnet if you want to isolate your application. You can use an existing subnet or create a newone. This subnet is used to launch the CloudEndure replication servers, which receive replicated datafrom the source machines.

In general, there are three points of contact between CloudEndure components and the externalnetwork:

• The CloudEndure Agent needs to communicate with the CloudEndure Service Manager.

• The CloudEndure Agent needs to communicate with the CloudEndure replication servers.

• CloudEndure replication servers need to communicate with the CloudEndure Service Manager andAmazon Simple Storage Service (Amazon S3).

7

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Network requirements

Network requirements

Client Server Description

Agent Outbound: TCP1500

Replicationserver(s) (private/public network)

Inbound: TCP1500

Productioninstance statusand data (theactual datareplication stream)

Agent Outbound: TCP1500

Management(public network)

  • REST APIs usedduring Agentinstallation

• Agentmonitoring

• Statistics forAgents

Replicationserver(s)

Outbound: TCP443

Management(public network)

  • Statistics forreplicationservers

• Replicationserver logs

• Replicationserver API

To prepare your network for running CloudEndure's solutions, you need to set the following connectivitysettings:

• Communication over TCP port 443:

• Between the source machines and CloudEndure Service Manager

8

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Communication over TCP port 443

• Between the staging area and CloudEndure Service Manager

• Communication over TCP port 1500:

• Between the source machines and the staging area

NoteFor information about replication from a private subnet or server behind a NAT gateway orinstance, see the CloudEndure documentation.

Communication over TCP port 443Add the following IP addresses and URLs to your firewall:

• CloudEndure Service Manager IP address (required for using CloudEndure software)

• 52.72.172.158 (main service of console.cloudendure.com)

• 52.53.92.136

• Amazon S3 service URLs (required for downloading CloudEndure software)

• s3.amazonaws.com

• s3.us-west-1.amazonaws.com

• s3.eu-west-1.amazonaws.com

Proxy serversIf you want to use proxy servers in your environment, follow this guidance for CloudEndure to operateeffectively:

• Make sure to set the proxy in replication settings, either as an IP address or as a fully qualified domainname (FQDN).

• Configure the proxy allow list for the CloudEndure Agent:

• In Windows, the CloudEndure Agent runs as a system service, so make sure that the system accountis part of the proxy allow list.

• In Linux, the CloudEndure Agent creates a Linux user (named cloudendure) to run commands, somake sure that this user is part of the proxy allow list.

• Set the proxy:

• In Windows, open the Command Prompt window as an administrator, and run the command:

setx https_proxy https://<proxy-ip>:<proxy-port>/ /m

• In Linux, change to sudo user and run the commands:

$ export http_proxy=http://server-ip:port/$ export http_proxy=http://127.0.0.1:3128/$ export http_proxy=http://proxy-server.mycorp.com:3128/

(make sure to include the trailing slash "/")

Optionally, if you want to keep the environment variables for Windows, follow these steps:

1. In Windows Control Panel, choose System and Security, System, Advanced system settings.

2. In the Advanced tab of the System Properties dialog box, choose Environment Variables.

9

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Proxy servers

3. In the System variables section of the Environment Variables dialog box, choose New to add thehttps_proxy environment variable, or Edit if the variable already exists.

4. In the Variable value field of the https_proxy variable, enter https://PROXY_ADDR:PROXY_PORT/ and then choose OK.

5. If the CloudEndure Agent was already installed, restart the service.

10

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Define replication settings for AWS

Migrating your workload

To migrate your workload to AWS, you use CloudEndure's web-based console to configure your sourceand target environments and to set up your replication servers. In this phase, you also install theCloudEndure Agent on your source machines, and specify a Blueprint for creating and configuringyour target machines. With these components and configurations in place, replication from the sourceenvironment to the lightweight staging area can begin.

Steps:

• Define replication settings for AWS (p. 11)

• Install CloudEndure Agent on source machines (p. 12)

• Configure the target system Blueprint (p. 13)

Define replication settings for AWSTo replicate data into or within the target environment, CloudEndure uses replication server(s) to providea lightweight replication staging area on AWS. These servers are automatically launched into the subnetyou created previously in the Configure your source and target network (p. 7) section.

The CloudEndure User Console address (console.cloudendure.com) is used for all cloud and on-premisesplatforms, except for specific cases.

In the CloudEndure User Console, you use the Replication Settings tab to define your source andtarget environments, and to configure the default replication servers in the staging area of thetarget infrastructure. For step-by-step instructions, see Defining Replication Settings for AWS in theCloudEndure documentation.

11

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Install CloudEndure Agent on source machines

Install CloudEndure Agent on source machinesAfter you’ve prepared your environment and configured your replication settings, you can installCloudEndure Agent on the machines in your source environment. The Agent replicates your applicationsand data in the staging area on AWS. Follow these steps:

1. In the CloudEndure User Console, choose Machines, Machine Actions, Add Machines.2. Locate the Installation Token that was provided for you when your CloudEndure account was

activated. (To locate your tokens, choose Help, How to Add Machines in the CloudEndure UserConsole.)

3. Download the Agent installer file to each source machine, and then use the command provided inthe How to Add Machines pane to run the installer on each source machine.

For more information, see Installing the CloudEndure Agents in the CloudEndure documentation.

When the Agent is installed, the source machine appears in the CloudEndure User Console, in theMachines tab, and the machine undergoes initial data replication (Initial Sync).

12

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Configure the target system Blueprint

Use the Machines dashboard to monitor the Initial Sync process, which includes these steps:

1. Creating firewall rules.2. Creating the replication server.3. Booting the replication server.4. Resolving the CloudEndure Service Manager address in the replication server.5. Authenticating the replication server with the CloudEndure Service Manager.6. Downloading the CloudEndure replication software to the replication server.7. Creating staging disks.8. Attaching the staging disks to the replication server.9. Pairing the CloudEndure Agent with the replication server.10. Establishing communication between the CloudEndure Agent and the replication server.

When the Initial Sync is complete, the Machines dashboard shows the final status as ContinuousData Replication. This indicates that all changes in the source server are being synchronized with theCloudEndure replication server.

For more information, see Monitoring Your Solution in the CloudEndure documentation.

Configure the target system BlueprintA Blueprint provides a set of instructions for creating and launching a target machine for a specifiedsource machine. To configure a source machine's Blueprint, choose the machine name from the Machinespane to access the Machine Details pane, and choose the Blueprint tab from the menu on the right.

Enter the following values in the Blueprint tab and then choose Save Blueprint.

Key Value

Machine Type t3.medium

Launch Type On Demand

Subnet Target subnet

Security Groups Target security group

Private IP Create New

Public IP (ephemeral) No

Disks SSD

For more information about these settings, see Configuring the Target Machine Blueprint in theCloudEndure documentation.

13

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Testing the migrationBefore you migrate your source machines into the target infrastructure, you should test yourCloudEndure Migration configuration. The Test Mode workflow launches and runs a target machinein the target infrastructure for the source machine you selected for testing. By testing your migrationconfiguration, you can verify that your source machines are working properly in the target environment.The CloudEndure User Console displays the test results. You can run Test Mode after the Initial Syncstage has been completed.

To test your migration, follow these steps:

1. Confirm that the source machine you want to test is in Continuous Data Replication (CDR) mode orthat its status is Ready for testing.

2. Configure the target machine with Blueprint. Verify that the subnet of the target environment isisolated. This isolation is designed to prevent conflicts with the source environment.

3. Test the target machines:

1. On the Machines page, check the box to the left of each source machine you want to test.2. Choose Launch x Target Machine, and then choose Test Mode.

3. When you receive the confirmation prompt, choose Continue to launch the target machines. Youcan monitor the launch process on the Job Progress tab.

4. Verify that the test completed successfully.5. Test the target machines by choosing each machine's name, navigating to the Target tab, copying

the public IP, and navigating to that IP.6. Verify service configuration and other settings.7. Verify that your network works as expected.8. Validate that you can connect to your target machines by using Secure Shell (SSH) for Linux or

Remote Desktop Protocol (RDP) for Windows, and perform acceptance tests for your application.

For more information about the testing process, see Testing the Migration Solution in the CloudEnduredocumentation.

14

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Cutting over to AWS

When you’ve completed your test and you’re ready to cut over to the target environment on AWS, followthese steps:

1. Confirm that the Data Replication Progress for the source machine is Continuous Data Replicationmode, and that the Live Migration Lifecycle column displays the status Tested.

2. Verify the Blueprint configuration.

3. Schedule and perform the cutover:

1. On the Machines page, check the box to the left of each source machine you want to migrate.

2. Choose Launch x Target Machine, and then choose Cutover Mode.

3. When you receive the confirmation prompt, choose Continue to launch the target machines. Youcan monitor the launch process on the Job Progress tab.

4. Verify that the cutover completed successfully.

15

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

5. Verify service configuration and other settings.6. Verify that your network works as expected.7. Validate that you can connect to your target machines by using SSH for Linux or RDP for

Windows, and perform acceptance tests for your application.8. Shut down your source machines.

4. After cutover is validated, uninstall the CloudEndure Agent by removing machines from theCloudEndure User Console.

1. On the Machines page, check the box to the left of each source machine you want to remove.2. From the Machine Actions menu, choose Remove x Machines from This Console. It takes up to

60 minutes for CloudEndure Migration to clean up the replication instances and volumes in thestaging area.

3. When all Agents have been uninstalled, delete the virtual private cloud (VPC) for the staging area.This deletes all the AWS resources you created for replication.

For more information about the cutover process, see Performing a Migration Cutover in the CloudEnduredocumentation.

16

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Best practices

The following video covers best practices and troubleshooting tips for using CloudEndure Migration. Best Practices for migrating servers to AWS by using CloudEndure Migration

To ensure project success:

• Train a field technical team, and assign a CloudEndure subject matter expert (SME).

• Share project timelines with CloudEndure.

• Monitor data replication progress and report any issues in advance.

• Perform a test for every machine in advance, and report issues to CloudEndure.

• Coordinate cutover windows with CloudEndure in advance.

Follow these best practices to implement a smooth and efficient migration process:

17

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

• Create a service account in the CloudEndure User Console instead of using individual administratoraccounts.

• Make sure that you have sufficient migration licenses for your project.• Install CloudEndure Agent on your source machines at least three weeks before your planned cutover.

This will give you enough time to test and help identify any issues in advance.• Install CloudEndure Agents on the source machines by using the --no-replication argument, to

prevent the replication from starting automatically.• When scheduling your cutover, allow enough time for data replication to complete and for all

necessary testing to be carried out.• Complete cutover within 90 days after you install the CloudEndure Agent. Migration licenses expire

after 90 days.• Do not perform any reboots on the source machines before a cutover.• Perform a test cutover at least one week before you plan to migrate your source machines. This will

help you identify potential problems and solve them before the actual cutover takes place. Afterperforming the test launch:• Validate connectivity to your target machines (using SSH for Linux or RDP for Windows), and

perform acceptance tests for your application.• Verify that the subnet of the target site is isolated, to prevent conflicts with the source site.• Verify that your network works as expected.• Verify service configuration and other settings.

• For Network Bandwidth Throttling, select Disabled. Enable this option only if you want to control theamount of bandwidth used for replication traffic.

• Remove the source machines from the CloudEndure User Console after cutover is complete, to cleanup the staging area, remove the replication resources that are no longer needed, and reduce yourcosts.

• If you’re replicating a large instance, use a dedicated replication server to accelerate replication.• After final cutover, verify that the launched Amazon Elastic Compute Cloud (Amazon EC2) instance

passes health checks (2/2 checks passed status) on AWS.

18

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Can I use my existing Windowslicensing with CloudEndure Migration?

CloudEndure Migration FAQ

This section provides answers to commonly raised questions about using CloudEndure Migration tomigrate your workloads. For additional information, see the FAQ on the CloudEndure website.

Can I use my existing Windows licensing withCloudEndure Migration?

You have a variety of options for using new and existing Microsoft software licenses on the AWS Cloud.

• You can purchase Amazon EC2 or Amazon Relational Database Service (Amazon RDS) license-includedinstances to get new, fully compliant Windows Server and SQL Server licenses from AWS.

• You can use your existing licenses on AWS with Amazon EC2 Dedicated Hosts, Amazon EC2 DedicatedInstances, or EC2 instances with default tenancy by using Microsoft License Mobility through SoftwareAssurance. Whether you want to purchase new Microsoft licenses, or utilize existing ones, you can relyon AWS to run your Microsoft software.

CloudEndure converts Microsoft Windows licenses to AWS Windows licenses and activates them by usingMicrosoft Key Management Service. If license activation fails, follow the instructions on the AWS supportwebsite to resolve the issue.

Can I use my existing Linux licenses withCloudEndure Migration?

When you migrate your Linux machines to AWS with CloudEndure Migration, you must supply your ownLinux OS licenses (BYOL). That is, AWS will not assign its own Linux OS licenses automatically.

What is the required bandwidth for TCP port 1500to replicate data?

The required bandwidth for transferring the replicated data over TCP port 1500 should be based on thewrite speed of the participating source machines. The minimum bandwidth is the sum of the averagewrite speed of all replicated source machines.

For example, if you are replicating two source machines that have write speeds of 5 megabytes persecond (MBps) and 7 MBps, the recommended bandwidth should be at least 12 MBps.

19

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Can I change the default disk type to SSD instead ofProvisioned SSD in the Blueprint for the target instance?

Can I change the default disk type to SSD insteadof Provisioned SSD in the Blueprint for the targetinstance?

You can change the default disk type, but this affects the first boot time of the target machine. Thetarget machine will boot much more slowly the first time on AWS. Sometimes, this process is so slowthat some Windows processes will time out and network drivers won’t be activated during bootup time.

How can I route replication traffic when I havemultiple leased lines in the source? Is thereconfiguration setting I can use in CloudEndure?

CloudEndure uses standard routing. If you configure the router to push the data to the IP addresses tothe staging area over the second link, this is what it'll do.

What compression mechanism does CloudEndureuse during replication?

CloudEndure uses Lempel-Ziv-Welch (LZW) compression during transit, which results in 60-70%compression, depending on the type of data.

What does the CloudEndure machine conversionserver do?

The machine conversion server runs in the target infrastructure and converts the disks to boot.Specifically, this server makes bootloader changes, injects hypervisor drivers, and installs cloud tools. TheCloudEndure machine conversion process typically takes less than a minute.

What are the differences between conversionservers and replication servers?

Here’s a list of similarities and differences between the two server types:

• Replication servers run on Linux, and conversion servers (for Windows machines) run on Windows.• When CloudEndure launches replication servers, it automatically places Windows conversion servers in

the same subnet as the replication servers.• Both conversion and replication servers have public IPs.• Conversion servers use the same security groups as replication servers.

20

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Which AWS Regions does CloudEndureuse for production and disaster recovery?

• The conversion server must be able to access the CloudEndure Service Manager.• The conversion server machines, just like replication servers, are managed automatically by

CloudEndure. Any attempt to disrupt their automated functionality will result in failed conversions.

Which AWS Regions does CloudEndure use forproduction and disaster recovery?

CloudEndure uses US East (N. Virginia) for production and US West (N. California) for disaster recovery.Data is copied from the production Region to the disaster recovery Region over a private AWS network.

What is the effect of having a dedicated replicationserver?

The dedicated replication instance makes full use of available bandwidth to accelerate replication.

21

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Next stepsBecause CloudEndure Migration minimizes cutover downtime and provides continuous replication, ithandles migration scenarios such as migrating your servers to AWS, deploying a block-level replicationsolution, or supporting real-time replication requirements much better than other migration tools.

If your enterprise is committed to a cloud migration journey and you wish to achieve a range of businessbenefits by migrating existing workloads to AWS, learn more about the AWS Migration AccelerationProgram (MAP), which provides consulting support, training, and services credits.

Before you migrate your production workloads, we recommend that you run a proof of concept (POC) tounderstand the CloudEndure Migration tool, infrastructure requirements, data transfer speeds, and othermigration considerations.

22

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Additional resourcesRelated guides and patterns

• CloudEndure Migration patterns• Automating large-scale server migrations with CloudEndure Migration Factory• Migrating Oracle databases to the AWS Cloud• Migrating SQL Server databases to the AWS Cloud• AWS Prescriptive Guidance website

References

• Migrating workloads across AWS Regions with CloudEndure Migration (blog post)• Migration Best Practices (CloudEndure documentation)• Troubleshooting Playbook (CloudEndure documentation)• CloudEndure documentation home page

Tools

• CloudEndure API documentation• CloudEndure API• AWS CloudEndure Migration Factory solution• AWS Migration Hub• AWS Migration Evaluator• CloudEndure Migration Training - Technical• CloudEndure Disaster Recovery Technical Training

23

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

AWS Prescriptive Guidance glossary

AI and ML terms (p. 24)    |    Migration terms (p. 25)    |    Modernization terms (p. 28)

AI and ML terms The following are commonly used terms in artificial intelligence (AI) and machine learning (ML)-related strategies,guides, and patterns provided by AWS Prescriptive Guidance. To suggest entries, please use the Provide feedbacklink at the end of the glossary.

binary classification A process that predicts a binary outcome (one of two possible classes). Forexample, your ML model might need to predict problems such as “Is this emailspam or not spam?" or "Is this product a book or a car?"

classification A categorization process that helps generate predictions. ML models forclassification problems predict a discrete value. Discrete values are always distinctfrom one another. For example, a model might need to evaluate whether or notthere is a car in an image.

data preprocessing To transform raw data into a format that is easily parsed by your ML model.Preprocessing data can mean removing certain columns or rows and addressingmissing, inconsistent, or duplicate values.

deep ensemble To combine multiple deep learning models for prediction. You can use deepensembles to obtain a more accurate prediction or for estimating uncertainty inpredictions.

deep learning An ML subfield that uses multiple layers of artificial neural networks to identifymapping between input data and target variables of interest.

exploratory data analysis(EDA)

The process of analyzing a dataset to understand its main characteristics. Youcollect or aggregate data and then perform initial investigations to find patterns,detect anomalies, and check assumptions. EDA is performed by calculatingsummary statistics and creating data visualizations.

features The input data that you use to make a prediction. For example, in amanufacturing context, features could be images that are periodically capturedfrom the manufacturing line.

feature transformation To optimize data for the ML process, including enriching data with additionalsources, scaling values, or extracting multiple sets of information from a singledata field. This enables the ML model to benefit from the data. For example, ifyou break down the “2021-05-27 00:15:37” date into “2021”, “May”, “Thu”, and“15”, you can help the learning algorithm learn nuanced patterns associated withdifferent data components.

24

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

multiclass classification A process that helps generate predictions for multiple classes (predicting one ofmore than two outcomes). For example, an ML model might ask "Is this producta book, car, or phone?" or "Which product category is most interesting to thiscustomer?"

regression An ML technique that predicts a numeric value. For example, to solve the problemof "What price will this house sell for?" an ML model could use a linear regressionmodel to predict a house's sale price based on known facts about the house (forexample, the square footage).

training To provide data for your ML model to learn from. The training data must containthe correct answer. The learning algorithm finds patterns in the training data thatmap the input data attributes to the target (the answer that you want to predict).It outputs an ML model that captures these patterns. You can then use the MLmodel to make predictions on new data for which you don’t know the target.

target variable The value that you are trying to predict in supervised ML. This is also referredto as an outcome variable. For example, in a manufacturing setting the targetvariable could be a product defect.

tuning To change aspects of your training process to improve the ML model's accuracy.For example, you can train the ML model by generating a labeling set, addinglabels, and then repeating these steps several times under different settings tooptimize the model.

uncertainty A concept that refers to imprecise, incomplete, or unknown information thatcan undermine the reliability of predictive ML models. There are two types ofuncertainty: Epistemic uncertainty is caused by limited, incomplete data, whereasaleatoric uncertainty is caused by the noise and randomness inherent in the data.For more information, see the Quantifying uncertainty in deep learning systemsguide.

Migration terms The following are commonly used terms in migration-related strategies, guides, and patterns provided by AWSPrescriptive Guidance. To suggest entries, please use the Provide feedback link at the end of the glossary.

7 Rs Seven common migration strategies for moving applications to the cloud. Thesestrategies build upon the 5 Rs that Gartner identified in 2011 and consist of thefollowing:

• Refactor/re-architect – Move an application and modify its architecture bytaking full advantage of cloud-native features to improve agility, performance,and scalability. This typically involves porting the operating system anddatabase. Example: Migrate your on-premises Oracle database to the AmazonAurora PostgreSQL-Compatible Edition.

• Replatform (lift and reshape) – Move an application to the cloud, and introducesome level of optimization to take advantage of cloud capabilities. Example:Migrate your on-premises Oracle database to Amazon Relational DatabaseService (Amazon RDS) for Oracle in the AWS Cloud.

• Repurchase (drop and shop) – Switch to a different product, typically by movingfrom a traditional license to a SaaS model. Example: Migrate your customerrelationship management (CRM) system to Salesforce.com.

• Rehost (lift and shift) – Move an application to the cloud without making anychanges to take advantage of cloud capabilities. Example: Migrate your on-premises Oracle database to Oracle on an EC2 instance in the AWS Cloud.

25

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

• Relocate (hypervisor-level lift and shift) – Move infrastructure to the cloudwithout purchasing new hardware, rewriting applications, or modifying yourexisting operations. This migration scenario is specific to VMware Cloudon AWS, which supports virtual machine (VM) compatibility and workloadportability between your on-premises environment and AWS. You can use theVMware Cloud Foundation technologies from your on-premises data centerswhen you migrate your infrastructure to VMware Cloud on AWS. Example:Relocate the hypervisor hosting your Oracle database to VMware Cloud onAWS.

• Retain (revisit) – Keep applications in your source environment. These mightinclude applications that require major refactoring, and you want to postponethat work until a later time, and legacy applications that you want to retain,because there’s no business justification for migrating them.

• Retire – Decommission or remove applications that are no longer needed inyour source environment.

application portfolio A collection of detailed information about each application used by anorganization, including the cost to build and maintain the application, and itsbusiness value. This information is key to the portfolio discovery and analysisprocess and helps identify and prioritize the applications to be migrated,modernized, and optimized.

artificial intelligenceoperations (AIOps)

The process of using machine learning techniques to solve operational problems,reduce operational incidents and human intervention, and increase servicequality. For more information about how AIOps is used in the AWS migrationstrategy, see the operations integration guide.

AWS Cloud AdoptionFramework (AWS CAF)

A framework of guidelines and best practices from AWS to help organizationsdevelop an efficient and effective plan to move successfully to the cloud. AWSCAF organizes guidance into six focus areas called perspectives: business,people, governance, platform, security, and operations. The business, people,and governance perspectives focus on business skills and processes; theplatform, security, and operations perspectives focus on technical skills andprocesses. For example, the people perspective targets stakeholders who handlehuman resources (HR), staffing functions, and people management. For thisperspective, AWS CAF provides guidance for people development, training, andcommunications to help ready the organization for successful cloud adoption. Formore information, see the AWS CAF website and the AWS CAF whitepaper.

AWS landing zone A landing zone is a well-architected, multi-account AWS environment that isscalable and secure. This is a starting point from which your organizations canquickly launch and deploy workloads and applications with confidence in theirsecurity and infrastructure environment. For more information about landingzones, see Setting up a secure and scalable multi-account AWS environment.

AWS Workload QualificationFramework (AWS WQF)

A tool that evaluates database migration workloads, recommends migrationstrategies, and provides work estimates. AWS WQF is included with AWS SchemaConversion Tool (AWS SCT). It analyzes database schemas and code objects,application code, dependencies, and performance characteristics, and providesassessment reports.

business continuity planning(BCP)

A plan that addresses the potential impact of a disruptive event, such as a large-scale migration, on operations and enables a business to resume operationsquickly.

Cloud Center of Excellence(CCoE)

A multi-disciplinary team that drives cloud adoption efforts across anorganization, including developing cloud best practices, mobilizing resources,establishing migration timelines, and leading the organization through large-

26

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

scale transformations. For more information, see the CCoE posts on the AWSCloud Enterprise Strategy Blog.

cloud stages of adoption The four phases that organizations typically go through when they migrate to theAWS Cloud:

• Project – Running a few cloud-related projects for proof of concept andlearning purposes

• Foundation – Making foundational investments to scale your cloud adoption(e.g., creating a landing zone, defining a CCoE, establishing an operationsmodel)

• Migration – Migrating individual applications• Re-invention – Optimizing products and services, and innovating in the cloud

These stages were defined by Stephen Orban in the blog post The JourneyToward Cloud-First & the Stages of Adoption on the AWS Cloud EnterpriseStrategy blog. For information about how they relate to the AWS migrationstrategy, see the migration readiness guide.

configuration managementdatabase (CMDB)

A database that contains information about a company’s hardware and softwareproducts, configurations, and inter-dependencies. You typically use data from aCMDB in the portfolio discovery and analysis stage of migration.

epic In agile methodologies, functional categories that help organize and prioritizeyour work. Epics provide a high-level description of requirements andimplementation tasks. For example, AWS CAF security epics include identity andaccess management, detective controls, infrastructure security, data protection,and incident response. For more information about epics in the AWS migrationstrategy, see the program implementation guide.

heterogeneous databasemigration

Migrating your source database to a target database that uses a differentdatabase engine (for example, Oracle to Amazon Aurora). Heterogeneousmigration is typically part of a re-architecting effort, and converting theschema can be a complex task. AWS provides AWS SCT that helps with schemaconversions.

homogeneous databasemigration

Migrating your source database to a target database that shares the samedatabase engine (for example, Microsoft SQL Server to Amazon RDS for SQLServer). Homogeneous migration is typically part of a rehosting or replatformingeffort. You can use native database utilities to migrate the schema.

IT information library (ITIL) A set of best practices for delivering IT services and aligning these services withbusiness requirements. ITIL provides the foundation for ITSM.

IT service management (ITSM) Activities associated with designing, implementing, managing, and supporting ITservices for an organization. For information about integrating cloud operationswith ITSM tools, see the operations integration guide.

Migration AccelerationProgram (MAP)

An AWS program that provides consulting support, training, and services tohelp organizations build a strong operational foundation for moving to thecloud, and to help offset the initial cost of migrations. MAP includes a migrationmethodology for executing legacy migrations in a methodical way and a set oftools to automate and accelerate common migration scenarios.

Migration PortfolioAssessment (MPA)

An online tool that provides information for validating the business case formigrating to the AWS Cloud. MPA provides detailed portfolio assessment(server right-sizing, pricing, TCO comparisons, migration cost analysis) as wellas migration planning (application data analysis and data collection, applicationgrouping, migration prioritization, and wave planning). The MPA tool (requires

27

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

login) is available free of charge to all AWS consultants and APN Partnerconsultants.

Migration ReadinessAssessment (MRA)

The process of gaining insights about an organization’s cloud readiness status,identifying strengths and weaknesses, and building an action plan to closeidentified gaps, using the AWS CAF. For more information, see the migrationreadiness guide. MRA is the first phase of the AWS migration strategy.

migration at scale The process of moving the majority of the application portfolio to the cloud inwaves, with more applications moved at a faster rate in each wave. This phaseuses the best practices and lessons learned from the earlier phases to implementa migration factory of teams, tools, and processes to streamline the migration ofworkloads through automation and agile delivery. This is the third phase of theAWS migration strategy.

migration factory Cross-functional teams that streamline the migration of workloads throughautomated, agile approaches. Migration factory teams typically includeoperations, business analysts and owners, migration engineers, developers,and DevOps professionals working in sprints. Between 20 and 50 percent ofan enterprise application portfolio consists of repeated patterns that can beoptimized by a factory approach. For more information, see the discussion ofmigration factories and the CloudEndure Migration Factory guide in this contentset.

operational-level agreement(OLA)

An agreement that clarifies what functional IT groups promise to deliver to eachother, to support a service-level agreement (SLA).

operations integration (OI) The process of modernizing operations in the cloud, which involves readinessplanning, automation, and integration. For more information, see the operationsintegration guide.

organizational changemanagement (OCM)

A framework for managing major, disruptive business transformations from apeople, culture, and leadership perspective. OCM helps organizations prepare for,and transition to, new systems and strategies by accelerating change adoption,addressing transitional issues, and driving cultural and organizational changes. Inthe AWS migration strategy, this framework is called people acceleration, becauseof the speed of change required in cloud adoption projects. For more information,see the OCM guide.

playbook A set of predefined steps that capture the work associated with migrations, suchas delivering core operations functions in the cloud. A playbook can take the formof scripts, automated runbooks, or a summary of processes or steps required tooperate your modernized environment.

responsible, accountable,consulted, informed (RACI)matrix

A matrix that defines and assigns roles and responsibilities in a project. Forexample, you can create a RACI to define security control ownership or to identifyroles and responsibilities for specific tasks in a migration project.

runbook A set of manual or automated procedures required to perform a specific task.These are typically built to streamline repetitive operations or procedures withhigh error rates.

service-level agreement (SLA) An agreement that clarifies what an IT team promises to deliver to theircustomers, such as service uptime and performance.

Modernization termsThe following are commonly used terms in modernization-related strategies, guides, and patterns provided by AWSPrescriptive Guidance. To suggest entries, please use the Provide feedback link at the end of the glossary.

28

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

business capability What a business does to generate value (for example, sales, customer service,or marketing). Microservices architectures and development decisions can bedriven by business capabilities. For more information, see the Organized aroundbusiness capabilities section of the Running containerized microservices on AWSwhitepaper.

microservice A small, independent service that communicates over well-defined APIs and istypically owned by small, self-contained teams. For example, an insurance systemmight include microservices that map to business capabilities, such as sales ormarketing, or subdomains, such as purchasing, claims, or analytics. The benefitsof microservices include agility, flexible scaling, easy deployment, reusable code,and resilience. For more information, see Integrating microservices by using AWSserverless services.

microservices architecture An approach to building an application with independent components that runeach application process as a microservice. These microservices communicatethrough a well-defined interface by using lightweight APIs. Each microservicein this architecture can be updated, deployed, and scaled to meet demand forspecific functions of an application. For more information, see Implementingmicroservices on AWS.

modernization Transforming an outdated (legacy or monolithic) application and its infrastructureinto an agile, elastic, and highly available system in the cloud to reduce costs,gain efficiencies, and take advantage of innovations. For more information, seeStrategy for modernizing applications in the AWS Cloud.

modernization readinessassessment

An evaluation that helps determine the modernization readiness of anorganization’s applications; identifies benefits, risks, and dependencies; anddetermines how well the organization can support the future state of thoseapplications. The outcome of the assessment is a blueprint of the targetarchitecture, a roadmap that details development phases and milestones for themodernization process, and an action plan for addressing identified gaps. Formore information, see Evaluating modernization readiness for applications in theAWS Cloud.

monolithic applications(monoliths)

Applications that run as a single service with tightly coupled processes. Monolithicapplications have several drawbacks. If one application feature experiences aspike in demand, the entire architecture must be scaled. Adding or improving amonolithic application’s features also becomes more complex when the code basegrows. To address these issues, you can use a microservices architecture. For moreinformation, see Decomposing monoliths into microservices.

polyglot persistence Independently choosing a microservice’s data storage technology based on dataaccess patterns and other requirements. If your microservices have the samedata storage technology, they can encounter implementation challenges orexperience poor performance. Microservices are more easily implemented andachieve better performance and scalability if they use the data store best adaptedto their requirements. For more information, see Enabling data persistence inmicroservices.

split-and-seed model A pattern for scaling and accelerating modernization projects. As new featuresand product releases are defined, the core team splits up to create new productteams. This helps scale your organization’s capabilities and services, improvesdeveloper productivity, and supports rapid innovation. For more information, seePhased approach to modernizing applications in the AWS Cloud.

two-pizza team A small DevOps team that you can feed with two pizzas. A two-pizza team sizeensures the best possible opportunity for collaboration in software development.

29

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

For more information, see the Two-pizza team section of the Introduction toDevOps on AWS whitepaper.

30

AWS Prescriptive Guidance Migrating workloadsto the AWS Cloud by using CloudEndure Migration

Document historyThe following table describes significant changes to this guide. If you want to be notified about futureupdates, you can subscribe to an RSS feed.

update-history-change update-history-description update-history-date

Added video (p. 31) We added a video thatcovers best practices andtroubleshooting tips.

January 27, 2021

Initial publication (p. 31) — November 23, 2020

31