Stop, start or reboot a database
Stop a database you do not need, start it again, or reboot it; a cluster reboots one machine at a time.
Replace ewdb-0123456789ab with your database's id.
Important
A stopped database is still billed: every started hour of every node counts, stopped ones included.
Prerequisites
- Permission for
rds:StopDBInstance,rds:StartDBInstanceorrds:RebootDBInstance. A missing grant is named under the buttons. - The right status: only a
stoppeddatabase can be started, and only anavailableone stopped or rebooted. Otherwise the request is refused ("Cannot start a database in status: …" and "Cannot stop …" with400, "Cannot reboot …" with409). - In the console, also
rds:DescribeDBInstancesto open the database's page (without it the page is not found).
Stop, start or reboot
- Open the database.
- In the header, choose Stop, Start or Reboot. Start runs at once.
- For Stop and Reboot, in Stop name? or Reboot name?, choose Stop or Reboot to confirm.
dcloud rds instances stop ewdb-0123456789ab
dcloud rds instances start ewdb-0123456789ab
dcloud rds instances reboot ewdb-0123456789abPATCH /rds/api/instances/ewdb-0123456789ab
{ "action": "reboot" }"stop" and "start" work the same way.
Not available in Terraform. Power state is an action, not configuration.
Result
The status moves through stopping → stopped or starting → available. A stop shuts the
machines down cleanly; storage, backups and the master password are kept.
Reboot on a cluster restarts one machine at a time: the replicas first, each streaming again
before the next, then a switchover, then the old leader. The database stays available; clients
see one switchover (a few seconds). Progress is on Activity (phase reboot).
Reboot on a single node starts at once: the database is rebooting and unavailable until its
machine is back and PostgreSQL answers again, then available.
A reboot also loads a library an extension waits for (see Enable an extension) and applies parameters that take effect at the next restart (see Tune parameters).