Modifying an Amazon DocumentDB Instance

You can modify your Amazon DocumentDB instance using either the AWS Management Console or the AWS CLI. To modify an instance, the instance must be in the available state. You cannot modify an instance that is stopped. If the cluster is stopped, first start the cluster, wait for the instance to become available, and then make the desired modifications. For more information, see Stopping and Starting an Amazon DocumentDB Cluster.

Using the AWS Management Console

To modify a specific Amazon DocumentDB instance using the console, complete the following steps.

  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 (Modifying an Instance - 图1) in the upper-left corner of the page.

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

    Modifying an Instance - 图2

  4. Check the box to the left of the instance you wish to modify.

  5. Choose Actions, and then choose Modify.

  6. In the Modify instance: <instance-name> pane, make the changes that you want. You can make the following changes:

    • Instance specifications — The instance identifier and class. Instance identifier naming constraints:

      • Instance identifier — Enter a name that is unique for all instances owned by your AWS account in the current region. The instance identifier must contain [1—63] alphanumeric characters or hyphens, have a letter as the first character, and cannot end with a hyphen or contain two consecutive hyphens.

      • Instance class — From the drop-down menu, select an instance class for your Amazon DocumentDB instance. For more information, see Managing Instance Classes.

    • Certificate authority — Server certificate for this instance. For more information, see Updating Your Amazon DocumentDB TLS Certificates.

    • Failover — During failover, the instance with the highest promotion tier will be promoted to primary. For more information, see Amazon DocumentDB Failover.

    • Maintenance — The maintenance window in which pending modifications or patches are applied to instances in the cluster.

  7. When you have finished, choose Continue to see a summary of your changes.

  8. After verifying your changes, you can apply them immediately or during the next maintenance window under Scheduling of modifications. Choose Modify instance to save your changes. Alternatively, you can choose Cancel to discard your changes.

It takes a few minutes for your changes to be applied. 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 Monitoring an Amazon DocumentDB Instance’s Status.

Using the AWS CLI

To modify a specific Amazon DocumentDB instance using the AWS CLI, use the modify-db-instance with the following parameters. For more information, see ModifyDBInstance. The following code modifies the instance class to db.r5.large for the instance sample-instance.

Parameters

  • --db-instance-identifier — Required. The identifier for the instance to be modified.

  • --db-instance-class — Optional. The new compute and memory capacity of the instance; for example, db.r5.large. Not all instance classes are available in all AWS Regions. If you modify the instance class, an outage occurs during the change. The change is applied during the next maintenance window, unless ApplyImmediately is specified as true for this request.

  • --apply-immediately or --no-apply-immediately — Optional. Specifies whether this modification should be applied immediately or wait until the next maintenance window. If this parameter is omitted, the modification is performed during the next maintenance window.

For Linux, macOS, or Unix:

  1. aws docdb modify-db-instance \
  2.        --db-instance-identifier sample-instance \
  3.        --db-instance-class db.r5.large \
  4.        --apply-immediately

For Windows:

  1. aws docdb modify-db-instance ^
  2.        --db-instance-identifier sample-instance ^
  3.        --db-instance-class db.r5.large ^
  4.        --apply-immediately

Output from this operation looks something like the following.

  1. {
  2.     "DBInstances": [
  3.         {
  4.             "DBInstanceIdentifier": "sample-instance-1",
  5.             "DBInstanceClass": "db.r5.large",
  6.             "Engine": "docdb",
  7.             "DBInstanceStatus": "modifying",
  8.             "Endpoint": {                     
  9.                 "Address": "sample-instance-1.node.us-east-1.docdb.amazonaws.com",
  10.                 "Port": 27017,   
  11.                 "HostedZoneId": "ABCDEFGHIJKLM"
  12.             },
  13.             "InstanceCreateTime": "2020-01-10T22:18:55.921Z",
  14.             "PreferredBackupWindow": "02:00-02:30",
  15.             "BackupRetentionPeriod": 1,
  16.             "VpcSecurityGroups": [
  17.                 {                             
  18.                     "VpcSecurityGroupId": "sg-abcd0123",
  19.                     "Status": "active"
  20.                 }
  21.             ],
  22.             "AvailabilityZone": "us-east-1a",
  23.             "DBSubnetGroup": {
  24.                 "DBSubnetGroupName": "default",
  25.                 "DBSubnetGroupDescription": "default",
  26.                 "VpcId": "vpc-abcd0123",
  27.                 "SubnetGroupStatus": "Complete",
  28.                 "Subnets": [
  29.                     {
  30.                         "SubnetIdentifier": "subnet-abcd0123",
  31.                         "SubnetAvailabilityZone": {
  32.                             "Name": "us-east-1a"
  33.                         },
  34.                         "SubnetStatus": "Active"
  35.                     },
  36.                     {
  37.                         "SubnetIdentifier": "subnet-abcd0123",
  38.                         "SubnetAvailabilityZone": {
  39.                             "Name": "us-east-1b"
  40.                         },
  41.                         "SubnetStatus": "Active"
  42.                     }
  43.                 ]
  44.             },
  45.             "PreferredMaintenanceWindow": "sun:10:57-sun:11:27",
  46.             "PendingModifiedValues": {
  47.                 "DBInstanceClass": "db.r5.large"
  48.             },
  49.             "EngineVersion": "3.6.0",
  50.             "AutoMinorVersionUpgrade": true,
  51.             "PubliclyAccessible": false,
  52.             "DBClusterIdentifier": "sample-cluster",
  53.             "StorageEncrypted": true,
  54.             "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY",
  55.             "DbiResourceId": "db-ABCDEFGHIJKLMNOPQRSTUVWXYZ",
  56.             "CACertificateIdentifier": "rds-ca-2019",
  57.             "PromotionTier": 1,                     
  58.             "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:sample-instance-1",
  59.             "EnabledCloudwatchLogsExports": [
  60.                 "profiler"
  61.             ]
  62.         }
  63.     ]
  64. }

It takes a few minutes for your modifications to be applied. You can use the instance only when its status is available. You can monitor the instance’s status using the AWS Management Console or AWS CLI. For more information, see Monitoring an Amazon DocumentDB Instance’s Status.