Why landing zones exist
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
explain why a landing zone should exist before workloads arrive.
Planned topics
- A landing zone is the prepared foundation: account structure, networking, identity, logging, security baseline, and guardrails.
- Without it, each team builds its own, producing inconsistent security and cost.
- Retrofitting guardrails onto live workloads is slow and risky.
- It gives teams a safe, fast way to start: self-service within boundaries.
- Keep it small and evolve it; it is a product with an owner.
Draft outline details
Demonstration
a diagram: organization root, baseline services (logging, security, network), and workload accounts created from a template.
Check your understanding
When should guardrails be added?
Show answer
Before workloads go live, not after.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.