NEW - You can now accelerate your migration and modernization with AWS Transform. Read [Getting Started](https://docs.aws.amazon.com/transform/latest/userguide/getting-started.html) in the *AWS Transform User Guide*.
# Quick start guide for AWS Application Migration Service
Follow this guide to set up AWS Application Migration Service for the first time, including:
**Topics**
+ [First time setup](first-time-setup-gs.md)
+ [Adding source servers](adding-servers-gs.md)
+ [Configuring launch settings](configuring-target-gs.md)
+ [Launching a test instance](launching-test-gs.md)
+ [Launching a cutover instance](launch-cutover-gs.md)
# First time setup
The first setup step for AWS Application Migration Service is creating the replication template.
Choose **Get started** on the AWS Application Migration Service landing page.
You will automatically be prompted to initialize the service the first time you log into AWS Application Migration Service.
Initializing the service will create a replication template. This template will determine how data replication will work for each newly added source server.
The configured replication settings can be changed at any time for any individual source server or group of source servers. [Learn more about replication settings.](replication-settings-template.md)
[Learn more about changing individual server and multiple server replication settings.](replication-settings-template.md#template-vs-server)
**Important**
Prior to configuring your replication template, ensure that you meet the [Network requirements for running AWS Application Migration Service](preparing-environments.md).
Once AWS Application Migration Service is initialized you'll be redirected into the MGN console **Source servers** page.
To edit your replication template, click **Replication template** on the left-hand navigation menu. You will be able to edit individual server replication settings after adding your source servers to AWS Application Migration Service.
The next step of the setup process is adding your source servers to AWS Application Migration Service.
# Adding source servers
Add source servers to AWS Application Migration Service by installing the AWS Replication Agent (the Agent) on them. The Agent can be installed on both Linux and Windows servers. [Learn more about adding source servers.](adding-servers.md)
**Note**
If you are using the agentless replication for vCenter feature, then you will need to add your source servers by installing the AWS MGN vCenter Client. [Learn more about agentless replication.](agentless-mgn.md)
Prior to adding your source servers, ensure that you meet all of the [network requirements](preparing-environments.md).
The following is the AWS MGN agent network architecture diagram:
![\[AWS cloud migration architecture showing data replication from on-premises to AWS staging and migrated resources.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/AWSMGNArchitecture.png)
## Migration lifecycle
After the source server has been added to AWS Application Migration Service, it will undergo the migration lifecycle steps.
The migration lifecycle shows the current state of each source server within the migration process. Lifecycle states include:
+ **Not ready** – The server is undergoing the initial sync process and is not yet ready for testing. Data replication can only commence once all of the initial sync steps have been completed.
+ **Ready for testing** – The server has been successfully added to AWS Application Migration Service and data replication has started. test or cutover instances can now be launched for this server.
+ **Test in progress** – A Test instance is currently being launched for this server.
+ **Ready for cutover** – This server has been tested and is now ready for a cutover instance to be launched.
+ **Cutover in progress** – A cutover instance is currently being launched for this server.
+ **Cutover complete** – This server has been cutover. All of the data on this server has been migrated to the AWS cutover instance.
+ **Disconnected** – This server has been disconnected from AWS Application Migration Service.
[Learn more about the migration lifecycle states.](migration-dashboard.md#lifecycle)
Once the initial async process has completed successfully, data replication will start automatically.
# Configuring launch settings
After you have added your source servers to the AWS Application Migration Service console, you will need to configure the launch settings for each server. The launch settings are a set of instructions that determine how a test or cutover instance will be launched for each source server on AWS. You must configure the launch settings prior to launching test or cutover instances. You can use the default settings or configure the settings to fit your requirements.
**Note**
You can change the launch settings after a test or cutover instance has been launched. You will need to launch a new test or cutover instance for the new settings to take effect.
You can access the launch settings by clicking on the source server name of a source server on the **Source servers** page.
Within the individual server view, navigate to the **Launch settings** tab.
Here you can see your **General launch settings** and **EC2 launch template**. Click the **Edit** button to edit your Launch settings or **Modify** to change your EC2 launch template.
Launch settings are composed of the following:
+ **Instance type right-sizing** – The Instance type right-sizing feature allows AWS Application Migration Service to launch a test or cutover instance type that best matches the hardware configuration of the source server. When activated, this feature overrides the instance type selected in the EC2 launch template.
+ **Start instance upon launch** – Choose whether you want to start your test and cutover instances automatically upon launch or whether you want to start them manually through the Amazon EC2 Console.
+ **Copy private IP** – Choose whether you want Application Migration Service to verify that the private IP used by the test or cutover instance matches the private IP used by the source server (not supported for IPv6).
+ **Transfer server tags** – Choose whether you want AWS Application Migration Service to transfer any user-configured custom tags from your source servers to your test or cutover instance.
+ **OS Licensing** – Choose whether you want to Bring Your Own Licenses (BYOL) from the source server to the test or cutover instance.
AWS Application Migration Service automatically creates an **EC2 launch template** for each new source server. AWS Application Migration Service bases the majority of the instance launch settings on this template. You can edit this template to fit your needs.
[Learn more about Launch settings.](launch-settings.md)
# Launching a test instance
After you have added all of your source servers and configured their launch settings, you are ready to launch a test instance. It is crucial to test the migration of your source servers to AWS prior to initiating a cutover in order to verify that your source servers function properly within the AWS environment.
**Important**
It is a best practice to perform a test at least two weeks before you plan to migrate your source servers. This time frame allows you to identify potential problems and solve them, before the actual cutover takes place. After launching test instances, use either SSH (Linux) or RDP (Windows) to connect to your instance and ensure that everything is working correctly.
You can test one source server at a time, or simultaneously test multiple source servers. For each source server, you will be informed of the success or failure of the test. You can test your source server as many times as you want. Each new test first deletes any previously launched test instance and dependent resources. Then, a new test instance is launched, which reflects the most up-to-date state of the source server. After the test, data replication continues as before. The new and modified data on the source server is transferred to the staging area subnet and not to the test instances that were launched during the test.
**Note**
When launching a test or cutover instance, you can launch up to 100 source servers in a single operation. Additional source servers can be launched in subsequent operations.
Windows source servers need to have at least 2 GB of free space to successfully launch a test instance.
Take into consideration that once a test instance is launched, actual resources will be used in your AWS account and you will be billed for these resources. You can terminate the operation of launched Test instances once you verify that they are working properly without impact in order to data replication.
## Ready for testing indicators
Prior to launching a Test instance, ensure that your source servers are ready for testing by looking for the following indicators on the **Source servers** page:
1. Under the **Migration lifecycle** column, the server should show **Ready for testing**.
1. Under the **Data replication status** column, the server should show the **Healthy** status.
1. Under the **Next step** column, the server should show **Launch test instance**.
## Starting a test
To launch a test instance for a single source server or multiple source servers, take the following steps:
+ Go to the **Source servers** page and check the box to the left of each server for which you want to launch a test instance.
+ Open the **Test and cutover** menu.
+ Under **Testing**, choose the **Launch test instances** option to launch a test instance for this server.
+ When the **Launch test instances for X** **servers** dialog appears, choose **Launch** to begin the test.
The AWS Application Migration Service console will indicate **Launch job started** when the test has started.
Choose **View job details** on the dialog to view the specific Job for the test launch in the **Launch History** tab.
### Successful test launch indicators
You can tell that the Test instance launch started successfully through several indicators on the **Source Servers** page.
1. The Alerts column will show the **Launched** status, indicating that a test instance has been launched for this server.
1. The **Migration lifecycle** column will show **Test in progress**.
1. The **Next step** column will show **Complete testing and mark as 'Ready for cutover'**.
## Reverting or finalizing a test
After you have launched your test instances, open the Amazon EC2 Console and SSH or RDP into your test instances in order to ensure that they function correctly. Validate connectivity and perform acceptance tests for your application.
### Reverting a test
If you encounter any issues and want to launch new test instances, or if you are performing a scheduled test and plan to perform additional tests prior to cutover, you can revert the test. This will revert your source servers' **Migration lifecycle** status to **Ready for testing**, indicating that these servers still require additional testing before they are ready for cutover. During a revert, you will also have the option to delete your Test instances for cost-saving purposes.
To revert a test:
1. Check the box to the left of every source server that has a launched test instance for which you want to revert the test.
1. Open the **Test and cutover** menu.
1. Under **Testing**, choose **Revert to "ready for testing"**
1. When the **Revert testing for X servers** dialog appears, select whether you want to terminate the launched instances used for testing. It is recommended to terminate these instances, as you will be charged for them even though you will no longer need them. Check the **Yes, terminate launched instances (recommended)** box and choose **Revert**.
The AWS Application Migration Service console will indicate that testing has been reverted. The selected source servers' **Migration lifecycle** column will show the **Ready for testing** status, the **Next step** column will show **Launch test instance** and the launched Test instances will be deleted if that option was selected.
### Marking as Ready for cutover
If you are completely done with your testing and are ready for cutover, you can finalize the test. This will change your source servers' **Migration lifecycle** status to **Ready for cutover**, indicating that all testing is complete and that these servers are now ready for cutover. You will also have the option to delete your Test instances for cost saving purposes.
To finalize a test:
1. Check the box to the left of every source server that has a launched Test instance for which you want to finalize the test.
1. Open the **Test and Cutover** menu.
1. Under **Testing**, choose **Mark as "Ready for cutover"**
1. Mark X servers as "Ready for cutover" dialog will appear. Select whether you want to terminate the launched instances used for testing. It is recommended to terminate these instances, as you will be charged for them even though you will no longer need them. Check the **Yes, terminate launched instances (recommended)** box and choose **Continue**.
1. The AWS Application Migration Service console will confirm that the servers were marked as ready for cutover.
The console will indicate that testing has been finalized. The selected source servers' **Migration lifecycle** column will show the **Ready for cutover** status and the launched test instances will be deleted if that option was selected. The **Next step** column will show **Terminate launched instance; Launch cutover instance**.
1. You can now terminate the launched test instance directly from the Amazon EC2 Console as that instance is no longer needed (if you have not done so already through the AWS MGN Console). You can quickly access the Test instance by navigating to the specific servers > **Server Details > Migration dashboard > Lifecycle > Launch status** and choosing **View in EC2 Console.**
1. The Amazon EC2 Console will automatically search for and display the test instance. Select the instance, open the **Instance state** menu, and choose **Terminate instance**. When the confirmation dialogue appears, click **Terminate**.
# Launching a cutover instance
Once you have finalized the testing of all of your source servers, you are ready for cutover. You should perform the cutover at a set date and time. The cutover will migrate your source servers to the cutover instances on AWS.
**Important**
It is a best practice to perform a test at least two weeks before you plan to migrate your source servers. This time frame allows you to identify potential problems and solve them, before the actual migration takes place. After launching test instances, use either SSH (Linux) or RDP (Windows) to connect to your instance and ensure that everything is working correctly.
You can cutover one source server at a time, or simultaneously cutover multiple source servers. For each source server, you will be informed of the success or failure of the cutover. For each new cutover, AWS Application Migration Service first deletes any previously launched Test instance and dependent resources. Then, it launches a new cutover instance which reflects the most up-to-date state of the source server. After the cutover, data replication continues as before. The new and modified data on the source server is transferred to the Staging Area Subnet, and not to the cutover instances that were launched during the cutover.
## Ready for cutover indicators
Prior to launching a cutover instance, ensure that your source servers are ready for cutover by looking for the following indicators on the **Source Servers** page:
1. Under the **Migration lifecycle** column, the server should show **Ready for cutover** .
1. Under the **Data replication status** column, the server should show the **Healthy** status.
1. Under the **Next step** column, the server should show **Terminate launched instance; Launch cutover instance** if you have not terminated your latest launched test instance.
1. Alternatively, the Next step column will show **Launch cutover instance** if you have terminated your latest launched test instance.
## Starting a cutover
To launch a cutover instance for a single source server or multiple source servers, take the following steps:
1. Go to the **Source servers** page and check the box to the left of each server you want to cutover.
1. Open the **Test and cutover** menu.
1. Under **Cutover**, choose the **Launch cutover instances** option.
1. When the **Launch cutover instances for X** servers dialog appears, choose **Launch** to begin the cutover.
On the **Source servers** page, the **Migration lifecycle** column will show **Cutover in progress** and the **Next step** column will show **Finalize cutover**. When the cutover starts, the Application Migration Service Console will indicate **Launch job started**.
1. Choose **View job details** on the dialog to view the specific Job for the cutover launch in the** Launch History** tab.
### Successful cutover launch indicators
You can tell that the cutover instance launch was started successfully through several indicators on the **Source servers** page.
1. The **Alerts** column will state **Launched**.
1. The **Migration lifecycle** column will state **Cutover in progress**.
1. The **Data replication status** will state **Healthy**.
1. The **Next step column** will state **Finalize cutover**.
## Reverting or finalizing a cutover
Once you have launched your cutover instances, open the Amazon EC2 Console and SSH or RDP into your cutover instances in order to ensure that they function correctly. Validate connectivity and perform acceptance tests for your application.
**Note**
You should turn on Termination Protection after you have completed your testing and before you are ready to finalize the cutover. Learn more about enabling termination protection in [this Amazon EC2 article ](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/terminating-instances.html#Using_ChangingDisableAPITermination).
### Reverting a cutover
If you encounter any issues and want to launch new cutover instances, you can revert the cutover. This will revert your source servers' **Migration lifecycle** status to **Ready for cutover**, indicating that these servers have not undergone cutover. During a revert, you will also have the option to delete your Cutover instances for cost-saving purposes.
To revert a cutover:
1. Check the box to the left of every source server that has a launched cutover instance you want to revert.
1. Open the **Test and cutover** menu.
1. Under **Cutover**, choose **Revert to "ready for cutover"**
1. This will revert your source servers' **Migration lifecycle** status to **Ready for cutover**, indicating that these servers have not undergone cutover.
When the **Revert cutover for X servers** dialog appears, click **Revert**.
### Finalizing a cutover
If you are completely done with your migration and performed a successful cutover, you can finalize the cutover. This will change your source servers' **Migration lifecycle** status to **Cutover complete**, indicating that the cutover is complete and that the migration has been performed successfully. In addition, this will stop data replication and cause all replicated data to be discarded. All AWS resources used for data replication will be terminated.
To finalize a cutover:
1. Check the box to the left of every source server that has a launched cutover instance you want to finalize.
1. Open the **Test and cutover** menu.
1. Under **Cutover**, choose **Finalize cutover**.
1. The **Finalize cutover for X servers** dialog will appear. Choose **Finalize**. This will change your source servers' **Migration lifecycle** status to **Cutover complete**, indicating that the cutover is complete and that the migration has been performed successfully. In addition, this will stop data replication and cause all replicated data to be discarded. All AWS resources used for data replication will be terminated.
The AWS Application Migration Service console will indicate **Cutover finalized** when the cutover has completed successfully.
The AWS Application Migration Service console will automatically stop data replication for the source servers that were cutover in order to save resource costs. The selected source servers' **Migration lifecycle** column will show the **Cutover complete** status, the **Data replication** status column will show **Disconnected**, and the **Next step** column will show **Mark as archived**. The source servers have now been successfully migrated into AWS.
1. You can now archive your source servers that have launched cutover instances. Archiving will remove these source servers from the main **Source servers** page, allowing you to focus on source servers that have not yet been cutover. You will still be able to access the archived servers through filtering options.
To archive your cutover source servers:
1. Check the box to the left of the of each source server for which the **Migration lifecycle** column states **Cutover complete**.
1. Open the **Actions** menu and choose **Mark as archived**.
1. When the **Archive X server** dialog appears, click **Archive**.
1. To see your archived servers, choose **Archived source servers** from the drop-down menu in the source servers view.
You will now be able to see all of your archived servers. Use the same drop-down menu to see only **Active source servers** or **Discovered source servers**, according to your preferences.