A landing zone is the underlying core configuration of any cloud adoption environment. Landing zones provide a pre-configured environment – provisioned through code – to host workloads in private, hybrid, or public clouds. You don’t want to hand your developers “naked” cloud tenants – completely unconfigured AWS accounts, Azure subscriptions, or GCP projects.
Landing Zones allow you to standardize cloud environments that are provisioned to DevOps teams. They offer consistency across all tenants in naming, scaling, and access control. With that comes a security baseline that preempts (accidental) non-compliant or unauthorized configurations.
So let’s talk about the differnt phases of a landing zones lifecycle!