Rebooting a Multi-AZ DB cluster and reader DB instances - Amazon Relational Database Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Rebooting a Multi-AZ DB cluster and reader DB instances

You might need to reboot your Multi-AZ DB cluster, usually for maintenance reasons. For example, if you make certain modifications or change the DB cluster parameter group associated with a DB cluster, you reboot the DB cluster. Doing so causes the changes to take effect.

If a DB cluster isn't using the latest changes to its associated DB cluster parameter group, the Amazon Web Services Management Console shows the DB cluster parameter group with a status of pending-reboot. The pending-reboot parameter groups status doesn't result in an automatic reboot during the next maintenance window. To apply the latest parameter changes to that DB cluster, manually reboot the DB cluster. For more information about parameter groups, see Working with parameter groups for Multi-AZ DB clusters.

Rebooting a DB cluster restarts the database engine service. Rebooting a DB cluster results in a momentary outage, during which the DB cluster status is set to rebooting.

You can't reboot your DB cluster if it isn't in the Available state. Your database can be unavailable for several reasons, such as an in-progress backup, a previously requested modification, or a maintenance-window action.

The time required to reboot your DB cluster depends on the crash recovery process, the database activity at the time of reboot, and the behavior of your specific DB cluster. To improve the reboot time, we recommend that you reduce database activity as much as possible during the reboot process. Reducing database activity reduces rollback activity for in-transit transactions.


Multi-AZ DB clusters don't support reboot with a failover. When you reboot the writer instance of a Multi-AZ DB cluster, it doesn't affect the reader DB instances in that DB cluster and no failover occurs. When you reboot a reader DB instance, no failover occurs. To fail over a Multi-AZ DB cluster, choose Failover in the console, call the Amazon CLI command failover-db-cluster, or call the API operation FailoverDBCluster.

To reboot a DB cluster
  1. Sign in to the Amazon Web Services Management Console and open the Amazon RDS console at

  2. In the navigation pane, choose Databases, and then choose the Multi-AZ DB cluster that you want to reboot.

  3. For Actions, choose Reboot.

    The Reboot DB cluster page appears.

  4. Choose Reboot to reboot your DB cluster.

    Or choose Cancel.

To reboot a Multi-AZ DB cluster by using the Amazon CLI, call the reboot-db-cluster command.

aws rds reboot-db-cluster --db-cluster-identifier mymultiazdbcluster

To reboot a Multi-AZ DB cluster by using the Amazon RDS API, call the RebootDBCluster operation.