News for hackers. Stuff that matters.

A comment on I returned to AWS, and was reminded why I left. Parent comment

Re:I returned to AWS, and was reminded why I left by Aperocky on Sunday May 10, 2026 @09:31PM (#48090071)
They are just some slight variation of the fundamental idea. For example resource policy and org SCP are just the same check on a different level (e.g. more of who has access to what). They are attached to Organization and individual resource respectively (vs Account) so they need to exist in a separate place. And then in use they are ALL checked before an access is granted.

I don't work for IAM but I worked for several other teams over the years and IAM is actually one of the least confusing services. But I am definitely biased and have more than average amount of experience on this particular subject. I still think the general idea is more sane than Azure Account for example. I do think this reflect on the philosophical level where whether cloud are building blocks or are they consulting projects. I personally think IAM is done right in that regard.

[ Parent | on HN ]
Re:I returned to AWS, and was reminded why I left by amluto on Sunday May 10, 2026 @10:53PM (#48090567)
> And then in use they are ALL checked before an access is granted.

I know they’re all checked. What don’t know is how the results of those checks are combined to get the final result. As far as I can tell, the result is not something like OR or AND — it seems like it’s something exceedingly complex and that the output of the policy part may be more complex than just a Boolean value.

Maybe the underlying implementation is fantastic (and my distinct impression is that AWS takes this stuff far more seriously than Azure), but that doesn’t mean that the docs are easy to find or that the system actually makes sense in anything other than an agglomeration-of-backwards-compatible-layers sense.

[ Parent | on HN ]
Re:I returned to AWS, and was reminded why I left by jtoberon on Wednesday May 20, 2026 @09:43AM (#48207661)
The output is Allow or Deny. To be Allowed, you need an policy that includes an Allow statement. If you don't have one, then the result is implicit Deny by default. Also, any explicit Deny wins over all Allows. Disclosure: I work on AWS IAM.
[ Parent | on HN ]