You may need to reboot a DB instance for maintenance purposes. For example, if the status of a DB instance is Abnormal, you can try rebooting it to restore its status to Available. After modifying some parameters, you must reboot the DB instance for the modifications to take effect. You can reboot a primary DB instance or a read replica on the management console.
For primary/standby DB instances, rebooting the primary DB instance will automatically cause the standby DB instance to also be rebooted.
DB instances can be rebooted only when they are in the abnormal or available state. DB instances cannot be rebooted when backups or read replicas are being created for them.
The time required for rebooting a DB instance depends on the crash recovery process of the DB engine. To shorten the reboot time, you are advised to reduce database activities during the reboot to reduce rollback activities of transit transactions.
Rebooting DB instances will reboot database services. Rebooting a DB instance will cause service interruption. During this period, the DB instance status is Rebooting.
For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.