Control Tower - Unable to add new account to the Security OU?

Question

Hello,

I'm setting up a new Control Tower managed organization using https://docs.aws.amazon.com/prescriptive-guidance/latest/security-reference-architecture/ as a reference. This suggests creating a Security Tooling account under the Security OU for services such as GuardDuty, Security Hub, etc.

When I try to create this account in the Service Catalogue, the Security OU isn't available to select for the ManagedOrganiszationalUnit preference (all other OU are though). How can I add a CT managed account to the Security OU?

Thanks!

Accepted Answer

Hi, unfortunately there seems to be a disparity in the documentation. While the Security Reference Architecture describes the Security Tooling account under the Security OU. Control Towers functionality does not allow the provisioning of an Account into it's default created OU, which happens to be called Security, as this is the location for core accounts that Control Tower creates. The field advice I give customers on this currently, and often help them deploy, is to create a new OU for the Security Tooling account. There are also mandatory guardrails applied to that default OU, that may limit your usage, and it's best to keep accounts that you create in their own OU's to allow full flexibility in deployment and configuration.

Answer

Thanks for the explanation, Jimmy. I've passed on this feedback via the SRA page so hopefully this will be picked up.

Control Tower - Unable to add new account to the Security OU?

Relevant questions