# Rebooting a replication instance
You can reboot an Amazon DMS replication instance to restart the replication engine. A reboot results in a momentary outage for the replication instance, during which the instance status is set to **Rebooting**. If the Amazon DMS instance is configured for Multi-AZ, the reboot can be conducted with a failover. An Amazon DMS event is created when the reboot is completed.
If your Amazon DMS instance is a Multi-AZ deployment, you can force a planned failover from one Amazon Availability Zone to another when you reboot. When you force a planned failover of your Amazon DMS instance, Amazon DMS closes out active connections on the current instance prior to automatically switching to a standby instance in another Availability Zone. Rebooting with a planned failover helps you simulate a planned failover event of an Amazon DMS instance, such as when scaling the replication instance class.
**Note**
After a reboot forces a failover from one Availability Zone to another, the Availability Zone change might not be reflected for several minutes. This lag appears in the Amazon Web Services Management Console, and in calls to the Amazon CLI and Amazon DMS API.
If migration tasks are running on the replication instance when a reboot occurs, no data loss occurs but the task stops, and the task status changes to an error state.
If the tables in the migration task are in the middle of a bulk load (full load phase) and haven't yet started, they go into an error state. But tables that are complete at that time, remain in a complete state. When a reboot happens during the full load phase, we recommended that you perform either one of the steps below.
+ Remove the tables that are in a complete state from the task, and restart the task with the remaining tables.
+ Create a new task with tables in an error state, and with tables that are pending.
If tables in the migration task are in the ongoing replication phase, the task resumes once the reboot is completed.
You can't reboot your Amazon DMS replication instance if its status is not in the **Available** state. Your Amazon DMS instance can be unavailable for several reasons, such as a previously requested modification or a maintenance-window action. The time required to reboot an Amazon DMS replication instance is typically small (under 5 minutes).
## Rebooting a replication instance using the Amazon console
To reboot a replication instance, use the Amazon console.
**To reboot a replication instance using the Amazon console**
1. Sign in to the Amazon Web Services Management Console and open the Amazon DMS console at [https://console.amazonaws.cn/dms/v2/](https://console.amazonaws.cn/dms/v2/).
1. In the navigation pane, choose **Replication instances**.
1. Choose the replication instance you want to reboot.
1. Choose **Reboot**. The **Reboot replication instance** dialog box opens.
1. Select the check box for **Reboot with planned failover?** if you have configured your replication instance for Multi-AZ deployment and you want to fail over to another Amazon Availability Zone.
1. Choose **Reboot**.
## Rebooting a replication instance using the CLI
To reboot a replication instance, use the Amazon CLI [https://docs.amazonaws.cn/cli/latest/reference/dms/reboot-replication-instance.html](https://docs.amazonaws.cn/cli/latest/reference/dms/reboot-replication-instance.html) command with the following parameter:
+ `--replication-instance-arn`
**Example simple reboot**
The following Amazon CLI example reboots a replication instance.
```
aws dms reboot-replication-instance \
--replication-instance-arn {{arn of my rep instance}}
```
**Example simple reboot with failover**
The following Amazon CLI example reboots a replication instance with failover.
```
aws dms reboot-replication-instance \
--replication-instance-arn {{arn of my rep instance}} \
--force-planned-failover
```
## Rebooting a replication instance using the API
To reboot a replication instance, use the Amazon DMS API [https://docs.amazonaws.cn/AmazonRDS/latest/APIReference/API_ModifyDBInstance.html](https://docs.amazonaws.cn/AmazonRDS/latest/APIReference/API_ModifyDBInstance.html) action with the following parameters:
+ `ReplicationInstanceArn = {{arn of my rep instance}}`
**Example simple reboot**
The following code example reboots a replication instance.
```
1. https://dms.us-west-2.amazonaws.com/
2. ?Action=RebootReplicationInstance
3. &DBInstanceArn={{arn of my rep instance}}
4. &SignatureMethod=HmacSHA256
5. &SignatureVersion=4
6. &Version=2014-09-01
7. &X-Amz-Algorithm=AWS4-HMAC-SHA256
8. &X-Amz-Credential=AKIADQKE4SARGYLE/20140425/us-east-1/dms/aws4_request
9. &X-Amz-Date=20140425T192732Z
10. &X-Amz-SignedHeaders=content-type;host;user-agent;x-amz-content-sha256;x-amz-date
11. &X-Amz-Signature=1dc9dd716f4855e9bdf188c70f1cf9f6251b070b68b81103b59ec70c3e7854b3
```
**Example simple reboot with failover**
The following code example reboots a replication instance and fails over to another Amazon Availability Zone.
```
1. https://dms.us-west-2.amazonaws.com/
2. ?Action=RebootReplicationInstance
3. &DBInstanceArn={{arn of my rep instance}}
4. &ForcePlannedFailover=true
5. &SignatureMethod=HmacSHA256
6. &SignatureVersion=4
7. &Version=2014-09-01
8. &X-Amz-Algorithm=AWS4-HMAC-SHA256
9. &X-Amz-Credential=AKIADQKE4SARGYLE/20140425/us-east-1/dms/aws4_request
10. &X-Amz-Date=20140425T192732Z
11. &X-Amz-SignedHeaders=content-type;host;user-agent;x-amz-content-sha256;x-amz-date
12. &X-Amz-Signature=1dc9dd716f4855e9bdf188c70f1cf9f6251b070b68b81103b59ec70c3e7854b3
```