Inference Public

Cloud foundations

Where Control Tower fits in a cloud operating model

Control Tower can set up a governed multi-account environment in under an hour. Deciding who owns each part of it takes longer, and matters more.

Engineer reviewing an abstract account structure on a wall screen.

Start with a practical question

Who decides whether a delivery team may have a new AWS account, which controls apply to it, and who can grant an exception? If the honest answer depends on one engineer's memory, the landing zone has a governance gap however well it was built. Control Tower automates a great deal of a multi-account foundation, and this article looks at where its automation stops.

What Control Tower sets up

AWS Control Tower sets up and governs a landing zone. It orchestrates AWS Organizations for accounts and organisation-wide policies, AWS Service Catalog for the Account Factory, and IAM Identity Center for user access.

During setup it enables mandatory controls that cannot be switched off. These protect the resources Control Tower itself creates, such as the organisation's CloudTrail trail, the AWS Config recorder, the log archive bucket and Control Tower's own roles. They do not cover other logging arrangements in member accounts, which depend on the controls you choose. The management account is also exempt from controls, so access to it needs its own strict protection.

Understand what each type of control actually does

Preventive controls are implemented as service control policies and, for some controls, resource control policies. They deny non-compliant actions before they happen, but they do not find resources that were already non-compliant.

Detective controls use AWS Config rules to report non-compliance after a change. They neither block the change nor fix it, so somebody has to own the response and the time it takes.

Proactive controls use CloudFormation hooks to check resources before they are provisioned, and they only apply to resources deployed through CloudFormation. Anything created through the console, the command line or another tool is not checked by them.

The practical decision is which risks need prevention, which can tolerate detection with an agreed response time, and which delivery routes your proactive checks really cover. AWS classes each control as mandatory, strongly recommended or elective, and the elective choices are where your organisation's judgement is needed.

What it leaves with you

Control Tower creates organisational units, but it cannot tell you how your organisation is governed. The OU structure, the elective controls, who reads the security logs, how exceptions are approved and how the landing zone itself is upgraded all need a named owner and a recorded decision. Our article on planning an OU strategy covers the first of these.

Account Factory needs a request process

The Account Factory provisions new accounts quickly, with approved configuration and controls applied automatically. That speed is valuable, and it also means accounts can multiply faster than anyone's understanding of them. Ask for a named owner, a cost code, a data classification and, for experimental accounts, an end date before an account is created.

Suppliers and exit

Many public bodies work with several delivery partners at once. Decide early whether suppliers work in accounts your organisation owns and governs, which accounts they can reach, and how access is removed when a contract ends. A landing zone that the organisation owns and lends to suppliers makes each supplier transition considerably simpler.

Working document: an account ownership and exception record

Keep one record per account, ideally generated from the same code that provisions it, so that ownership and exceptions can be reviewed together.

Illustrative template
FieldWhat to record
AccountName, identifier and organisational unit.
OwnerThe named person and team accountable for the account and its costs.
Purpose and dataWhat runs there and the classification of the data it handles.
CostCost code, budget and the alert threshold that notifies the owner.
Supplier accessWhich supplier has access, through which roles, and the contract end date.
Controls beyond baselineAny additional controls applied and the reason for each.
ExceptionsEach control exception with its reason, approver, expiry and review date.
End dateFor sandbox and experimental accounts, when the account will be closed.

Read about infrastructure engineering or discuss your AWS foundations.

Further reading

AWS Control Tower: what is AWS Control Tower?

AWS Control Tower: about controls

Related articles

Planning an OU strategy that outlasts the next reorganisation

A landing zone needs owners as well as accounts.

All insights

Start a conversation

Let’s talk about what you need to build.

Bring the service, the constraint or the engineering question. We’ll work through a sensible starting point.

Discuss a project