News for hackers. Stuff that matters.
Re:AWS Permission Boundaries for Dummies by technion on Thursday October 13, 2022 @09:13PM (#33198556)
I would suggest azure has an approach that shows how iam can be a lot simpler. I can create a resource group, and make you a contributor on that group.

You now have full permissions to servers, storage and anything else created under that group without me having to enumerate them. If I want to create a new blob store under that group, you already have access without me having to edit iam. I can still make granular permissions where suitable.

Azure makes the path to having all console users require mfa much simpler too.

Re:AWS Permission Boundaries for Dummies by vdm on Friday October 14, 2022 @06:53AM (#33201831)
Thanks for sharing this perspective.

AWS IAM does have resource condition keys which allow matching resources by account, org, org path, and tag. Resources in a Cloudformation stack would be automatically tagged, for example.

https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_p...