{"id":77056,"date":"2023-01-25T21:15:00","date_gmt":"2023-01-25T21:15:00","guid":{"rendered":"https:\/\/www.globallogic.com\/il\/insights\/%insight%\/customising-aws-control-tower-with-cfct\/"},"modified":"2024-11-05T06:10:15","modified_gmt":"2024-11-05T06:10:15","slug":"customising-aws-control-tower-with-cfct","status":"publish","type":"insightsection","link":"https:\/\/www.globallogic.com\/il\/insights\/blogs\/customising-aws-control-tower-with-cfct\/","title":{"rendered":"Customising AWS Control Tower with CfCT"},"content":{"rendered":"
In this post, we\u2019re going to walkthrough how you can start customising Control Tower using the\u00a0Security Reference Architecture (SRA)<\/a>. The SRA utilises\u00a0Customisations for Control Tower (CfCT)<\/a>\u00a0which deploys a DevOps pipeline that works with CloudFormation templates and Control Tower lifecycle events.<\/p>\n By no means is this the only way of customising the Landing Zone that Control Tower deploys, but it\u2019s how the previous version of AWS Landing Zones was based upon and therefore, more users will be familiar with its setup and configuration. It does have some drawbacks though, in that it is only single threaded and therefore slow in large environments.<\/p>\n Here are some alternatives:<\/p>\n The easiest way to answer this question is simply because whilst Control Tower provides the foundations for a Well-Architected Multi-Account Landing Zone, it\u2019s not completely perfect.<\/p>\n In terms of AWS Services, Control Tower is still in its infancy and whilst AWS is constantly adding new functionality and guardrails, there are still some basic best practices that aren\u2019t there natively. For example, in Part Three we mentioned that AWS Config doesn\u2019t get configured in the Management Account but it is in every other Member AWS Account.<\/p>\n The reality is, there is no one size fits all, but there are synergies between them. With this in mind, the majority of organisations will need to tailor the Landing Zone to meet their specific security and governance requirements.<\/p>\n If you already have Control Tower enabled for you, this next section might not be relevant. However, it\u2019s always worth double checking just to play safe.<\/p>\n A web browser will then open prompting for login credentials if you\u2019re not already logged in.<\/p>\n Deploying the SRA Common Pre-Requisites<\/p>\n There are a few things that need to be installed on our local device as a pre-cursor for this part, including Git, Bash Shell, the AWS CLI v2 and 7-Zip. The following instructions will be based on running a Windows Device.<\/p>\n Now that we have the SRA source files locally, we need to start creating some CloudFormation Stacks in our Management Account using the YAML templates within the source. These templates setup the functionality for SRA to work before we even install the Customisations for Control Tower solution.<\/p>\n\n
Why would I want to customise Control Tower?<\/h4>\n
Enable Trusted Access for CloudFormation StackSets in AWS Organisations<\/h4>\n
\n
\n
\n
Configure an AWS CLI Profile to the Management Account<\/h4>\n
\n
<\/p>\n\n
\n
\n
<\/p>\n\n
<\/p>\n\n
<\/p>\n\n
<\/p>\n