Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

When to multi-account

This revision card explains When to multi-account. It starts from the need that premature multi-account adds tickets; one shared account forever adds blast radius. It describes split when you need strong blast-radius limits, different security postures, or clear bill-by-team. The how-to section notes start with Sandbox + Workloads + Security OUs; avoid dozens of empty accounts. An example on the card is a student lab in Sandbox cannot touch prod data in Workloads.

When to multi-account Premature multi-account adds tickets; one shared account forever adds blast radius. Split when you need strong blast-radius limits, different security postures, or clear bill-by-team. Start with Sandbox + Workloads + Security OUs; avoid dozens of empty accounts. A student lab in Sandbox cannot touch prod data in Workloads.
When to multi-account · Download PNG
Read card text

What this card says

Why do we need it?

Premature multi-account adds tickets; one shared account forever adds blast radius.

What is it?

Split when you need strong blast-radius limits, different security postures, or clear bill-by-team.

blast radius

How to do it

Start with Sandbox + Workloads + Security OUs; avoid dozens of empty accounts.

Example

A student lab in Sandbox cannot touch prod data in Workloads.

See all AWS revision cards