The Multi-Account Organization
There are a lot of properties of having multiple AWS accounts in an organization to recommend it as a practice: Separate invoices for different teams
In some organizations cost allocation is a thing, and being able to get different invoices for different product groups is good. You can achieve some of this using Tags, but various services have some costs that aren’t easily separated. Security
It can be difficult to avoid giving developers IAM access, since there are an ever increasing number of services and uses for it with assumed roles for EC2 and AWS Lambda.
[Read More]