amazon-web-servicesarchitectureclouddomain-driven-designbounded-contexts

AWS Accounts and Bounded Contexts


I am migrating a project from Azure to AWS. In Azure we used a subscription for each environment like "dev,test,prod" and resources groups to cluster resources that are part of a bounded context.

How would one organize this scenario in AWS? We started with AWS Organizations and organized the environments in different Organizational Unit. Within an OU would one rather create an Account for each bounded context or let all resources live in a single account and use resource groups instead?

Any suggestions?


Solution

  • Ideally you would split down to at least one account per each environment within their respective organisational unit.

    As time progresses you might look at splitting down further, such as accounts per application as well as accounts for specific functions such as centralisation of monitoring etc.

    AWS have also published their list of best practices available here if this helps with your decision.