# View server details with AWS DRS
Server details

To access the server details view, click the **Hostname** of any server on the **Source servers** page. 

![\[Source servers list showing hostname, recovery readiness, and data replication status.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss11-details.png)


You can also access the server details view by checking the box to the left of any single source server on the **Source servers** page and choosing **Actions > View server details**. 

![\[Source servers list with options to view details, edit settings, or initiate recovery job.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss11-details2.png)


The server details view shows information and options for an individual server. Here, you can fully control and monitor the individual server. 

![\[AWS Elastic Disaster Recovery server details showing recovery status and options for a specific server.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss12-details.png)


You can also perform a variety of actions, control replication, and launch Recovery instances for the individual server from the server details view.

The **Overview** box provides a basic overview of the server's status, including the whether the server is ready for recovery, any pending actions, the last recovery result (if any), and a link to the Recovery instance (if one was launched for the server). 

![\[Overview box showing server status: ready for recovery, no pending actions, successful last result.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss12-details-overview.png)


# AWS DRS recovery dashboard
Recovery dashboard

The **Recovery dashboard** tab allows you to monitor the server, its data replication status, and view events and metrics in CloudTrail. 

![\[Recovery dashboard showing last recovery details and data replication status.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss12-details-dashboard.png)


**Topics**
+ [

## Last recovery
](#lifecycle)
+ [

## Data replication status
](#data-replication-stat)
+ [

## Events and metrics
](#events)
+ [

## Server actions and replication control
](#actions)

## Last recovery


The **Last recovery** box provides an overview of the recovery process for the server.

![\[Recovery job details showing start time, job ID, and current status as healthy.\]](http://docs.aws.amazon.com/drs/latest/userguide/images/drs-new-ss12-details-recovery.png)


Here, you can see the following:
+ **Job type** – The type of recovery job performed (drill or recovery)
+ **Job ID** – The ID of the last recovery job. Choose the **Job Id** to be redirected to the **Job** page for that specific recovery launch within the **Recovery job history**. 
+ **Job started** – The date and time the last recovery job was started.
+ **Job finished** – The date and time the last recovery job was finished. This field is blank if the job is still ongoing.
+ **Current recovery instance status** – The current status of the latest Recovery instance (if one has been launched).
+ **Status taken at** – The last date and time the** current recovery instance status** was queried.

## Data replication status


The **Data replication status** section provides an overview of the overall source server status, including:
+ **Replication progress** – The percentage of the server's storage that was successfully replicated.
+ **Rescan progress** – In the event of of a rescan, the percentage of the server's storage that was rescanned.
+ **Total replicated storage** – The total amount of storage replicated (in GiB).
+ **Lag** – Whether the server is experiencing any lag. If it is - the lag time is indicated.
+ **Backlog** – Whether there is any backlog on the server (in MiB)
+ **Elapsed replication time** – Time elapsed since replication first began on the server.
+ **Last seen** – The last time the server successfully connected to AWS Elastic Disaster Recovery.
+ **Replication start time** – The date and time replication first began on the server. 

Data replication can be in one of several states, as indicated in the panel title:
+ **Initial sync**: initial copying of data from external servers is not done. Progress bar and **Total replicated storage** fields indicate how far along the process is.
+ **Healthy**: all data has been copied and any changes at source are continuously being replicated (data is flowing).
+ **Rescan**: an event happened that forced the agent on the external server to rescan all blocks on all replicated disks. This is the same as an initial sync but is faster because only changed blocks need to be copied; a rescan progress bar appears.
+ **Stalled**: data is not flowing and user intervention is required (either initial sync never completes, or the state at the source becomes increasingly different from the state at AWS). When the state is stalled, then the replication initiation checklist is also shown, indicating where the error occurred that caused the stalled state.

This panel also shows:
+ **Total replicated storage:** size of all disks being replicated for this source server, and how much has been copied to AWS (once initial sync is complete)

  **Lag**: if you launch a recovery instance now, how far behind it is from the state at the source. Normally this should be none.

  **Backlog**: how much data has been written at source but has not yet been copied to AWS. Normally this should be none.

  **Last seen**: when is the last time the AWS Replication Agent communicated with the AWS DRS service or the replication server.

If everything is working as it should and replication has finished initializing, the Data replication progress section displays a **Healthy** status.

If there are initialization, replication, or connectivity errors, the **Data replication status** section displays the cause of the issue, for example, a stall. If the error occurred during the initialization process, then the exact step during which the error occurred is marked with a red "x" under **Replication initiation steps**.

## Events and metrics


You can review AWS Elastic Disaster Recovery events and metrics in AWS CloudTrail. Choose **View CloudTrail event history** to open AWS CloudTrail in a new tab. Learn more about AWS CloudTrail events in the [AWS CloudTrail user guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html). 

## Server actions and replication control


You can perform a variety of actions, control data replication, and manage your recovery and drill instances for an individual server from the server details view.

**Topics**
+ [

### Actions menu
](#server-actions)
+ [

### Initiate recovery job menu
](#server-initiate-recovery-menu-2)
+ [

### Alerts and errors
](#server-test-alert2)

### Actions menu


The **Actions** menu allows you to perform the following actions: 
+ **Add servers** – Choosing this option redirects you to the AWS Replication Agent installation instructions.
+ **Edit replication settings** – Choose this option to edit the replication settings for the selected server or group of servers through on the **Edit replication settings** tab. 
+ **Edit launch settings** – Choose this option to enter the source server's **Server details view > Launch settings** tab. 
+ **View server details** – Choose this option to enter the source server's **Server details view**. 
+ **Disconnect from AWS** – Choose this option to disconnect the selected server from AWS Elastic Disaster Recovery and AWS. 

  On the **Disconnect X server/s from service** dialog, choose **Disconnect**. 
**Important**  
This uninstalls the AWS Replication Agent from the source server, and data replication stops for the source server. This action does not affect any drill or recovery instances that have been launched for this source server, but you are no longer able to identify which source servers your Amazon EC2 instances correspond to. 
+ **Delete server** – Choose this option to permanently delete a source server from AWS Elastic Disaster Recovery. This removes all information related to the server from the AWS Elastic Disaster Recovery service. You can only delete servers that have been disconnected from AWS. You need to reinstall the AWS Replication Agent on a deleted source server to add it back to AWS Elastic Disaster Recovery. 

  When the **Delete X servers** dialog appears, click **Permanently delete**. 

### Initiate recovery job menu


The Initiate recovery job menu allows you to start drills and recoveries by launching drill and recovery instances as part of the overall failback process. You can learn more about the entire failback and failover process with AWS Elastic Disaster Recovery in the [Performing a failback and failover with AWS Elastic Disaster Recovery documentation](failback.md). 
+ **Initiate drill** – Choose the **Initiate drill** option to launch a drill instance for this server or group of servers for the purpose of testing your recovery solution. You should perform periodic drills in order to ensure that you are ready for recovery. [Learn more about launching drill instances in AWS Elastic Disaster Recovery.](preparing-failover.md#recovery-drill-overview) 
+ **Initiate recovery** – Choose the **Initiate recovery** option to launch a recovery instances for this server or group of servers for the purpose of recovering the server in the event of a disaster. [Learn more about launching recovery instances in AWS Elastic Disaster Recovery.](failback-preparing-failover.md#failback-launching-instances)

### Alerts and errors


You can distinguish between healthy servers and servers that are experiencing issues on the **Recovery dashboard** in several ways. The AWS Elastic Disaster Recovery console is color-coded for ease of use. 
+ Healthy servers with no errors are characterized by the color blue. The **Data replication status** boxes displays steps and information in blue if the server is healthy.
+ Servers that are experiencing temporary issues are characterized by the color yellow. This can include issues such as lag or a rescan. These issues do not break replication, but may delay replication or indicate a bigger problem. 
+ Servers that are experiencing serious issues are characterized by the color red. These issues can include a loss of connection, a stall, or other issues. You have to fix these issues in order for data replication to resume. 

  The **Data replication status** box includes details of the issue. 

  If the stall occurred during initiation, scroll down to **Replication initiation steps**. The step where the issue arose is marked with a red "x". 

# AWS DRS server info
Server info

The **Server info** tab shows general server information, hardware, and network information:
+ **General information**
  + **Last updated**: when was the data in this tab updated.
  + **Date added**: when was this server added to the service.
  + **AWS ID**: the ID of this source server resource.
  + **arn**: the AWS Resource Name for this source server.
+ **Identification hint**s: under most circumstances, the hostname is the best identifier, as it is what is used throughout the console as the name of the source server. If you need to validate which external server this is referring to in your data center, you can use one of the additional fields: Fully qualified domain name, VMware virtual machine identifier (only if source is VMWare), AWS instance ID (only is source is running on AWS).
+ **Hardware and operating system**: the CPUs, RAM, disks, and network interfaces on the external server, as well as the type and full name of the operating system running on that server. The disks shown are all the disk on the source server, and may include disks not being replicated.
+ **Recommended instance type**: this is the EC2 instance type the service is auto-recommending to use for the launched recovery instance. This is based only on the CPUs and RAM at the source (and not on utilization information). This is the instance type that is launched for this server by default. 

Information shown includes:
+ **Last updated**
+ **Date added**
+ **AWS ID** (if relevant)
+ **Hostname**
+ **Fully qualified domain name**
+ **VMware virtual machine identifier** (if relevant)
+ **AWS instance ID**
+ **AWS ID**
+ **CPUs**
+ **RAM**
+ **Disks**
+ **Network interfaces**
+ **Operating system** information
+ **Recommended instance type**

# Managing tags with AWS DRS
Tags

The Tags section shows any tags that have been assigned to the server. 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). 

**Important**  
**Do not** alter the **Name** tag of resources created by AWS DRS (replication servers, EBS volumes, EBS snapshots, Conversion servers).

Choose **Manage tags** to open **Manage tags** page to add or remove tags. 
+ Choose **Add new tag** to add a new tag. Add a tag **Key** and an optional tag **Value**. Choose **Save** to save your added tags.
+ To remove a tag, choose **Remove** to the right of the tag you want to remove, and then choose **Save**.

# AWS DRS disk settings
Disk settings

The **Disk settings** tab shows a list of all of the disks on the source server and information for each disk:
+ **Disk name**
+ **Staging disk type** – The corresponding Amazon EBS volume disk type that is being used for the disk.
+ **Replicated storage** – The amount of storage that has been replicated from the disk to the Replication Server.
+ **Total storage** – The total storage capacity of the disk.
+  **Status** – shows the status of each disk, values can be either **Normal**, **Normal with marketplace license**, **Error** (with error description). Normal with marketplace license means that the server has at least one marketplace license associated with this volume. Volumes with marketplace licenses pose some limitations on launch: the target region and the selected instance type must support this license. If launching into a different account, the marketplace product must be subscribed to in that account as well or the launch fails. The state is set to Error if there is a problem with the volume, such as not having permissions to read the marketplace license details if the server is owned by a different AWS account. The value can also be empty if the status is not known at this time. 

## Change staging disk type


You can change the EBS volume disk type for each disk or for a group of disks. To change the EBS volume disk type:

1. Select the circle to the left of each disk name and choose **Change staging disk type**.

1. On the **Change staging disk type** dialog, select the type of EBS volume to use for the disk or group of disks.

1. Select the **AUTO** option if your volume's size is greater than 125 GiB and you want AWS Elastic Disaster Recovery to automatically select the most cost-effective EBS volume disk type for each disk based on the disk size and type based on the option you defined in the **Replication settings** (either the default **Lower cost, Throughput Optimized HDD (st1)** option or the **Faster, General Purpose SSD (gp2) or (gp3)** s option).

AWS Elastic Disaster Recovery uses a single Replication Server per 15 source disks. Selecting the **Auto** option ensures that the fewest number of replication servers are used, resulting in increased cost savings.

**Note**  
AWS Elastic Disaster Recovery always uses EBS magnetic volumes for disks that are under 125 GiB in size when you choose the **Auto** option.

If you do not want AWS Elastic Disaster Recovery to automatically select a disk, you can select a disk manually. Select the disk type from the **EBS volume type** menu.

For certain disks, you can configure the amount of IOPS to be allocated per GB of disk space under **IOPS**. You can allocate up to 50 IOPS per GB. 64,000 IOPS are available for Nitro-based instances. Other instances are guaranteed up to 32,000 IOPS. The maximum IOPS per instance is 80,000. 

Choose **Change** to confirm the change.

# AWS DRS replication settings
Replication settings

The **Replication settings** tab allows you to edit the replication settings for an individual source server. After the source server is added to AWS Elastic Disaster Recovery, the replication settings that are defined in the Replication Settings template are automatically applied to the server. You can later edit them for a single source server or multiple source servers through the **Replication settings** tab.

Edit each setting as required and then choose **Save replication settings**.

[Learn more about replication settings.](settings.md) 

# AWS DRS launch settings


The launch settings are a set of instructions that comprise an EC2 launch template and other settings, which determine how a recovery instance is launched for each source server on AWS. 

Launch settings, including the EC2 launch template, are automatically created every time you add a server to AWS Elastic Disaster Recovery. 

The launch settings can be modified at any time, including before the source servers have even completed initial sync.

[Learn more about individual launch settings.](launching-target-servers.md) 

**Important**  
**If the source server’s instance type includes instance store, please consider the following: **   
 It is **not** recommended to change the instance type of an instance to a type that has no ephemeral volumes, or has a different number of ephemeral volumes, as such changes could lead to data inconsistencies and may even cause recovery, drill, or failback to fail. 

# Post-launch settings
Post-launch settings

Post-launch settings allow you to control and automate actions performed after a recovery instance has been launched for the source server in AWS. These settings are created automatically based on the **Default post-launch actions**.

**Activating the post-launch actions for a specific source server**:
+ Navigate to the **Source servers** page and select a source server.
+ Go to the **Post-launch settings** tab. If **Post launch action settings** has **Post launch actions** set to **Active**, click **Edit** for **Post launch action settings**.
+ You will be redirected to the **Edit post-launch settings** screen. Make sure the **Post-launch actions active** option is not checked and click **Save**.

 Alternatively, you can activate and deactivate post-launch actions for multiple servers by navigating to the **Source servers** page, selecting the servers you want to update and clicking **Actions > Edit post-launch action settings**. To activate, make sure the **Post-launch actions active** option is checked, and to deactivate, it should be unchecked. If you made a change, click **Save**. 

**Topics**
+ [

# Adding custom actions with AWS DRS
](post-launch-action-settings-adding-custom-source.md)
+ [

# Activating, deactivating, and editing predefined or custom actions
](post-launch-action-settings-editing-source.md)
+ [

# Deleting custom actions
](post-launch-action-settings-deleting-source.md)
+ [

# Predefined post-launch actions
](predefined-post-launch-actions-source.md)

# Adding custom actions with AWS DRS
Adding custom actions

 AWS Elastic Disaster Recovery (AWS DRS) allows you to run any SSM document that you like – public SSM documents, SSM documents that you created and uploaded to your account or SSM documents that are shared with you. You can configure a custom action to run any SSM document that is available in your account. To be able to create, edit or delete a custom action, make sure the post-launch actions are activated for this source server. Custom actions added to the default settings are automatically added to newly added source servers. 

## Create a custom action


Adding a custom action through source server’s **Post-launch settings**, adds it to this source server. To add a custom action to all newly added source servers, use the **Settings → Default post-launch actions** page. To add a new custom action to the source server, go to **Source server details → Post-launch settings** tab. If the **Post-launch actions** post-launch actions settings is **Active**, you can create new custom actions by clicking on the **Add action** button. 

The **Add action** page includes these parameters:
+ **Action name** – The name of the action in AWS DRS, which should be intuitive, meaningful and unique in this AWS account and region.
+ **Activate this action** – Use this checkbox to activate or deactivate the custom action for this source server. Only active actions run after the launch of a recovery instance.
+ **Mark launch as successful only if this action finishes running successfully** – This checkbox dictates whether or not the launch is marked as successful, based on the successful run of this action. Instance launches progress normally regardless of the success of the action.
+ **System Manager document name** – Select any Systems Manager document that is available to be used in this account.
+ **View in Systems Manager** – Click to open **System Managers** and view additional information about the document.
+ **Description** – Add a description or keep the default.
+ **Document version** – Select which SSM document version to run. AWS DRS can run a default version, the latest version, or a specific version, according to your preferences.
+ **Category** – Select from various available categories including monitoring, validation, security and more.
+ **Order** – Specify the order in which the actions are executed. The lower the number, the earlier the action is executed. Values allowed are between 2 and 10,000. The numbers must be unique but don’t need to be consecutive.
+ **Platform** – Taken from the SSM document and reports which Operating System platform (Windows/Linux) is supported by the action. 
+ **Creator** – Who created the action. For custom actions, the default is always **This account**.

 The **Action parameters** change according to the specific SSM document that is selected. Note that for the instance ID parameter, you can choose to use the launch instance ID, in which case, AWS DRS dynamically populates the value. 

**Note**  
 AWS Elastic Disaster Recovery (AWS DRS) places **AWSElasticDisasterRecoveryRecoveryInstanceWithLaunchActionsRole** instance profile on the launch instance if post-launch actions is active for the source server. If you add an SSM command action that requires additional permissions in the launch instance, you must ensure that the instance profile has the right policies or the right permissions. In order to do so, create a role that has the required permissions as per the policies above or has a policy or policies with those permissions attached to it. Go to **Launch settings** > **EC2 launch template** > **Modify** > **Advance** > **IAM instance profile**. Use an existing profile or create a new one using the **Create new IAM profile** link. 

**Note**  
 Only trusted, authorized users should have access to the parameter store. For enhanced security, ensure that users who do not have permissions to execute SSM documents / commands, do not have access to parameter store. [Learn more about restricting access to Systems Manager parameters](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-access.html). Action parameters are stored in the SSM parameter store as regular strings. Changing parameters in the SSM Parameter store may impact the post launch action run on target instances. We recommend to consider security implications, when choosing to use parameters that contain scripts or sensitive information, such as API keys and database passwords. 

# Activating, deactivating, and editing predefined or custom actions


 You can activate, deactivate and edit actions available for this source server. Activating an action ensures it runs after launching a recovery instance. Likewise, deactivating it, prevents it from being run after launching a recovery instance. The default settings are not affected by activating, deactivating or editing an action for a source server. Editing an action for a source server updates it for that source server. These changes are not reflected on the action, if it exists in the default post-launch actions settings. Changes to actions in the default settings, as to apply to newly added source servers, can be done from the **Settings → Default post-launch actions** page. 

To be able to activate, create, deactivate, edit, or delete a custom action and to activate, deactivate or edit predefined actions for a source server, make sure the post-launch actions are activated for that source server.

## Activating, deactivating and editing predefined or custom actions


 To activate, deactivate or edit a post launch action in the default post-launch actions settings, go to **Source server details** page, and visit the **Post-launch settings** tab. If **Post-launch actions settings** shows **Post-launch actions** to be **Active**, you can edit any action defined for the source server. 

Locate the action you want to edit in the **Actions** card view, or use the search field to filter the actions by name.

Choose the action’s card to select it, and then choose the **Edit** button.

 To activate the action, make sure the **Activate this action setting** is checked and click the **Save** button. To deactivate, make sure the **Activate this action** setting is un-checked and click the **Save** button. 

 The edit page allow you to change the value of some of the parameters for both pre-defined actions and custom actions. Some parameters can only be edited if the action is a custom action. See below for specific information. 

The parameters that appear on the edit page:
+ **Action name** – Editable for custom actions. The name of the action in AWS DRS, which should be intuitive, meaningful and unique in this AWS account and region.
+ **Activate this action** – Use this checkbox to activate or deactivate the action for this source server. Only active actions run after the launch of a recovery instance.
+ **Mark launch as successful only if this action finishes running successfully** – This checkbox dictates whether or not the launch is marked as successful, based on the successful run of this action. Instances launches progress normally regardless of the success of the action.
+ **System Manager document name** – Editable for custom actions. Select any Systems Manager document that is available to be used in this account.
+ **View in Systems Manager** – Click to open **System Managers** and view additional information about the document.
+ **Description** – Editable for custom actions. Add a description or keep the default.
+ **Document version** – Editable for custom actions. Select which SSM document version to run. AWS DRS can run a default version, the latest version, or a specific version, according to your preferences.
+ **Category** – Editable for custom actions. Select from various available categories including monitoring, validation, security and more.
+ **Order** – Specify the order in which the actions run. The lower the number, the earlier the action runs. Values allowed are between 2 and 10,000. The numbers must be unique but don’t need to be consecutive.
+ **Platform** – Not editable. Taken from the SSM document and reports which Operating System platform (Windows/Linux) is supported by the action. 
+ **Creator** – Not editable. Who created the action. For custom actions, the default is always **This account**.

 The **Action parameters** change according to the specific SSM document that is selected. Note that for the instance ID parameter, you can choose to use the launch instance ID, in which case, AWS DRS dynamically populates the value. Some predefined actions, where applicable allow to use a dynamically populated value for the volumes. This value is dynamically populated by AWS DRS with the volumes of the instance being launched. 

After making the required changes, click **Save**, to save the changes and **Cancel** to abort them.

# Deleting custom actions


 Custom actions added to a source server from the default settings on creation or created later for that source server can also be deleted. Deleting a custom action for a source server removes it from that source server and means the action is no longer available to that source server. Deleting the action for a source server does not remove it from the default settings if the action was defined there as well. To delete a custom action from the default settings to avoid adding it to newly added source servers, go to the **Settings → Default post-launch actions** page, and delete the action from there. Pre-defined actions cannot be deleted. If a pre-defined action is not required, it can be deactivated. 

 Locate the action you want to delete in the **Actions** card view, or use the search field to filter the actions by name. Select the action, and click the **Delete** button. To confirm, press **Delete**. 

# Predefined post-launch actions


 AWS Elastic Disaster Recovery allows you to run various predefined post-launch actions on your EC2 launched instance. Use these out-of-the-box actions to improve your launch flexibility. 

These actions can be activated, edited or deactivated for a specific source servers.

[List of available pre-defined actions](https://docs.aws.amazon.com/drs/latest/userguide/predefined-post-launch-actions-default.html)