News for hackers. Stuff that matters.
Re:Awsviz.dev simplifying AWS IAM policies by tyingq on Wednesday July 10, 2024 @02:40PM (#40929999)
You can't meld the rules together to get a cohesive view of, for example, "who can access this S3 bucket?". Because, for example, an SCP can override a bucket policy. And policies can be other places too.

I can get "can this specific role/user access this specific bucket", just not the other direction.

It's not because the language isn't consistent, it's because the language isn't backed by a single cohesive RBAC type setup.

Re:Awsviz.dev simplifying AWS IAM policies by oneplane on Wednesday July 10, 2024 @04:15PM (#40931051)
I'm not sure how that makes it a bolt-on or conflicting or complicated. It is indeed not a simple central spreadsheet of 'who can do X on Y', but that would not be feasible at AWS scale.

Microsoft tries that with Entra and it's a pretty miserable experience. Google has CEL for the conditionals which is neat, but it gets rather close to software engineering rather than IAM configuration at that point.

Re:Awsviz.dev simplifying AWS IAM policies by tyingq on Wednesday July 10, 2024 @05:42PM (#40931819)
Yeah I'm not saying I can't use it. I'm just trying to explain why people might look at it and feel like it's not unified.