Menu
Amazon Relational Database Service
User Guide (API Version 2014-10-31)

Rebooting a DB Instance

In some cases, if you modify a DB instance, change the DB parameter group associated with the instance, or change a static DB parameter in a parameter group the instances uses, you must reboot the instance for the changes to take effect.

Rebooting a DB instance restarts the database engine service. A reboot also applies to the DB instance any modifications to the associated DB parameter group that were pending. Rebooting a DB instance results in a momentary outage of the instance, during which the DB instance status is set to rebooting. If the Amazon RDS instance is configured for MultiAZ, the reboot is possibly conducted through a failover. An Amazon RDS event is created when the reboot is completed.

If your DB instance is a Multi-AZ deployment, you can force a failover from one availability zone to another when you select the Reboot option. When you force a failover of your DB instance, Amazon RDS automatically switches to a standby replica in another Availability Zone and updates the DNS record for the DB instance to point to the standby DB instance. As a result, you will need to clean up and re-establish any existing connections to your DB instance. Reboot with failover is beneficial when you want to simulate a failure of a DB instance for testing, or restore operations to the original AZ after a failover occurs. For more information, see High Availability (Multi-AZ). Note that when you reboot an Amazon Aurora DB cluster, it will failover to the standby replica; rebooting an Amazon Aurora Replica does not initiate a failover.

The time required to reboot is a function of the specific database engine's crash recovery process. To improve the reboot time, we recommend that you reduce database activities as much as possible during the reboot process to reduce rollback activity for in-transit transactions.

In the console, the Reboot option may be disabled if the DB instance is not in the "Available" state. This can be due to several reasons, such as an in-progress backup or a customer-requested modification or a maintenance-window action.

Note

Rebooting the primary instance of an Amazon Aurora DB cluster also automatically reboots the Aurora Replicas for that DB cluster.

AWS Management Console

To reboot a DB instance

  1. Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/.

  2. In the navigation pane, click Instances.

  3. Select the check box of the DB instance that you want to reboot.

  4. Select Instance Actions and then select Reboot from the drop down menu.

  5. To force a failover from one AZ to another, select the Reboot with failover? check box in the Reboot DB Instance dialog box.

  6. Click Yes, Reboot. To cancel the reboot instead, click Cancel.

CLI

To reboot a DB instance, use the AWS CLI command reboot-db-instance. To force a failover from one AZ to the other, use the --force-failover parameter.

For Linux, OS X, or Unix:

Copy
aws rds reboot-db-instance \ --db-instance-identifier dbInstanceID \ --force-failover

For Windows:

Copy
aws rds reboot-db-instance ^ --db-instance-identifier dbInstanceID ^ --force-failover

API

To reboot a DB instance, call the Amazon RDS API function RebootDBInstance with the following parameters:

  • DBInstanceIdentifier=mydbinstance

  • ForceFailover=true

Copy
https://rds.amazonaws.com/ ?Action=RebootDBInstance &DBInstanceIdentifier=mydbinstance &ForceFailover=true &Version=2012-01-15 &SignatureVersion=2 &SignatureMethod=HmacSHA256 &Timestamp=2012-01-20T22%3A06%3A23.624Z &AWSAccessKeyId=<AWS Access Key ID> &Signature=<Signature>