# How to reboot an RDS instance

How-to guides · Updated 17 November 2026

**Short answer:** In the RDS console select the database, then Actions, Reboot. From the CLI run aws rds reboot-db-instance --db-instance-identifier my-db, adding --force-failover on a Multi-AZ instance to switch to the standby. The database is unavailable while it restarts, typically for a few minutes, and the instance must be in the available state first.

## Why reboot (and why not)

The usual good reasons are applying a static parameter group change (the parameter shows `pending-reboot`), recovering an engine that has stopped responding, or testing a Multi-AZ failover. A reboot does not fix storage that is full, too many connections from a misbehaving client, or slow queries; those come straight back. See [too many connections](https://cloudconsole.dev/errors/rds-too-many-connections) and [storage full](https://cloudconsole.dev/errors/rds-storage-full) first.

## Console and CLI

**Console:** open the Amazon RDS console, choose **Databases**, select the DB instance (for Aurora, a specific writer or reader instance), choose **Actions** > **Reboot**. For Multi-AZ instances you can tick the option to reboot with failover.

**CLI:**

```
# Plain reboot
aws rds reboot-db-instance --db-instance-identifier my-db

# Multi-AZ instance: restart by failing over to the standby
aws rds reboot-db-instance --db-instance-identifier my-db --force-failover

# Wait until it is available again
aws rds wait db-instance-available --db-instance-identifier my-db

# What happened, in RDS's own words (last 60 minutes)
aws rds describe-events --source-type db-instance \
  --source-identifier my-db --duration 60 \
  --query 'Events[].[Date,Message]' --output text
```

## Aurora and Multi-AZ DB clusters

| Deployment | How to reboot |
|---|---|
| Single-AZ or Multi-AZ DB *instance* | `reboot-db-instance` (optionally with `--force-failover`) |
| Aurora cluster | Reboot each instance with `reboot-db-instance`. To move the writer role, use [a cluster failover](https://cloudconsole.dev/how-to/failover-rds-aurora-cluster) instead. |
| Multi-AZ DB *cluster* (non-Aurora, one writer and two readers) | `aws rds reboot-db-cluster --db-cluster-identifier my-cluster` |

For Aurora, rebooting readers one at a time keeps reads available. Rebooting the writer interrupts writes for the duration.

## How long it takes, and what to check

- **Duration:** mostly crash-recovery time. An idle database comes back in a minute or two; one with a lot of uncommitted work or a large buffer pool can take longer.
- **Before:** check the status is `available`; a reboot is refused while the instance is modifying or backing up. Check whether other modifications are pending with `describe-db-instances --query 'DBInstances[0].PendingModifiedValues'`; a reboot doesn't apply those, only pending parameter changes.
- **Before a failover reboot:** make sure applications reconnect on errors and don't cache DNS indefinitely, because the endpoint's DNS changes to the new primary.
- **After:** confirm parameter groups show `in-sync`, connection counts recover, and the RDS event log shows the reboot completed.

## Common mistakes

- Rebooting production in business hours to apply a parameter that could wait for the maintenance window.
- Expecting `--force-failover` on a Single-AZ instance; it only applies to Multi-AZ.
- Rebooting repeatedly when the engine is hung on storage: check `FreeStorageSpace` before trying again.
- Rebooting a read replica to "clear" replica lag; lag comes from write volume or long transactions on the source, which a reboot doesn't change.
- Forgetting the application: connection pools that don't validate connections can keep failing after the database is back, until the app is restarted.

## Questions

### How long does it take to reboot an RDS instance?

Usually a few minutes, most of which is database crash recovery. A failover reboot on Multi-AZ is often faster from the client's point of view, because the standby is already running.

### Does rebooting RDS cause downtime?

Yes. The instance is unavailable while it restarts. With Multi-AZ and --force-failover the interruption is shorter, but connections still drop.

### How do I reboot an RDS cluster?

For Aurora, reboot the individual instances. For a non-Aurora Multi-AZ DB cluster, use aws rds reboot-db-cluster.

## When this happens away from your desk

A database that needs a kick rarely waits for office hours. CloudConsole, a phone app for AWS, is built to show RDS status, events and alarms on your phone, with guardrails around production changes.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Rebooting a DB instance](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RebootInstance.html)
- [RebootDBInstance API reference](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RebootDBInstance.html)

## Related

- [aws rds reboot-db-instance](https://cloudconsole.dev/cli/rds-reboot-db-instance)
- [aws rds describe-db-instances](https://cloudconsole.dev/cli/rds-describe-db-instances)
- [How to fail over an Aurora cluster](https://cloudconsole.dev/how-to/failover-rds-aurora-cluster)
- [RDS instance in incompatible-parameters state](https://cloudconsole.dev/errors/rds-incompatible-parameters)
- [CloudWatch alarm: Aurora EngineUptime (writer)](https://cloudconsole.dev/alarms/rds-engineuptime)
- [Too many connections on RDS (MySQL / PostgreSQL)](https://cloudconsole.dev/errors/rds-too-many-connections)
- [How to kill a running query on Amazon RDS](https://cloudconsole.dev/how-to/kill-query-rds)

---

Source: https://cloudconsole.dev/how-to/reboot-rds-instance

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
