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.

Last updated 18 November 2026View as Markdown

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:StartDBInstance or rds:RebootDBInstance. A missing grant is named under the buttons.
  • The right status: only a stopped database can be started, and only an available one stopped or rebooted. Otherwise the request is refused ("Cannot start a database in status: …" and "Cannot stop …" with 400, "Cannot reboot …" with 409).
  • In the console, also rds:DescribeDBInstances to open the database's page (without it the page is not found).

Stop, start or reboot

  1. Open the database.
  2. In the header, choose Stop, Start or Reboot. Start runs at once.
  3. For Stop and Reboot, in Stop name? or Reboot name?, choose Stop or Reboot to confirm.

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).

Did this page help you?