Comparison
Cloud landing zonevsInfrastructure module
Cloud landing zone
a new team gets an account that already has the network, the logging, the guardrails and the billing tags applied.
A pre-baked account or project structure with networking, identity, logging, policy and cost controls already in place, issued rather than assembled. It exists because the alternative is every team making the same twenty decisions differently, and then a compliance exercise discovering that. It is the account-level equivalent of a golden path, and like a golden path its value collapses if teams routinely need to step outside it.
Full entry →Infrastructure module
the team's standard service takes six inputs and produces thirty resources, and nobody writes the thirty by hand any more.
A parameterised, reusable unit of infrastructure configuration with declared inputs and outputs. It is how a platform team encodes an opinionated default and how a golden path becomes a thing you can call rather than a document. The failure mode is the module with forty inputs, which is a leaky abstraction that has all the indirection of a module and none of the opinion.
Full entry →