AWS Security ChangesHomeSearch

AWS controltower medium security documentation change

Service: controltower · 2026-05-22 · Security-related medium

File: controltower/latest/userguide/config-updates-v4.md

Summary

Added warning about potential AWS Config data loss during upgrade and recommended remediation steps

Security assessment

Addresses security logging gap where configuration snapshots/history might not be delivered to S3 during upgrade, impacting audit capabilities. Explicitly warns about data loss risk and provides API workaround.

Diff

diff --git a/controltower/latest/userguide/config-updates-v4.md b/controltower/latest/userguide/config-updates-v4.md
index 65b8975fc..9fdce410c 100644
--- a//controltower/latest/userguide/config-updates-v4.md
+++ b//controltower/latest/userguide/config-updates-v4.md
@@ -99,0 +100,4 @@ After you upgrade to landing zone version 4.0 and enable the AWS Config integrat
+We recommend that you re-register your OUs or enable the `ConfigBaseline` as soon as possible after enabling the AWS Config integration. The landing zone update removes AWS Config delivery permissions from the previous S3 bucket policy, but delivery channels are redirected to the new bucket only after you complete re-registration. Until then, configuration snapshots and configuration history are not delivered to S3. 
+
+If re-registration is delayed, some of this data may not be delivered to S3 after re-registration completes. You can retrieve all data recorded within your configured retention period using the `config:GetResourceConfigHistory` API. 
+