Multi-account architecture for cost isolation
Use cloud accounts as a cost boundary. How to divide them, what to share, and what the network between them costs.
5 lessons. 1 quiz.
Read in order, or jump to what you need.
Per-team vs per-env accounts
By the end of this lesson, you will be able to choose between per-team and per-environment account axes, evaluate the hybrid (per-team × per-env) option, and assess the trade-offs (isolation, ops overhead, blast radius).
Shared services accounts
By the end of this lesson, you will be able to design a shared-services account for cross-cutting infrastructure, decide what should be centralized vs team-owned, and allocate the shared cost back to consuming teams.
Network architecture and egress cost
By the end of this lesson, you will be able to diagnose network egress costs in your estate, identify the top three cost-reducing patterns (VPC endpoints, Transit Gateway, PrivateLink), and decide when cross-region replication is worth its cost.
Cross-account scheduling concerns
By the end of this lesson, you will be able to identify cross-account scheduling concerns, design coordinated schedules that respect dependencies, and avoid the common multi-account scheduling anti-patterns.
Consolidate vs split
By the end of this lesson, you will be able to decide when to consolidate accounts vs split them, execute a consolidation or split migration, and run an annual account-structure review to keep the org's account topology aligned with reality.
Module quiz.
Take it once the lessons are done.