AWS guardduty documentation change
Summary
Removed '(recommended)' label from AWS managed policy reference for Malware Protection
Security assessment
Minor editorial change to policy naming convention. Does not alter security guidance or address vulnerabilities.
Diff
diff --git a/guardduty/latest/ug/enable-malware-protection-s3-bucket.md b/guardduty/latest/ug/enable-malware-protection-s3-bucket.md index cb265ee3e..462ea047b 100644 --- a//guardduty/latest/ug/enable-malware-protection-s3-bucket.md +++ b//guardduty/latest/ug/enable-malware-protection-s3-bucket.md @@ -30 +30 @@ If you expect high volumes of `GET` and `PUT` requests to your S3 buckets, consi -When you enable Malware Protection for S3 for an Amazon S3 bucket, GuardDuty creates a Malware Protection plan resource that acts as an identifier for the bucket's protection plan. If you are not already using the [AWS managed policy: AmazonGuardDutyFullAccess_v2 (recommended)](./security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonGuardDutyFullAccess-v2), then you must add the following permissions to create this resource: +When you enable Malware Protection for S3 for an Amazon S3 bucket, GuardDuty creates a Malware Protection plan resource that acts as an identifier for the bucket's protection plan. If you are not already using the [AWS managed policy: AmazonGuardDutyFullAccess_v2](./security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonGuardDutyFullAccess-v2), then you must add the following permissions to create this resource: