AWS controltower: Clarify required enabled flags for Control Tower integrations
Summary
Changed wording from 'optionally required' to 'required' enabled flags in the API for AWS Control Tower service integrations.
Security assessment
Purely a wording correction about API flag semantics; no vulnerability, credential, or access-control content is introduced.
Evidence
+ * **Optional Service Integrations:** You now have the ability to enable/disable all AWS Control Tower integrations including AWS Config, AWS CloudTrail, SecurityRoles, and AWS Backup. These integrations also now have required `enabled` flags in the API. The baselines that may apply to your landing zone or shared accounts now have dependencies on one another. The Integrations specific dependencies are:
Diff
diff --git a/controltower/latest/userguide/key-changes-lz-v4.md b/controltower/latest/userguide/key-changes-lz-v4.md index 6d0ffffe8..7ef1b758d 100644 --- a//controltower/latest/userguide/key-changes-lz-v4.md +++ b//controltower/latest/userguide/key-changes-lz-v4.md @@ -46 +46 @@ Accounts in the Security OU that are not designated as service integration accou - * **Optional Service Integrations:** You now have the ability to enable/disable all AWS Control Tower integrations including AWS Config, AWS CloudTrail, SecurityRoles, and AWS Backup. These integrations also now have optionally required `enabled` flags in the API. The baselines that may apply to your landing zone or shared accounts now have dependencies on one another. The Integrations specific dependencies are: + * **Optional Service Integrations:** You now have the ability to enable/disable all AWS Control Tower integrations including AWS Config, AWS CloudTrail, SecurityRoles, and AWS Backup. These integrations also now have required `enabled` flags in the API. The baselines that may apply to your landing zone or shared accounts now have dependencies on one another. The Integrations specific dependencies are: