Messy shared accounts, tidied into a landing zone
Several projects lived in the same AWS accounts, each with its own habits, and costs kept rising.
- What we found
- Multiple projects sharing one account, no standard governance around security, every team building its own route to the internet, and shortcuts that had become permanent. Nobody could say which project a cost or a permission belonged to.
- Where it came from
- Consulting work in roles held before Inference Public was established, across several organisations.
- Approach
- A landing zone: accounts separated by workload and environment, organisational units grouping them by the guardrails they need, service control policies enforcing the rules that must never be broken, and centralised logging and identity.
- AWS services
- AWS Organizations, AWS Control Tower and Account Factory, service control policies, AWS IAM Identity Center, AWS CloudTrail and AWS Config, AWS Service Catalog for golden-path templates, and cost allocation tags with AWS Cost Explorer and AWS Budgets.
- Developer golden paths
- Standard, supported ways for teams to get an account, deploy and connect, so following the guardrails is the easiest route rather than an obstacle.
- What it changes
- Each cost and permission has an owner, new projects start from a governed baseline instead of a copy of the last one, and exceptions become visible decisions rather than shortcuts.
- What it taught us
- Ownership and discipline matter more than tooling. See a landing zone needs owners as well as accounts.
