Rebooting an Amazon DocumentDB Instance

    Rebooting an instance restarts the database engine service. Rebooting results in a momentary outage, during which the instance status is set to . 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 . 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 .

    The following procedure reboots an instance that you specify using the console.

    1. Sign in to the AWS Management Console, and open the Amazon DocumentDB console at https://console.aws.amazon.com/docdb.

    2. In the Clusters navigation box, you’ll see the column Cluster Identifier. Your instances are listed under clusters, similar to the screenshot below.

    It takes a few minutes for your instance to reboot. You can use the instance only when its status is available. You can monitor the instance’s status using the console or the AWS CLI. For more information, see .

    Rebooting an Instance Using the AWS CLI

    To reboot an Amazon DocumentDB instance, use the operation with the parameter. This parameter specifies the identifier for the instance to be rebooted.

    The following code reboots the instance .

    For Linux, macOS, or Unix:

    For Windows:

    It takes a few minutes for your instance to reboot. You can use the instance only when its status is available. You can monitor the instance’s status using the console or AWS CLI. For more information, see .