AWS guardduty documentation change
Summary
Clarified disassociation consequences including loss of findings access and lack of notifications.
Security assessment
Improves documentation accuracy about existing security boundaries but doesn't address new vulnerabilities or security features.
Diff
diff --git a/guardduty/latest/ug/disassociate-remove-member-account-from-admin.md b/guardduty/latest/ug/disassociate-remove-member-account-from-admin.md index f2da7283b..9450a05b1 100644 --- a//guardduty/latest/ug/disassociate-remove-member-account-from-admin.md +++ b//guardduty/latest/ug/disassociate-remove-member-account-from-admin.md @@ -9 +9,14 @@ When you want to stop configuring the GuardDuty settings and accessing the data -When you disassociate a GuardDuty member account, GuardDuty remains enabled for the account in the current AWS Region. However, the account is disassociated from the delegated GuardDuty administrator account and the account becomes a standalone GuardDuty account. After you have disassociated the member account, it continues to show in the account inventory. GuardDuty doesn't notify the account's owner that you disassociated the account. You can add the account to your organization again at a later time. +When you disassociate a GuardDuty member account, the following happens: + + * GuardDuty remains enabled for the account in the current AWS Region, but the account becomes disassociated from the delegated GuardDuty administrator account. + + * The disassociated account continues to show in the account inventory. + + * The GuardDuty administrator account no longer has access to this standalone account's findings. + + * The account owner is not notified of the disassociation. + + + + +You can add the disassociated account to your organization again at a later time.