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*. # Group Source Servers and Applications in Waves AWS Application Migration Service helps users manage their migration by grouping **Source servers** and **Applications** in **Waves**. These are logical groups, describing the migration plan over time. You can: + Monitor the wave's migration status, progress, and associated applications + Perform operations on the wave, such as editing, tagging, and archiving + Perform bulk operations on the applications associated with the wave **Topics** + [Manage migration waves](waves-list.md) + [Review migration wave details](wave-details.md) # Manage migration waves The **Waves** page lists all the waves that have been added to AWS Application Migration Service (AWS MGN). The **Waves** page allows you to manage your waves and perform a variety of commands for one or more waves (such as controlling replication and launching test and cutover instances). ## Interacting with the Waves page The **Waves** page shows a list of waves. Each row on the list represents a single wave. The **Waves** page provides key information for each wave under each of the columns on the page. The columns include: + **Selector column** – This blank checkbox selector column allows you to select one or more waves. When a wave is selected, you can interact with the wave through the **Actions** menu, **Edit**, and **Delete** buttons. Selected waves are highlighted. + **Wave name** – This column shows the unique wave name for each wave. + **Migration status** – This column shows the migration status for each wave. + **Not started** – If none of the wave's associated servers has started replication yet. + **In progress** – At least one of the wave's associated applications has started replication and not all of its applications completed migration. + **Completed** – If all the wave associated applications completed migration (have been cutover). + **Alerts** – This column shows whether any alerts exist for the wave. A wave that has at least one application that is experiencing significant issues, such as a stall, will display a **Stalled** status. An wave that has at least one application that is experiencing a temporary issue such as lag or backlog will display a **Lagging** status. A healthy active wave will display a **Healthy** status. Archived waves do not display any alerts. + **Number of applications** – This column shows the total number of applications associated with each wave. **Topics** + [Interacting with the Waves page](#waves-list-interacting) + [Add wave](add-wave.md) + [Edit wave](edit-wave.md) + [Delete wave](delete-wave.md) + [Manage selected waves](wave-actions-menu.md) + [Filtering migration waves](waves-filtering.md) # Add wave To add a wave, click the **Add wave** button. You will then see the **Add wave** prompt that includes the following parameters: + **Wave name** – Select a wave name. The name must be unique per account per region. Note that uniqueness verification for wave name in Migration Application Service is case-insensitive. + **Description (optional)** – Add a description of the wave according to your preferences. + **Associate applications (optional)** – You can add up to 200 applications to a single wave. Checking an application in the dropdown list will associate it with the wave. + **Add tags (optional)** – You can up to 50 tags according to your preferences. Click **Add wave** to create the wave. # Edit wave To edit a wave, click **Edit wave**. You will see the **Edit wave** prompt, which allows you to edit the following parameters: + **Wave name** – Select a wave name. The name must be unique per account per region. Note that uniqueness verification for wave name in Migration Application Service is case-insensitive. + **Description (optional)** – Add a description of the wave according to your preferences. + **Associate** applications (optional) – You can add up to 200 applications to a single wave. Checking an application in the dropdown list will associate it with the wave. + **Add tags (optional)** – You can up to 50 tags according to your preferences. After you edit the parameters as required, click the **Save changes** button to save your changes. # Delete wave To delete a wave, click the **Delete wave** button and the **Delete wave** prompt will open. You will need to verify that you want to delete the selected wave. When you delete the wave, all associated applications will disassociate from the wave but will not be deleted. Click **Delete** to confirm the deletion. # Manage selected waves The **Actions** menu allows you to perform actions on selected waves. **Note** A wave must have **all** of its associated servers in the correct lifecycle for the desired action, otherwise it will be excluded. Use this menu to perform the following actions: + **Launch test instances** – Choose this option to launch test instances for this wave servers. + **Mark as "Ready for cutover"** – Choose this option to finalize testing for this wave after you have completed all the necessary tests in preparation for cutover. Once the **Mark 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**. + **Revert to "ready for testing"** – Choose this option to revert a finalized test for this wave if you want to run additional tests prior to initiating a cutover. The **Revert testing** 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 **Revert**. + **Launch cutover instances** – Choose this option to launch cutover instances for this wave servers after you have finalized all of your testing and are ready to initiate a cutover. + **Finalize cutover** – Choose this option to finalize the cutover for this wave servers after you have successfully performed a cutover. **Note** This action does not uninstall the AWS Replication Agent from the source servers. When you have completed the migration and want to uninstall the agent from your source servers, go to ** Source servers** page and select the relevant servers. Use the **Disconnect from service** option under the **Actions** menu. + **Revert to "ready for cutover"** – Choose this option to revert a finalized cutover for this wave if you encounter any issues or want to reverse the cutover for any reason. + **Start data replication** – Choose this option to start replication of the wave source servers. **Note** This action is applicable if all the wave's associated servers are **Agentless snapshot based** and are in **Discovered** lifecycle state. + **Archive waves** – Choose this option to archive the selected waves. You should only archive waves for which you have already performed a cutover. **Important** A wave can be archived only if all servers that are part of in one of these states: archived, cutover or disconnected. If that is the case, the wave and its associated applications will be archived. The servers that are not yet archived (but can be) will also be archived. + Archived waves will be removed from the main Waves page, but can still be accessed through the selector options. # Filtering migration waves Use filtering to easily filter your waves by one or multiple properties. Click within the **Filter waves** field and choose the filtering property from the **Properties** menu. You can filter by a variety of properties, including: + Wave name – Filter by wave name. + Wave ID – Filter by wave ID. + Migration status – Filter by the migration status (Not started, In progress, Completed). + Alerts – Filter by health status alert (Stalled, Lagging, Healthy). + Number of applications – Filter by a number of applications. + Tags – Filter by tags. Relevant specific tag values will appear under the **Tags** category. Choose the value to filter by. You can filter by multiple properties at once in order to narrow down your results. To clear the selected filtering properties, click **Clear filters** t. # Review migration wave details There are several ways you can access the **Wave details** view. Click the **Wave name** of any wave on the **Waves** page. ![\[Wave management interface showing one active wave with in-progress migration status and healthy alerts.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/wave-1.png) Click the **Wave** of any application on the **Applications** page. ![\[Applications page showing one app with Wave 2 and migration status in progress.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/wave-2.png) Click the **Wave name** in the **Overview** dashboard inside **Application details** of an application. ![\[Overview dashboard showing App 2 details, including Wave name set to "wave 1".\]](http://docs.aws.amazon.com/mgn/latest/ug/images/wave-3.png) The **Wave details** view shows information and options for an individual wave. Here, you can control and monitor the individual wave. ![\[Wave details view showing overview, status, and migration progress for MGN-6583.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/wave-11.png) You can also perform a variety of actions on the wave, and perform batch operations such as launch test and cutover instances for the servers associated with the wave. The **Wave details** view is divided into several dashboards: **Topics** + [Review overall wave status](wave-overview-dashboard.md) + [Applications](wave-applications.md) + [Source servers](wave-source-servers.md) # Review overall wave status The **Overview** dashboard provides an overview of the overall wave status, including: + **Description** – The description of the wave. + **State** – The state of the wave. **State** can be in one of two states: **Active** or **Archived** + **Last status update** – Time stamp of when wave status was updated (update occurs every five minutes). + **Wave start time** – Time stamp of when the earliest replication started for a server associated with this wave. + **Current duration** – Duration of replication time since **Wave start time**. If wave is archived, duration is until the moment the wave was archived. + **Migration status** – The wave migration status. Wave **Migration status** can have one of the following values: + **Not started** – If none of its applications has started replication yet. + **Completed** – If all of its applications completed migration (have been cutover). + **In progress** – At least one of its applications has started replication and not all of its applications completed migration. + **Alerts** – The wave alert. + A wave that has at least one application that is experiencing significant issues, such as a stall, will display a **Stalled** status. + A wave that has at least one application that is experiencing a temporary issue such as lag or backlog will display a **Lagging** status. + A healthy active wave will display a **Healthy** status. + An archived wave will not display a status. # Applications The **Applications** tab shows migration metrics aggregating statuses as well as a list of all the wave associated applications. The application migration metrics show an aggregated overview of the wave's associated servers on two topics: **Alerts** and **Migration status**. **Topics** + [Review alerts on applications in a wave](wave-application-migration-metrics-alerts.md) + [Review the migration status of applications in a wave](wave-application-migration-metrics-migration.md) + [Review all applications associated with a wave](wave-applications-table.md) # Review alerts on applications in a wave The application **Alerts** metric provides an aggregated overview of the alerts related to the wave's associated applications. You can look up an individual application **Alerts** status at the **Applications** table at the bottom of the page. ![\[Pie chart showing 100% healthy status for 2 applications in the Alerts metric.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/wave-8.png) + A healthy application will display a **Healthy** status. + An application that is experiencing a temporary issue such as lag or backlog will display a **Lagging** status. + An application that is experiencing significant issues, such as a stall, will display a **Stalled** status. # Review the migration status of applications in a wave The application **Migration status** metric provides an aggregated overview of the migration status of the wave's associated applications. You can look up an individual application **Migration status** status at the **Applications** table at the bottom of the page. ![\[Pie chart showing migration status: 50% not started, 50% in progress, with 1 application each.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/wave-9.png) Application **Migration status** can have one of the following values: + **Not started** + **In progress** + **Completed** # Review all applications associated with a wave The **Applications** table lists all the applications that are associated with the wave. You can perform batch operations on all the applications via the wave **Actions** menu at the top of the page. You can perform an operation on a single application from its own **Application details** page, by clicking the application's **Application name**. # Source servers The **Source servers** tab shows migration metrics aggregating statuses as well as a list of all the wave's associated applications. The source server migration metrics provide an aggregated overview of the wave's associated servers on three topics: **Alerts**, **Data replication status**, and **Migration status**. **Topics** + [Review alerts on source servers in a wave](wave-source-server-migration-metrics-alerts.md) + [Review data replication status of the servers in a wave](wave-source-server-migration-metrics-drs.md) + [Review the migration lifecycle for the servers in a wave](wave-source-server-migration-metrics-migration.md) + [Review the source servers in a wave](wave-source-servers-table.md) + [Review tags assigned to a wave](wave-cirrus_tags.md) # Review alerts on source servers in a wave The source server **Alerts** metric provides an aggregated overview of the alerts related to the wave's associated servers. You can look up an individual source server **Alerts** status at the **Source servers** table at the bottom of the page. ![\[Pie chart showing server status: 2 healthy servers (66.7%) and 1 launched server (33.3%).\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-7.png) + A healthy server for which a test or cutover instance has not been launched will display a **Healthy** status. + A healthy server for which a test or cutover instance has been launched will display a **Healthy** status. + A server that is experiencing a temporary issue such as a lag or backlog will display a **Lagging** status. + A server that is experiencing significant issues, such as a stall, will display a **Stalled** status. # Review data replication status of the servers in a wave The source server **Data replication status** metric provides an aggregated overview of the data replication status of the wave's associated servers. You can look up an individual source server **Data replication status** status at the **Source servers** table at the bottom of the page. ![\[Pie chart showing data replication status: 66.7% Healthy (2 servers), 33.3% Initial sync (1 server).\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-8.png) Source server's **Data replication status** can have one of the following values: + **Transferring snapshot** + **Initial sync** + **Finalizing sync** + **Lagging** + **Healthy** + **Stalled** + **Rescanning** + **Not started** + **Initiating** + **Creating snapshot** + **Paused** + **Disconnected** # Review the migration lifecycle for the servers in a wave The source server's **Migration lifecycle** metric provides an aggregated overview of the migration lifecycle of the wave's associated servers . You can look up an individual source server's **Migration lifecycle** status at the **Source servers** table at the bottom of the page. ![\[Pie chart showing migration lifecycle status: equal distribution among three server states.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-9.png) The source server's **Migration lifecycle** can have one of the following values: + **Stopped** + **Not ready** + **Ready for testing** + **Test in progress** + **Ready for cutover** + **Cutover in progress** + **Cutover complete** + **Disconnected** + **Discovered** # Review the source servers in a wave The **Source servers** table lists all the servers that are associated with the wave. You can perform batch operations on all the servers via the wave **Actions** menu at the top of the page. You can perform an operation on a single server from its own **Server details** page, by clicking on the server **Source server name**. # Review tags assigned to a wave The **Tags** section shows any tags that have been assigned to the wave. A tag is a label that you assign to an AWS resource. Each tag consists of a key and an optional value. You can use tags to search and filter your resources or track your AWS costs. Learn more about AWS tags in [this Amazon EC2 article](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html).