AWS guardduty documentation change
Summary
Added clarification about 'COMPLETED_WITH_ISSUES' status for S3 Recovery Points and AMIs, explaining what triggers this status
Security assessment
The change provides operational clarification about scan statuses but doesn't address any security vulnerability or weakness. It improves documentation accuracy without security implications.
Diff
diff --git a/guardduty/latest/ug/monitoring-malware-protection-backup-scans.md b/guardduty/latest/ug/monitoring-malware-protection-backup-scans.md index affb0ebbe..ce0612318 100644 --- a//guardduty/latest/ug/monitoring-malware-protection-backup-scans.md +++ b//guardduty/latest/ug/monitoring-malware-protection-backup-scans.md @@ -17,0 +18,2 @@ Scan Result Status | `NO_THREATS_FOUND` or `THREATS_FOUND` +For S3 Recovery Points, COMPLETED_WITH_ISSUES indicates that some files were either skipped or failed. For AMI's, COMPLETED_WITH_ISSUES indicates that at least 1 snapshot was not able to be scanned. See below for the list of skipped reasons. +