Determining Pending Maintenance

You can determine whether you have the latest Amazon DocumentDB engine version by determining whether you have pending cluster maintenance.

Using the AWS Management Console

You can use the AWS Management Console to determine whether a cluster has pending maintenance.

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

  2. In the navigation pane, choose Clusters.

    Tip

    If you don’t see the navigation pane on the left side of your screen, choose the menu icon (Determining Pending Maintenance - 图1) in the upper-left corner of the page.

  3. Locate the Maintenance column to determine whether a cluster has pending maintenance.

    ![

    1.                     Console screenshot showing Amazon DocumentDB cluster 
    2.                        maintenance field.
    3.                  ](/projects/DocumentDB-20201111-en/cb1463dd30b9f4070da1180777096969.png)

    None indicates that the cluster is running the latest engine version. Available indicates that the cluster has pending maintenance, which might mean that an engine upgrade is needed.

  4. If your cluster has pending maintenance, continue with the steps at Upgrading a Cluster’s Engine Version.

Using the AWS CLI

You can use the AWS CLI to determine whether a cluster has the latest engine version by using the describe-pending-maintenance-actions operation with the following parameters.

Parameters

  • --resource-identifier—Optional. The ARN for the resource (cluster). If this parameter is omitted, pending maintenance actions for all clusters are listed.

  • --region—Optional. The AWS Region that you want to run this operation in, for example, us-east-1.

For Linux, macOS, or Unix:

  1. aws docdb describe-pending-maintenance-actions \
  2.    --resource-identifier arn:aws:rds:us-east-1:123456789012:cluster:sample-cluster \
  3.    --region us-east-1

For Windows:

  1. aws docdb describe-pending-maintenance-actions ^
  2.    --resource-identifier arn:aws:rds:us-east-1:123456789012:cluster:sample-cluster ^
  3.    --region us-east-1

Output from this operation looks something like the following.

  1. {
  2.     "PendingMaintenanceActions": [
  3.         {
  4.             "ResourceIdentifier": "arn:aws:rds:us-east-1:123456789012:cluster:sample-cluster",
  5.             "PendingMaintenanceActionDetails": [
  6.                 {
  7.                     "Description": "New feature",
  8.                     "Action": "db-upgrade",
  9.                     "ForcedApplyDate": "2019-02-25T21:46:00Z",
  10.                     "AutoAppliedAfterDate": "2019-02-25T07:41:00Z",
  11.                     "CurrentApplyDate": "2019-02-25T07:41:00Z"
  12.                 }
  13.             ]
  14.         }
  15.     ]
  16. }

If your cluster has pending maintenance, continue with the steps at Upgrading a Cluster’s Engine Version.