Encrypting Data in Transit

    Encryption in transit for an Amazon DocumentDB cluster is managed via the TLS parameter in a cluster parameter group. You can manage your Amazon DocumentDB cluster TLS settings using the AWS Management Console or the AWS Command Line Interface (AWS CLI). See the following sections to learn how to verify and modify your current TLS settings.

    Follow these steps to perform management tasks for TLS encryption using the console—such as identifying parameter groups, verifying the TLS value, and making needed modifications.

    Note

    Unless you specify differently when you create a cluster, your cluster is created with the default cluster parameter group. The parameters in the cluster parameter group can’t be modified (for example, tls enabled/disabled). So if your cluster is using a default cluster parameter group, you need to modify the cluster to use a non-default cluster parameter group. First, you might need to create a custom cluster parameter group. For more information, see .

    1. Determine the cluster parameter group that your cluster is using.

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

      3. Note that in the Clusters navigation box, the column Cluster Identifier shows both clusters and instances. Instances are listed underneath clusters. See the screenshot below for reference.

        Encrypting Data in Transit - 图2

      4. Choose the cluster that you’re interested in.

      5. Scroll down to the bottom of Cluster details and locate the Cluster parameter group. Note the name of the cluster parameter group.

        If the name of the cluster’s parameter group is default (for example, default.docdb3.6), you must create a custom cluster parameter group and make it the cluster’s parameter group before you continue. For more information, see the following:

        1. — If you don’t have a custom cluster parameter group that you can use, create one.

        2. Modifying an Amazon DocumentDB Cluster — Modify your cluster to use the custom cluster parameter group.

    2. Determine the current value of the tls cluster parameter.

      1. Open the Amazon DocumentDB console at .

      2. In the navigation pane, choose Parameter groups.

      3. In the list of cluster parameter groups, choose the name of the cluster parameter group you are interested in.

      4. Locate the Cluster parameters section. In the list of cluster parameters, locate the tls cluster parameter row. At this point, the following four columns are important:

        • Cluster parameter name — The name of the cluster parameters. For managing TLS, you’re interested in the tls cluster parameter.

        • Allowed values — A list of values that can be applied to a cluster parameter.

        • Apply type — Either static or dynamic. Changes to static cluster parameters can be applied only when the instances are rebooted. Changes to dynamic cluster parameters can be applied either immediately or when the instances are rebooted.

    3. Modify the value of the tls cluster parameter.

      If the value of tls is not what is needs to be, modify its value for this cluster parameter group. To change the value of the tls cluster parameter, continue from the preceding section by following these steps.

      1. Choose the button to the left of the cluster parameter’s name (tls).

      2. Choose Edit.

      3. To change the value of tls, in the Modify tls dialog box, choose the value that you want for the cluster parameter in the drop-down list.

      4. Choose Modify cluster parameter. The change is applied to each cluster instance when it is rebooted.

    4. Reboot the Amazon DocumentDB instance.

      Reboot each instance of the cluster so that the change is applied to all instances in the cluster.

      1. Open the Amazon DocumentDB console at https://console.aws.amazon.com/docdb.

      2. In the navigation pane, choose Instances.

      3. To specify an instance to reboot, locate the instance in the list of instances, and choose the button to the left of its name.

      4. Choose Actions, and then Reboot. Confirm that you want to reboot by choosing Reboot.

    Follow these steps to perform management tasks for TLS encryption using the AWS CLI—such as identifying parameter groups, verifying the TLS value, and making needed modifications.

    Note

    Unless you specify differently when you create a cluster, the cluster is created with the default cluster parameter group. The parameters in the default cluster parameter group can’t be modified (for example, tls enabled/disabled). So if your cluster is using a default cluster parameter group, you need to modify the cluster to use a non-default cluster parameter group. You might need to first create a custom cluster parameter group. For more information, see .

    1. Determine the cluster parameter group that your cluster is using.

      Use the describe-db-clusters command with the following parameters:

      • --db-cluster-identifier — Required. The name of the cluster of interest.

      • --query — Optional. A query that limits the output to just the fields of interest, in this case, the cluster name and its cluster parameter group name.

      Output from this operation looks something like the following (JSON format).

      1. [
      2.        [
      3.            "docdb-2019-05-07-13-57-08",
      4.            "custom3-6-param-grp"
      5.        ]
      6. ]

      1. Creating Amazon DocumentDB Cluster Parameter Groups — If you don’t have a custom cluster parameter group that you can use, create one.

      2. — Modify your cluster to use the custom cluster parameter group.

    2. Determine the current value of the tls cluster parameter.

      To get more information about this cluster parameter group, use the describe-db-cluster-parameters operation with the following parameters:

      • --db-cluster-parameter-group-name — Required. Use the cluster parameter group name from the output of the previous command.

      • --query — Optional. A query that limits the output to just the fields of interest, in this case, the ParameterName, ParameterValue, AllowedValues, and ApplyType.

      Output from this operation looks something like the following (JSON format).

      1. [
      2.     [
      3.         "audit_logs",
      4.         "disabled",
      5.         "enabled,disabled",
      6.         "dynamic"
      7.     ],
      8.     [
      9.         "tls",
      10.         "disabled",
      11.         "static"
      12.     ],
      13.     [
      14.         "ttl_monitor",
      15.         "enabled",
      16.         "disabled,enabled",
      18.     ]
      19. ]

    3. Modify the value of the tls cluster parameter.

      If the value of tls is not what it needs to be, modify its value for this cluster parameter group. To change the value of the tls cluster parameter, use the modify-db-cluster-parameter-group operation with the following parameters.

      • --db-cluster-parameter-group-name — Required. The name of the cluster parameter group to modify. This cannot be a default.* cluster parameter group.

      • --parameters — Required. A list of the cluster parameter group’s parameters to modify.

        • ParameterName — Required. The name of the cluster parameter to modify.

        • ParameterValue — Required. The new value for this cluster parameter. Must be one of the cluster parameter’s AllowedValues.

          • enabled — The cluster only accepts secure connections using TLS.

          • disabled — The cluster does not accept secure connections using TLS.

        • ApplyMethod — When this modification is to be applied. For static cluster parameters like tle, this value must be pending-reboot.

          • pending-reboot — Change is applied to an instance only after it is rebooted. You must reboot each cluster instance individually for this change to take place across all of the cluster’s instances.

    1. Reboot your Amazon DocumentDB instance.

      Reboot each instance of the cluster so that the change is applied to all instances in the cluster. To reboot an Amazon DocumentDB instance, use the reboot-db-instance operation with the following parameter:

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

      The following code reboots the instance sample-db-instance.

      For Linux, macOS, or Unix:

      1. aws docdb reboot-db-instance \
      2.        --db-instance-identifier sample-db-instance

      For Windows:

      Output from this operation looks something like the following (JSON format).

      1. {
      2.     "DBInstance": {
      3.         "AutoMinorVersionUpgrade": true,
      4.         "PubliclyAccessible": false,
      5.         "PreferredMaintenanceWindow": "fri:09:32-fri:10:02",
      6.         "PendingModifiedValues": {},
      7.         "DBInstanceStatus": "rebooting",
      8.         "DBSubnetGroup": {
      9.             "Subnets": [
      10.                 {
      11.                     "SubnetStatus": "Active",
      12.                     "SubnetAvailabilityZone": {
      13.                         "Name": "us-east-1a"
      14.                     },
      15.                     "SubnetIdentifier": "subnet-4e26d263"
      16.                 },
      17.                 {
      18.                     "SubnetStatus": "Active",
      19.                     "SubnetAvailabilityZone": {
      20.                         "Name": "us-east-1c"
      21.                     },
      22.                     "SubnetIdentifier": "subnet-afc329f4"
      23.                 },
      24.                 {
      25.                     "SubnetStatus": "Active",
      26.                     "SubnetAvailabilityZone": {
      27.                         "Name": "us-east-1e"
      28.                     },
      29.                     "SubnetIdentifier": "subnet-b3806e8f"
      31.                     "SubnetStatus": "Active",
      32.                     "SubnetAvailabilityZone": {
      33.                         "Name": "us-east-1d"
      34.                     },
      35.                     "SubnetIdentifier": "subnet-53ab3636"
      36.                 },
      37.                 {
      38.                     "SubnetStatus": "Active",
      39.                     "SubnetAvailabilityZone": {
      40.                         "Name": "us-east-1b"
      41.                     },
      42.                     "SubnetIdentifier": "subnet-991cb8d0"
      43.                 },
      44.                 {
      45.                     "SubnetStatus": "Active",
      46.                     "SubnetAvailabilityZone": {
      47.                         "Name": "us-east-1f"
      48.                     },
      49.                     "SubnetIdentifier": "subnet-29ab1025"
      50.                 }
      51.             ],
      52.             "SubnetGroupStatus": "Complete",
      53.             "DBSubnetGroupDescription": "default",
      54.             "VpcId": "vpc-91280df6",
      55.             "DBSubnetGroupName": "default"
      56.         },
      57.         "PromotionTier": 2,
      58.         "DBInstanceClass": "db.r5.4xlarge",
      59.         "InstanceCreateTime": "2018-11-05T23:10:49.905Z",
      60.         "PreferredBackupWindow": "00:00-00:30",
      61.         "KmsKeyId": "arn:aws:kms:us-east-1:012345678901:key/0961325d-a50b-44d4-b6a0-a177d5ff730b",
      62.         "StorageEncrypted": true,
      63.         "VpcSecurityGroups": [
      64.             {
      65.                 "Status": "active",
      66.                 "VpcSecurityGroupId": "sg-77186e0d"
      67.             }
      68.         ],
      69.         "EngineVersion": "3.6.0",
      70.         "DbiResourceId": "db-SAMPLERESOURCEID",
      71.         "DBInstanceIdentifier": "sample-cluster-instance-00",
      72.         "Engine": "docdb",
      73.         "AvailabilityZone": "us-east-1a",
      74.         "DBInstanceArn": "arn:aws:rds:us-east-1:012345678901:db:sample-cluster-instance-00",
      75.         "BackupRetentionPeriod": 1,
      76.         "Endpoint": {
      77.             "Address": "sample-cluster-instance-00.corcjozrlsfc.us-east-1.docdb.amazonaws.com",
      78.             "Port": 27017,
      79.             "HostedZoneId": "Z2R2ITUGPM61AM"
      80.         },
      81.         "DBClusterIdentifier": "sample-cluster"