AWS guardduty: Update Organizations permission error text in malware protection troubleshooting
Summary
Rewrites the quoted error string shown when a user lacks permission to enable GuardDuty-initiated malware scan across an AWS Organizations organization, changing the wording from 'required AWS Organization master permission' to 'required AWS Organizations management account permission'; the surrounding remediation guidance is unchanged.
Security assessment
The only change is terminology alignment with the renamed Organizations management-account permission in an error message; the explanatory guidance about missing permissions for enabling malware scanning is identical. No vulnerability, weakness, or new security guidance is introduced.
Evidence
+When you want to manage multiple accounts by using AWS Organizations and you get this error – `The request failed because you do not have the required AWS Organizations management account permission.`, then you're missing the permission to enable GuardDuty-initiated malware scan for multiple accounts in your organization.
Diff
diff --git a/guardduty/latest/ug/troubleshooting-guardduty-malware-protection-issues.md b/guardduty/latest/ug/troubleshooting-guardduty-malware-protection-issues.md index fb461d6..f4b5985 100644 --- a//guardduty/latest/ug/troubleshooting-guardduty-malware-protection-issues.md +++ b//guardduty/latest/ug/troubleshooting-guardduty-malware-protection-issues.md @@ -15 +15 @@ This section lists the errors that you may experience when setting up or using M -When you want to manage multiple accounts by using AWS Organizations and you get this error – `The request failed because you do not have required AWS Organization master permission.`, then you're missing the permission to enable GuardDuty-initiated malware scan for multiple accounts in your organization. +When you want to manage multiple accounts by using AWS Organizations and you get this error – `The request failed because you do not have the required AWS Organizations management account permission.`, then you're missing the permission to enable GuardDuty-initiated malware scan for multiple accounts in your organization.