AWS controltower documentation change
Summary
Updated drift resolution behavior documentation: added version-specific instructions (3.1+ vs older versions) for Reset/Update actions
Security assessment
Clarifies operational procedures for drift resolution but doesn't mention security vulnerabilities, patches, or security features
Diff
diff --git a/controltower/latest/userguide/resolve-drift.md b/controltower/latest/userguide/resolve-drift.md index 8009b55cb..892cdc127 100644 --- a//controltower/latest/userguide/resolve-drift.md +++ b//controltower/latest/userguide/resolve-drift.md @@ -17 +17 @@ One special case of drift resolution occurs for _role drift_. If a required role -###### When you take action to resolve drift on a landing zone version, two behaviors are possible. +###### When you take action to resolve drift on a landing zone version, the behavior depends on your current version. @@ -19 +19 @@ One special case of drift resolution occurs for _role drift_. If a required role - * If you are on the latest landing zone version, when you choose **Reset** and then choose **Confirm** , your drifted landing zone resources are reset to the saved AWS Control Tower configuration. The landing zone version stays the same. + * If you are on landing zone version 3.1 or above, you can choose **Update** to change your landing zone configuration without upgrading versions, or choose **Reset** to reapply your saved configurations to your drifted landing zone resources. Drift is resolved as part of the update process. @@ -21 +21 @@ One special case of drift resolution occurs for _role drift_. If a required role - * If you are not on the latest version, you must choose **Update**. The landing zone is upgraded to the latest landing zone version. Drift is resolved as part of this process. + * If you are on a landing zone version earlier than 3.1, you cannot choose **Reset**. You must choose **Update** and upgrade your landing zone to at least version 3.1.