An account is a boundary
A cloud account ties together three things: the resources that exist inside it, the billing relationship that pays for them, and the identities permitted to act on them. Everything you create lives inside one.
Because the account is the boundary, it is also the natural unit of separation. One account per project or per environment keeps spend attributable, keeps permissions simple, and limits how far a mistake can travel.
Root access and its weight
The original owner identity on an account can usually do anything, including closing it. That identity should be protected with multi-factor authentication and used as rarely as possible, with day-to-day work done through a less privileged user.
Separation in practice
A common pattern is one account for production, one for staging, and one per client or experiment. The small overhead of managing several accounts is usually repaid the first time a test resource would otherwise have appeared on a production bill.


