AWS guardduty documentation change
Summary
Removed '(recommended)' label from AmazonGuardDutyFullAccess_v2 policy reference
Security assessment
Similar to the first change, this removes a recommendation qualifier without altering security guidance or addressing vulnerabilities. Maintains existing security documentation standards.
Diff
diff --git a/guardduty/latest/ug/malware-protection-getting-started-on-demand-scan.md b/guardduty/latest/ug/malware-protection-getting-started-on-demand-scan.md index 88d6c53dc..758a54d69 100644 --- a//guardduty/latest/ug/malware-protection-getting-started-on-demand-scan.md +++ b//guardduty/latest/ug/malware-protection-getting-started-on-demand-scan.md @@ -19 +19 @@ Before you start an On-demand malware scan, your account must meet the following - * Ensure that the [AWS managed policy: AmazonGuardDutyFullAccess_v2 (recommended)](./security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonGuardDutyFullAccess-v2) is attached to the IAM user or the IAM role. You will need the access key and secret key associated with the IAM user or the IAM role. + * Ensure that the [AWS managed policy: AmazonGuardDutyFullAccess_v2](./security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonGuardDutyFullAccess-v2) is attached to the IAM user or the IAM role. You will need the access key and secret key associated with the IAM user or the IAM role.