International leasing group
Infrastructure as code for an organisation, not a project
An enterprise with dozens of teams wanting AWS accounts and no consistent way to give them one. Designed the multi-account model and the automation and process around it.
The situation
An international vehicle-leasing group operating in more than thirty countries, moving into AWS. Teams were requesting cloud accounts faster than anyone could provision them consistently. Each one arrived configured slightly differently, which meant security review was bespoke every time and nothing could be assumed about any given account.
The problem was organisational as much as technical: not “how do we build an account” but “how does this company give a team an account, repeatably, without a person in the middle.”
What was done
Designed and automated a multi-account infrastructure-as-code model — account structure, baseline security and networking applied automatically, identity and access as code, and a deployment framework teams could use without needing to become infrastructure experts.
The process around it mattered as much as the automation: what a team must supply to get an account, what they get by default, what they may change, and who approves the rest. Codified and documented, so it survives the people who wrote it.
Where it ended up
Provisioning became repeatable rather than artisanal. New accounts arrived with the same baseline, which made security review a check rather than an investigation.
What this engagement taught: at enterprise scale the automation is the easy half. The durable part is the agreed process it encodes — and getting that agreed means talking to a lot of teams who all believe their case is the exception.