A/05Accelerators
AWS Landing Zone
Infrastructure as code from the first commit.
The problem it solves
Infrastructure built by hand in a console works until someone has to rebuild it, audit it or hand it over. Most teams know they should codify it; few have time to design the layout, the state, the pipelines and the security headers before the first feature is due.
An OpenTofu and Terragrunt foundation for AWS: an explicit dependency graph, a pinned toolchain in a container, and CloudFront hosting behind a strict Content-Security-Policy. This website is deployed on it.
What’s inside
- ✦A directory layout where environment, account and region come from the path
- ✦Registry modules wired with explicit dependencies, with no hidden wrapper modules
- ✦A pinned toolchain in a container, so every machine runs the same versions
- ✦Static hosting on S3 and CloudFront with a strict Content-Security-Policy and a build step that enforces it
- ✦Validation that runs offline, without cloud credentials
How a project uses it
- 01Review your current AWS estate and what must stay as it is
- 02Lay out accounts, environments and state
- 03Codify existing resources or build fresh ones
- 04Hand over with plan and apply steps documented and rehearsed
What it is not
- A managed hosting service
- A multi-cloud abstraction
- A reason to rebuild infrastructure that already works
Works well with
- A/06
Modernisation Starter
Change an old system without switching it off.
A toolkit for moving an ageing application forward safely: an inventory of what it really does, tests that pin its behaviour, and scaffolding to replace it piece by piece.
- Legacy systems
- Characterisation tests
- Strangler fig
- Incremental delivery
- A/01
Governed RAG Foundation
Answers from your documents — only from the ones the person asking may read.
Retrieval-augmented generation over company data, with access control carried from the source system and a citation on every answer.
- RAG
- Vector search
- Access control
- Citations
Start a project
Want this under your project?
Tell us what you are building and what you already have. We will tell you whether this accelerator fits, what it would need adapting, and where it would not help.
No form and no automated follow-up sequence. An email reaches an engineer, and the first reply is either a real question or an honest “not us.” We work in English, remotely, across European time zones.
We reply to every message that isn’t automated.