AWS Security ChangesHomeSearch

AWS guardduty: GuardDuty RDS Protection: add RDS data activity monitoring config

Service: guardduty · 2026-10-09 · Documentation medium

File: guardduty/latest/ug/configure-rds-pro-multi-account.md · Type: logging

Summary

Expands the multi-account RDS Protection guide to document the new RDS data activity monitoring additional configuration (RDS_DATA_RISK), including updated console steps, ordering notes, and AWS CLI examples for enabling, auto-enabling, and selectively toggling RDS login and data activity monitoring across delegated administrator, member, and new organization accounts.

Security assessment

The diff documents how to enable/auto-enable GuardDuty's RDS data activity monitoring (RDS_DATA_RISK) alongside RDS login activity monitoring, a threat-detection/monitoring capability with security impact. It is security documentation for a detection feature, but no specific vulnerability, incident, or CVE is referenced, so it is not security_issue_related.

Evidence

+Run the [updateDetector](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateDetector.html) API operation using your own regional detector ID and passing the `features` object `name` as `RDS_LOGIN_EVENTS` and `status` as `ENABLED`. To also enable RDS data activity monitoring, pass `RDS_DATA_RISK` as the `name` under `AdditionalConfiguration` with `status` set to `ENABLED`.

Diff

diff --git a/guardduty/latest/ug/configure-rds-pro-multi-account.md b/guardduty/latest/ug/configure-rds-pro-multi-account.md
index c7715f8..55f3b69 100644
--- a//guardduty/latest/ug/configure-rds-pro-multi-account.md
+++ b//guardduty/latest/ug/configure-rds-pro-multi-account.md
@@ -9 +9 @@
-In a multiple-account environment, only the delegated GuardDuty administrator account has the option to enable or disable the RDS Protection feature for the member accounts in their organization. The GuardDuty member accounts can't modify this configuration from their accounts. The delegated GuardDuty administrator account manages their member accounts using AWS Organizations. This delegated GuardDuty administrator account can choose to auto-enable RDS login activity monitoring for all the new accounts as they join the organization. For more information about multiple-account environments, see [Managing multiple accounts](./guardduty_accounts.html).
+In a multiple-account environment, only the delegated GuardDuty administrator account has the option to enable or disable the RDS Protection feature, including the RDS data activity monitoring additional configuration, for the member accounts in their organization. The GuardDuty member accounts can't modify this configuration from their accounts. The delegated GuardDuty administrator account manages their member accounts using AWS Organizations. This delegated GuardDuty administrator account can choose to auto-enable RDS login activity monitoring and RDS data activity monitoring for all the new accounts as they join the organization. For more information about multiple-account environments, see [Managing multiple accounts](./guardduty_accounts.html).
@@ -11 +11 @@ In a multiple-account environment, only the delegated GuardDuty administrator ac
-Choose your preferred access method to configure RDS Login Activity Monitoring for the delegated GuardDuty administrator account.
+Choose your preferred access method to enable RDS Protection, including the RDS data activity monitoring additional configuration, for the delegated GuardDuty administrator account.
@@ -22 +22 @@ Console
-  4. Do one of the following:
+  4. Under **RDS Protection** , locate the **RDS Login Activity Monitoring** and **RDS Data Activity Monitoring** entries.
@@ -24 +24 @@ Console
-###### Using **Enable for all accounts**
+  5. In the **This account** column, choose **Enabled** for each entry that you want to turn on, or **Not enabled** to leave it off.
@@ -26,9 +26 @@ Console
-     * Choose **Enable for all accounts**. This will enable the protection plan for all the active GuardDuty accounts in your AWS organization, including the new accounts that join the organization.
-
-     * Choose **Save**.
-
-###### Using **Configure accounts manually**
-
-     * To enable the protection plan only for the delegated GuardDuty administrator account account, choose **Configure accounts manually**.
-
-     * Choose **Enable** under the **delegated GuardDuty administrator account (this account)** section.
+###### Note
@@ -36 +28 @@ Console
-     * Choose **Save**.
+RDS Login Activity Monitoring must be enabled before you can enable RDS Data Activity Monitoring.
@@ -44 +36 @@ API/CLI
-Run the [updateDetector](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateDetector.html) API operation using your own regional detector ID and passing the `features` object `name` as `RDS_LOGIN_EVENTS` and `status` as `ENABLED`.
+Run the [updateDetector](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateDetector.html) API operation using your own regional detector ID and passing the `features` object `name` as `RDS_LOGIN_EVENTS` and `status` as `ENABLED`. To also enable RDS data activity monitoring, pass `RDS_DATA_RISK` as the `name` under `AdditionalConfiguration` with `status` set to `ENABLED`.
@@ -49,0 +42,2 @@ To find the `detectorId` for your account and current Region, see the **Settings
+The following example enables RDS login activity monitoring on the delegated administrator account, and uses `AdditionalConfiguration` to also enable RDS data activity monitoring:
+    
@@ -51 +45,15 @@ To find the `detectorId` for your account and current Region, see the **Settings
-    aws guardduty update-detector --detector-id 12abc34d567e8fa901bc2d34e56789f0 --region us-east-1 --features '[{"Name": "RDS_LOGIN_EVENTS", "Status": "ENABLED"}]'
+    aws guardduty update-detector \
+        --detector-id 12abc34d567e8fa901bc2d34e56789f0 \
+        --region us-east-1 \
+        --features '[
+            {
+                "Name": "RDS_LOGIN_EVENTS",
+                "Status": "ENABLED",
+                "AdditionalConfiguration": [
+                    {
+                        "Name": "RDS_DATA_RISK",
+                        "Status": "ENABLED"
+                    }
+                ]
+            }
+        ]'
@@ -53 +61 @@ To find the `detectorId` for your account and current Region, see the **Settings
-Choose your preferred access method to enable the RDS Protection feature for all member accounts. This includes existing member accounts and the new accounts that join the organization.
+Choose your preferred access method to enable the RDS Protection feature, including the RDS data activity monitoring additional configuration, for all member accounts. This includes existing member accounts and the new accounts that join the organization.
@@ -62,3 +70 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-  2. Do one of the following:
-
-###### Using the **Protection Plans** page
+  2. In the navigation pane, choose **Protection Plans**.
@@ -66 +72 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-    1. In the navigation pane, choose **Protection Plans**.
+  3. Choose **Configure all enablements**.
@@ -68 +74 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-    2. Choose **Configure all enablements**.
+  4. Under **RDS Protection** , choose **Enable for all accounts**. This action automatically enables RDS Protection for both existing and new accounts in the organization.
@@ -70 +76 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-    3. Under **RDS Protection** , choose **Enable for all accounts**. This action automatically enables RDS Protection for both existing and new accounts in the organization.
+  5. To also turn on RDS data activity monitoring for every account, expand **Additional configuration** and choose **Enable for all accounts** for **RDS Data Activity Monitoring**.
@@ -72 +78 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-    4. Choose **Save all** , then choose **Confirm and save**.
+  6. Choose **Save all** , then choose **Confirm and save**.
@@ -78,12 +83,0 @@ It may take up to 24 hours to update the configuration for the member accounts.
-###### Using the **Accounts** page
-
-    1. In the navigation pane, choose **Accounts**.
-
-    2. On the **Accounts** page, choose **Auto-enable** preferences before **Add accounts by invitation**.
-
-    3. In the **Manage auto-enable preferences** window, choose **Enable for all accounts** under **RDS Login Activity Monitoring**.
-
-    4. Choose **Save**.
-
-If you can't use the **Enable for all accounts** option, see Selectively enable RDS Protection for member accounts.
-
@@ -96 +90 @@ API/CLI
-To selectively enable or disable RDS Protection for your member accounts, invoke the [updateMemberDetectors](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateMemberDetectors.html) API operation using your own `detector ID`. 
+To enable RDS Protection for all member accounts in your organization, including existing members and new accounts that join later, invoke the [UpdateOrganizationConfiguration](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateOrganizationConfiguration.html) API operation using your own `detector ID`. Set `AutoEnable` to `ALL` for the `RDS_LOGIN_EVENTS` feature, and pass `RDS_DATA_RISK` under `AdditionalConfiguration` with `AutoEnable` set to `ALL` to also auto-enable RDS data activity monitoring.
@@ -101,0 +96,21 @@ To find the `detectorId` for your account and current Region, see the **Settings
+The following example auto-enables both `RDS_LOGIN_EVENTS` and `RDS_DATA_RISK` for every member account in the organization:
+    
+    
+    aws guardduty update-organization-configuration \
+        --detector-id 12abc34d567e8fa901bc2d34e56789f0 \
+        --region us-east-1 \
+        --auto-enable-organization-members ALL \
+        --features '[
+            {
+                "Name": "RDS_LOGIN_EVENTS",
+                "AutoEnable": "ALL",
+                "AdditionalConfiguration": [
+                    {
+                        "Name": "RDS_DATA_RISK",
+                        "AutoEnable": "ALL"
+                    }
+                ]
+            }
+        ]'
+
+###### Note
@@ -103 +118 @@ To find the `detectorId` for your account and current Region, see the **Settings
-    aws guardduty update-member-detectors --detector-id 12abc34d567e8fa901bc2d34e56789f0 --region us-east-1 --account-ids 111122223333 --features '[{"name": "RDS_LOGIN_EVENTS", "status": "ENABLED"}]'
+It may take up to 24 hours to update the configuration for the member accounts.
@@ -105 +120 @@ To find the `detectorId` for your account and current Region, see the **Settings
-You can also pass a list of account IDs separated by a space.
+Choose your preferred access method to enable RDS Protection, including the RDS data activity monitoring additional configuration, for all the existing active member accounts in your organization. The member accounts that already have GuardDuty enabled, are referred to as existing active members.
@@ -107 +122 @@ You can also pass a list of account IDs separated by a space.
-When the code has successfully executed, it returns an empty list of `UnprocessedAccounts`. If there were any problems changing the detector settings for an account, that account ID is listed along with a summary of the issue.
+###### Note
@@ -109 +124 @@ When the code has successfully executed, it returns an empty list of `Unprocesse
-Choose your preferred access method to enable RDS Protection for all the existing active member accounts in your organization. The member accounts that already have GuardDuty enabled, are referred to as existing active members.
+RDS Login Activity Monitoring must be enabled on a member account before you can enable RDS Data Activity Monitoring on that account.
@@ -118 +133 @@ Sign in using the delegated GuardDuty administrator account credentials.
-  2. In the navigation pane, choose **Protection Plans**.
+  2. In the navigation pane, choose **Accounts**.
@@ -120 +135 @@ Sign in using the delegated GuardDuty administrator account credentials.
-  3. Choose **Configure all enablements**. Under **RDS Protection** , you can view the current status of the configuration. Under the **Active member accounts** section, choose **Actions**.
+  3. On the **Accounts** page, select the existing active member accounts you want to enable. To select every account, use the checkbox in the table header.
@@ -122 +137 @@ Sign in using the delegated GuardDuty administrator account credentials.
-  4. From the **Actions** dropdown menu, choose **Enable for all existing active member accounts**.
+  4. From the **Edit Protection Plans** dropdown menu, choose **RDS Login Activity** , and then choose **Enable**.
@@ -124 +139 @@ Sign in using the delegated GuardDuty administrator account credentials.
-  5. Choose **Confirm**.
+  5. To also enable RDS data activity monitoring on the selected accounts, open the **Edit Protection Plans** dropdown menu again, choose **RDS Data Activity** , and then choose **Enable**. RDS Login Activity Monitoring must already be enabled on each selected account.
@@ -132 +147 @@ API/CLI
-Run the [updateMemberDetectors](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateMemberDetectors.html) API operation using your own `detector ID`. 
+Run the [updateMemberDetectors](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateMemberDetectors.html) API operation using your own `detector ID`. Pass `RDS_DATA_RISK` under `AdditionalConfiguration` on the `RDS_LOGIN_EVENTS` feature to also control RDS data activity monitoring. 
@@ -138,2 +153,19 @@ To find the `detectorId` for your account and current Region, see the **Settings
-    
-    aws guardduty update-member-detectors --detector-id 12abc34d567e8fa901bc2d34e56789f0 --region us-east-1 --account-ids 111122223333 --features '[{"name": "RDS_LOGIN_EVENTS", "status": "ENABLED"}]'
+The following example enables RDS login activity monitoring on an existing active member account, and uses `AdditionalConfiguration` to also enable RDS data activity monitoring:
+    
+    
+    aws guardduty update-member-detectors \
+        --detector-id 12abc34d567e8fa901bc2d34e56789f0 \
+        --region us-east-1 \
+        --account-ids 111122223333 \
+        --features '[
+            {
+                "Name": "RDS_LOGIN_EVENTS",
+                "Status": "ENABLED",
+                "AdditionalConfiguration": [
+                    {
+                        "Name": "RDS_DATA_RISK",
+                        "Status": "ENABLED"
+                    }
+                ]
+            }
+        ]'
@@ -145 +177 @@ When the code has successfully executed, it returns an empty list of `Unprocesse
-Choose your preferred access method to enable RDS login activity for new accounts that join your organization.
+Choose your preferred access method to enable RDS login activity monitoring and RDS data activity monitoring for new accounts that join your organization.
@@ -150,4 +181,0 @@ Console
-The delegated GuardDuty administrator account can enable for new member accounts in an organization through the console, using either the **RDS Protection** or **Accounts** page.
-
-###### To auto-enable RDS Protection for new member accounts
-
@@ -158,13 +186 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-  2. Do one of the following:
-
-     * Using the **Protection Plans** page:
-
-       1. In the navigation pane, choose **Protection Plans**.
-
-       2. Choose **Configure all enablements**.
-
-       3. Choose **Configure accounts manually**.
-
-       4. Select **Automatically enable for new member accounts**. This step ensures that whenever a new account joins your organization, RDS Protection will be automatically enabled for their account. Only the organization delegated GuardDuty administrator account can modify this configuration.
-
-       5. Choose **Save**.
+  2. In the navigation pane, choose **Protection Plans**.
@@ -172 +188 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-     * Using the **Accounts** page:
+  3. Choose **Configure all enablements**.
@@ -174 +190 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-       1. In the navigation pane, choose **Accounts**.
+  4. Choose **Configure accounts manually**.
@@ -176 +192 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-       2. On the **Accounts** page, choose **Auto-enable** preferences.
+  5. Under **RDS Protection** , select **Automatically enable for new member accounts**. This step ensures that whenever a new account joins your organization, RDS Protection will be automatically enabled for their account. Only the organization delegated GuardDuty administrator account can modify this configuration.
@@ -178 +194 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-       3. In the **Manage auto-enable preferences** window, select **Enable for new accounts** under **RDS Login Activity Monitoring**.
+  6. To also auto-enable RDS data activity monitoring for new accounts, expand **Additional configuration** and select **Automatically enable for new member accounts** for **RDS Data Activity Monitoring**.
@@ -180 +196 @@ Make sure to use the delegated GuardDuty administrator account credentials.
-       4. Choose **Save**.
+  7. Choose **Save**.
@@ -188 +204 @@ API/CLI
-To selectively enable or disable RDS Protection for your member accounts, invoke the [UpdateOrganizationConfiguration](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateOrganizationConfiguration.html) API operation using your own `detector ID`.