AWS prescriptive-guidance documentation change
Summary
Changed 'AWS CloudFormation Hooks' to 'CloudFormation Hooks' for terminology consistency
Security assessment
This is a branding/nomenclature update without any substantive changes to security controls or guidance. The security implications of using CloudFormation Hooks remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/designing-control-tower-landing-zone/custom.md b/prescriptive-guidance/latest/designing-control-tower-landing-zone/custom.md index 72304ccfd..0b51e6cce 100644 --- a//prescriptive-guidance/latest/designing-control-tower-landing-zone/custom.md +++ b//prescriptive-guidance/latest/designing-control-tower-landing-zone/custom.md @@ -7 +7 @@ -After you have conducted your risk assessment, identified your security and compliance requirements, and selected the AWS Control Tower controls to guardrail these requirements, there might be some requirements that still aren't addressed. You can implement custom service control policies (SCPs), AWS Config Rules, and AWS CloudFormation Hooks to cover these requirements. However, these controls aren't implemented as AWS Control Tower controls—they're implemented outside AWS Control Tower. +After you have conducted your risk assessment, identified your security and compliance requirements, and selected the AWS Control Tower controls to guardrail these requirements, there might be some requirements that still aren't addressed. You can implement custom service control policies (SCPs), AWS Config Rules, and CloudFormation Hooks to cover these requirements. However, these controls aren't implemented as AWS Control Tower controls—they're implemented outside AWS Control Tower.