- Newest
- Most votes
- Most comments
The issue you're experiencing with resetting the CT.CLOUDFORMATION.PR.1 control is likely due to recent changes in AWS Control Tower's hook functionality.
To resolve this, you should follow these steps:
-
Instead of trying to reset the CT.CLOUDFORMATION.PR.1 control specifically, try resetting any other enabled proactive control on the current Organizational Unit (OU). You can do this by using the ResetEnabledControl API or by using the "Reset control" button on the Control page in the console for a different proactive control.
-
After resetting any proactive control, AWS Control Tower should move all of the proactive control hooks on the OU to the new capability.
-
Once you've done this, navigate to the CT.CLOUDFORMATION.PR.1 control in the AWS Control Tower controls library.
-
Disable the CT.CLOUDFORMATION.PR.1 control.
It's important to note that when you reset a proactive control, all enabled proactive controls for that OU are reset because their artifacts are bundled and deployed together.
If you have multiple OUs with proactive controls enabled, you'll need to repeat this process for each of those OUs.
Remember, the CT.CLOUDFORMATION.PR.1 control should be removed from your AWS Control Tower OUs after resetting, unless you specifically enabled it for another purpose. Keeping this control enabled may prevent you from creating and modifying other AWS CloudFormation hooks.
If you continue to experience issues after following these steps, you may need to contact AWS support for further assistance.
Sources
Update your proactive control hooks - AWS Control Tower
January - December 2024 - AWS Control Tower
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 2 months ago
