Nearly a yr in the past, Channy confirmed you Learn how to Use the New AWS Software Migration Server for Elevate-and-Shift Migrations. In his publish, he launched AWS Software Migration Service (AWS MGN) and stated:
With AWS MGN, you may reduce time-intensive, error-prone guide processes by mechanically replicating total servers and changing your supply servers from bodily, digital, or cloud infrastructure to run natively on AWS. The service simplifies your migration by enabling you to make use of the identical automated course of for a variety of purposes.
Since launch, now we have added agentless replication together with help for Home windows 10 and a number of variations of Home windows Server (2003, 2008, and 2022). We additionally expanded into further areas all through 2021.
New Submit-Launch Actions
Because the title of Channy’s publish acknowledged, AWS MGN initially supported direct, lift-and-shift migrations. In different phrases, the chosen disk volumes on the supply servers had been immediately copied, bit-for-bit to EBS volumes connected to freshly launched Amazon Elastic Compute Cloud (Amazon EC2) situations.
Immediately we’re including a set of elective post-launch actions that present further help to your migration and modernization efforts. The actions are initiated and managed by the AWS Methods Supervisor agent, which may be mechanically put in as the primary post-launch motion. We’re launching with an preliminary set of 4 actions, and plan so as to add extra over time:
Set up Agent – This motion installs the AWS Methods Supervisor agent, and is a prerequisite to the opposite actions.
Catastrophe Restoration – Installs the AWS Elastic Catastrophe Restoration Service agent on every server and configures replication to a specified goal area.
SUSE Subscription Conversion – If the supply service is operating SUSE Linux through a subscription offered by SUSE, the occasion is modified to make use of an AWS-provided SUSE subscription.
Utilizing Submit-Launch Actions
My AWS account has a post-launch settings template that serves as a place to begin, and supplies the default settings every time I add a brand new supply server. I can use the values from the template as-is, or I can customise them as wanted. I open the Software Migration Service Console and click on Settings to view and edit my template:
I click on Submit-launch settings template, and evaluation the default values. Then I click on Edit to make adjustments:
As I famous earlier, the Methods Supervisor agent executes the opposite post-launch actions, and is a prerequisite, so I allow it:
Subsequent, I select to run the post-launch actions on each my take a look at and cutover situations, since I wish to take a look at in opposition to the ultimate migrated configuration:
I can now configure any or the entire post-launch choices, beginning with catastrophe restoration. I verify Configure catastrophe restoration on migrated servers and select a goal area:
Subsequent, I verify Convert CentOS to Rocky Linux distribution. This motion converts a CentOS 8 distribution to a Rocky Linux 8 distribution:
Transferring proper alongside, I verify Change SUSE Linux Subscription to AWS offered SUSE Linux subscription, after which click on Save template:
To study extra about pricing for the SUSE subscriptions, go to the Amazon EC2 On-Demand Pricing web page.
After I’ve arrange my template, I can view and edit the settings for every of my supply servers. I merely choose the server and select Edit post-launch settings from the Replication menu:
The post-launch actions might be run on the acceptable time on the take a look at or the cutover situations, per my choices. Any errors that come up through the execution of an motion are written to the SSM execution log. I may also look at the Migration dashboard for every supply server and evaluation the Submit-launch actions:
The post-launch actions can be found now and you can begin utilizing them immediately in all areas the place AWS Software Migration Service (AWS MGN) is supported.