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*. # Associate a Group of Servers with an Application Many customers have clusters of servers with dependencies between them. AWS Application Migration Service provides the user with a way to represent a group of servers by associating them with an **Application**. You can monitor the migration status and progress of an application and its associated servers. You can also perform operation on the application, such as edit, tagging, archive, as well as bulk operations on the servers associated with the application. **Topics** + [ # Manage applications ](applications-list.md) + [ # Access details for an application ](application-details.md) # Manage applications The **Applications** page lists all the applications that have been added to AWS Application Migration Service. The **Applications** page allows you to manage your applications and perform a variety of commands for one or more applications (such as controlling replication and launching test and cutover instances). ## Interacting with the Applications page The **Applications** page shows a list of applications. Each row on the list represents a single application. The **Applications** page provides key information for each application 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 applications. When an application is selected, you can interact with the application through the **Actions** menu, **Edit**, and **Delete** buttons. Selected applications are highlighted. + **Application name** – This column shows the unique application name for each application. + **Wave name** – This column shows the name of the wave the application is associated with. An application cannot be associated with more than one wave at a time. This column is hidden by default. + **Migration status** – This column shows the migration status for each application. + **Not started** – None of the application associated servers has started replication yet. + **In progress** – At least one of the application associated servers has started replication and not all of its servers completed migration. + **Completed** – All the application associated servers completed migration (have been cut over). + **Alerts** – This column shows whether any alerts exist for the application. + **Stalled** – An application that has at least one server that is experiencing significant issues, such as a stall,. + **Lagging** – An application that has at least one server that is experiencing a temporary issue such as lag or backlog. + **Healthy** – A healthy active application. Archived applications do not display any alerts. + **Number of servers** – This column shows the total number of servers associated with each application. **Topics** + [ ## Interacting with the Applications page ](#applications-list-interacting) + [ # Add application ](add-application.md) + [ # Edit application ](edit-application.md) + [ # Delete application ](delete-application.md) + [ # Manage applications ](application-actions-menu.md) + [ # Filtering the Applications page ](applications-filtering.md) # Add application To add an application, click **Add application**. When the **Add application** prompt opens, configure the application name, add a description (optional), associate source servers (optional), and add tags (optional). + **Application name** – Application name is mandatory, with a limit of 256 characters. The name must be unique per account per region. Uniqueness verification for application name in Migration Application Service is case-insensitive. + **Description** – Application description is optional, with a limit of 600 characters. + **Servers** – You can add up to 200 servers to an application. Checking a server in the drop-down list will associate it with the application. + **Tags** – You can add up to 50 tags to an application. When you are done configuring your application settings, click **Add application** to create the application. # Edit application To edit an application, click **Edit**. When the **Edit application** prompt opens, edit the application name, description, and tags, as well as associate or disassociate source servers. + **Application name** – Application name is mandatory, with a limit of up to 256 characters. The name must be unique per account per region. Uniqueness verification for application name in Migration Application Service is case-insensitive. + **Description** – Application description is optional, with a limit of 600 characters. + **Servers** – You can add up to 200 servers to an application. Checking a server in the dropdown list will associate it with the application. Unchecking an associated server will disassociate it from the application. + **Tags** – You can add up to 50 tags to an application. To finalize your changes, click **Save changes**. # Delete application To delete an application, click **Delete**. When the **Delete application** prompt opens, verify that you want to delete the selected application. Deleting the application will disassociate the servers from the application, but will not delete them. Click **Delete** to confirm the deletion. # Manage applications The **Actions** menu allows you to perform actions on selected applications. **Note** An application must have **all** of its associated servers in the correct lifecycle for the desired action, otherwise it will be excluded. The **Actions** menu allows you to perform the following actions: + **Launch test instances** – Choose this option to launch test instances for this application servers. + **Mark as "Ready for cutover"** – Choose this option to finalize testing for this application after you have completed all the necessary tests in preparation for cutover. 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 application if you want to run further 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 application 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 application 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 application if you encounter any issues or want to reverse the cutover for any reason. + **Start data replication** – Choose this option to start replicating the application source servers. **Note** This action is applicable if all the application associated servers are **Agentless snapshot based ** and are in **Discovered** lifecycle state. + **Add applications to wave** – Choose this option to associate the selected applications to a wave. + **Archive applications** – Choose this option to archive the selected applications. You should only archive applications for which you have already performed a cutover. **Important** An application can be archived only if all servers that compose it are in one of these states: archived, cutover, or disconnected. If that is the case, the application will be archived and the servers that are not yet archived (but can be) will also be archived. Archived applications will be removed from the main applications page, but can still be accessed through the selector options. # Filtering the Applications page You can customize the **Applications** page through filtering. Filtering allows you to easily filter your applications by one or multiple properties. Click within the **Filter applications** field and choose the filtering property from the **Properties** menu. You can filter by a variety of properties, including: + Application name – Filter by application name. + Application ID – Filter by application ID. + Wave name – Filter by wave name. + Migration status – Filter by the migration status (Not started, In progress, Completed). + Alerts – Filter by health status alert (Stalled, Lagging, Healthy). + Number of servers – Filter by a number of servers. + Tags - Filter by tags. Relevant specific tag values will appear under the **Tags ** category. Choose the value by which to filter. You can filter by multiple properties at once in order to narrow down your results. To clear the selected filtering properties, click **Clear filters**. # Access details for an application There are several ways you can access the **Application details** view. Click on the **Application name** of any application on the **Applications** page. ![\[Applications page showing one active application named "App 3" with migration status and health indicators.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-1.png) Click on the **Application** of any server on the **Source servers** page. ![\[Source servers page showing one server with application "arch-app" ready for cutover.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-2.png) Click on the **Application name** in the **Server info** tab. ![\[Server info tab showing Application name field with "App 3" value highlighted.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-3.png) Click on the **Application name** of any application in the **Applications** table inside **Wave details** -> **Applications** tab. ![\[Dashboard showing application status with alerts, migration progress, and details for App 3.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-4.png) The **Application details** view shows information and options for an individual application. Here, you can control and monitor the individual application. ![\[Application details view showing overview, alerts, data replication, and migration lifecycle status.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-5.png) You can also perform a variety of actions on the application, and perform batch operations such as launch Test and Cutover instances for the servers associated with the application. The **Application details** view is divided into several dashboards: **Topics** + [ # Review overall application status ](application-overview-dashboard.md) + [ # Source server migration metrics ](application-source-server-migration-metrics.md) + [ # Review application source servers ](application-source-servers-table.md) + [ # Review application tags ](application-cirrus_tags.md) # Review overall application status The **Overview** dashboard provides an overview of the overall application status, including: + **Description** – The description of the application. + **State** – The state of the application. **State** can be in one of two states: **Active** or **Archived**. + **Last status update** – Time stamp of when application status was updated (update occurs every five minutes). + **Wave name** – Name of the wave that the application is associated with. + **Migration status** – The application migration status. Application **Migration status** can have one of the following values: **Not started** – If none of its servers has started replication yet. **Completed** – If all of its servers completed migration (have been cutover). **In progress** – At least one of its servers has started replication and not all of its servers completed migration. + **Alerts** – The application alert. An application that has at least one server that is experiencing significant issues, such as a stall, will display a **Stalled** status. An application that has at least one server that is experiencing a temporary issue such as lag or backlog will display a **Lagging** status. A healthy active application will display a **Healthy** status. An archived application will not display a status. # Source server migration metrics The source server migration metrics show an aggregated overview of the application associated servers on three topics: **Alerts**, **Data replication status** and **Migration status**. # Review source server alerts The source server **Alerts** migration metric presents an aggregated overview of the application associated servers alerts. 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 of cutover instance has been launched will display a **Healthy** status. + A server that is experiencing a temporary issue such as 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 source server data replication status The source server **Data replication status** migration metric presents an aggregated overview of the application associated servers data replication status. 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, 33.3% initial sync.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-8.png) Source server **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 application source server migration lifecycle The source server **Migration lifecycle** metric shows an aggregated overview of the application associated servers migration lifecycle. You can look up an individual source server **Migration lifecycle** status at the **Source servers** table at the bottom of the page. ![\[Pie chart showing migration lifecycle status: 33.3% each for Ready for cutover, Ready for test, and Not ready.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-9.png) Source server **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 application source servers The **Source servers** table lists all the servers that are associated with the application. To perform batch operations on all the servers, use the application **Actions** menu at the top of the page. To perform an operation on a single server, go to the specific server's **Server details** page by clicking the server **Source server name**. # Review application tags The **Tags** section shows any tags that have been assigned to the application. 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)