3 Answers
Hi Hendry,
Like the other domains, Designing for Organizational Complexity is a very wide space and your example is pretty specific.
In practice, I would not create some automated rule that prevents new resources once a budget is reached as this may kick in during a time when you really need it like in a scale-out scenario, a backup run or a DR situation. SCP’s are designed to setup guard-rails around sub-accounts rather than dynamically adding and removing capabilities. AWS Budgets are more designed to help enforce awareness of budgets. You can read about a practical example of this here but I probably would not implement it for reasons above: https://aws.amazon.com/blogs/compute/serverless-automated-cost-controls-part1/
Here are a few broad resources that might help get you started. This isn’t exhaustive but it should set you on the right path.
https://d1.awsstatic.com/whitepapers/cost-optimization-transparency-accountability.pdf
https://aws.amazon.com/answers/account-management/aws-multi-account-billing-strategy/
https://www.youtube.com/watch?v=kErRv4YB_T4
https://www.youtube.com/watch?v=ZKpkF17d0Oo
–Scott
Just got the same 0 score today! LOL
I started a global renovation in my apartment and decided to completely change the interior. The site https://crawoo.com/ helps me with this and I can say with confidence that it has the best quality and reasonable prices.