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.
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...
Usually, the best way to learn is by experimentation. But with security, your "experiments" might leave you exposed. Or at least, leave your system in some nonstandard state, making it even harder to figure out what the correct route was supposed to be.
It's why I've been happy to use things like netlify. They may not scale, but at least it feels like I can get a project up without it becoming an ordeal of opening permissions.
It's not my main line of work, and as you say, I imagine I would figure it out if I did it consistently for a bit. But every time I start a side project using AWS, IAM scares me off.