Rebooting a DB instance in a DB cluster - Amazon Aurora

Rebooting a DB instance in a DB cluster

You might need to reboot your DB instance, usually for maintenance reasons. For example, if you make certain modifications, or if you change the DB parameter group associated with the DB instance or its DB cluster, you must reboot the instance for the changes to take effect.


If a DB instance isn't using the latest changes to its associated DB parameter group, the AWS Management Console shows the DB 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 instance, manually reboot the DB instance. For more information about parameter groups, see Working with DB parameter groups and DB cluster parameter groups.

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

You can't reboot your DB instance if it is not 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.


When you reboot the primary instance of an Amazon Aurora DB cluster, RDS also automatically restarts all of the Aurora Replicas in that DB cluster. When you reboot the primary instance of an Aurora DB cluster, no failover occurs. When you reboot an Aurora Replica, no failover occurs. To fail over an Aurora DB cluster, call the AWS CLI command failover-db-cluster, or the API operation FailoverDBCluster.

The time required to reboot your DB instance depends on the crash recovery process, database activity at the time of reboot, and the behavior of your specific DB engine. 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.

For a DB instance with read replicas, you can reboot the source DB instance and its read replicas independently. After a reboot completes, replication resumes automatically.

To reboot a DB instance

  1. Sign in to the AWS Management Console and open the Amazon RDS console at

  2. In the navigation pane, choose Databases, and then choose the DB instance that you want to reboot.

  3. For Actions, choose Reboot.

    The Reboot DB Instance page appears.

  4. Choose Reboot to reboot your DB instance.

    Alternatively, choose Cancel.

To reboot a DB instance by using the AWS CLI, call the reboot-db-instance command.

Example Simple reboot

For Linux, macOS, or Unix:

aws rds reboot-db-instance \ --db-instance-identifier mydbinstance

For Windows:

aws rds reboot-db-instance ^ --db-instance-identifier mydbinstance

To reboot a DB instance by using the Amazon RDS API, call the RebootDBInstance operation.