Rebooting an Amazon DocumentDB instance
Occasionally, you might need to reboot your Amazon DocumentDB instance, usually for maintenance reasons. If you make certain changes, such as changing the cluster parameter group that is associated with a cluster, you must reboot the instances in the cluster for the changes to take effect. You can reboot a specified instance using the AWS Management Console or the AWS CLI.
Rebooting an instance restarts the database engine service.
Rebooting results in a momentary outage, during which the
instance status is set to rebooting
. An Amazon DocumentDB
event is created when the reboot is completed.
Rebooting an instance doesn't result in a failover. To failover
an Amazon DocumentDB cluster, use the AWS Management Console or the AWS CLI operation
failover-db-cluster
. For more information, see Amazon DocumentDB Failover.
You can't reboot your instance if it isn't in the available state. Your database can be unavailable for several reasons, such as a previously requested modification, or a maintenance-window action. For more information on instance states, see Monitoring an Amazon DocumentDB instance's status.