What is the best way to separate projects in AWS services?

Question

I would like to have a strict split between my own, personal, services in the AWS. These services can be split into two categories:

• Ones that are not changing often but are responsible for crucial for me services (e.g. Route53 config for my main domain),
• Ones that are "experiments" / side-projects that can change often and touches multiple services through CloudFront/Serverless framework.

What is the best solution in 2021 to address this challenge? Multiple AWS accounts or AWS Organizations or something else?

The requirements are:

• I would like to have my crucial services (first category of services) properly guarded, i.e. not easily changed by a mistake,
• At the same time I'm the only person that will in the end manage both so I'd like to have one bill and not separate ones.

Answer 1

A common way to address your use-case is through AWS Organizations. Using AWS Org you would have one management account and two member accounts for your services.

This allows you to consolidate all the billing as well as setup Org level Service control policies to manage permissions in your member account.

It is also common to have a dedicated security member account which will be a central repository of various logs from other accounts.