AWS controltower documentation change
Summary
Updated terminology from enrollment status to baseline status and aligned status labels
Security assessment
This change improves documentation about the AWS Control Tower baseline (a security feature) by standardizing terminology to 'AWS Control Tower baseline status'. It provides clearer guidance on account compliance states but doesn't address any specific security vulnerability or incident. The update enhances security documentation clarity without resolving an existing threat.
Diff
diff --git a/controltower/latest/userguide/ou-updates.md b/controltower/latest/userguide/ou-updates.md index 6a54808a7..e64cf1b96 100644 --- a//controltower/latest/userguide/ou-updates.md +++ b//controltower/latest/userguide/ou-updates.md @@ -24 +24 @@ The quickest way to update an organizational unit (OU) or to update multiple acc - * The **State** field indicates whether the account currently is enrolled with AWS Control Tower (**Enrolled**), whether the account has never been enrolled (**Not enrolled**), or whether enrollment failed previously (**Enrollment failed**). + * The **AWS Control Tower baseline status** field indicates whether the `AWSControlTowerBaseline` is applied to the account (**Enabled**), whether the baseline has not been applied (**Not enabled**), or whether applying the baseline failed previously (**Failed**). @@ -26 +26 @@ The quickest way to update an organizational unit (OU) or to update multiple acc - * When you re-register the OU, the `AWSControlTowerExecution` role is added to all accounts with status **Not enrolled** or **Enrollment failed**. + * When you re-register the OU, the `AWSControlTowerExecution` role is added to all accounts with status **Not enabled** or **Failed**. @@ -30 +30 @@ The quickest way to update an organizational unit (OU) or to update multiple acc - * **Enrolled** accounts are re-enrolled into AWS Control Tower. + * **Enabled** accounts are re-enrolled into AWS Control Tower.