AWS guardduty medium security documentation change
Summary
Corrected AWS CLI command from update-member-detectors to update-detector for RDS monitoring
Security assessment
Fixes incorrect command that could prevent proper security monitoring configuration (RDS_LOGIN_EVENTS enablement)
Diff
diff --git a/guardduty/latest/ug/configure-rds-pro-multi-account.md b/guardduty/latest/ug/configure-rds-pro-multi-account.md index 01fcee386..0c0786a74 100644 --- a/guardduty/latest/ug/configure-rds-pro-multi-account.md +++ b/guardduty/latest/ug/configure-rds-pro-multi-account.md @@ -49 +49 @@ 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 --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"}]'