AWS controltower documentation change
Summary
Updated instructions for repairing mixed governance by resetting regional controls and removed outdated steps for account/OU updates.
Security assessment
The documentation now clarifies how to resolve mixed governance states, which helps maintain compliance and control enforcement. While this relates to security posture, it does not directly address a specific security vulnerability.
Diff
diff --git a/controltower/latest/userguide/mixed-governance.md b/controltower/latest/userguide/mixed-governance.md index bdf2c6b2d..2904daf41 100644 --- a//controltower/latest/userguide/mixed-governance.md +++ b//controltower/latest/userguide/mixed-governance.md @@ -40,3 +40 @@ Mixed governance is not the same as drift, and it is not reported as drift. - * Choose **Update account** for each account in the OU that shows **Update available** status on the **Organizations** page in the console. - - * Choose **Re-Register OU** on the **Organizations** page, which automatically updates all accounts in the OU, for OUs with fewer than 1000 accounts. + * Customers are now able to repair mixed governance by resetting regional controls. Any non-global controls are regional (detective and proactive controls). You will be alerted that your OU is in a mixed governance through an alert banner.