AWS IAM

“IAM is still a nightmare on both GCP and AWS”

“a pain in the ass to manage”

“The policy framework is everything that explains why formal methods has gotten very little traction”

“Except for IAM that was a huuuge struggle.”

“You don't want to spend 2 hours in the IAM and Role control panels?”

“they warn the shit out of you multiple times”

“cannot be easily done for IAM permission reasons”

“IAM - the hideously complex auth and access rules system”

“It's complex but still easily understandable to get the basics.”

“With IAM it's more like "I'm pretty sure I figured out the right silly-walk for X…”

“the system actually makes sense in anything other than an agglomeration-of-backwards-compatible-layers sense”

“I personally think IAM is done right in that regard.”

“having to iterate, one at a time, through the five hundred and thirty seven new permissions you need to grant”

“imposing worst-case complexity on the 99% of people who will never benefit”

“the big problems with amazon IAM is not that it’s inherently complex…”

“It's literally a JSON policy document.”

“Like you said with IAM, I think it just slowly evolved into the mess it is today”

“It has grown organically and is complicated, just as any other policy language.”

“fundamentally it is one input into a huge mess that you cannot actually see or audit from a 10k foot level”

“IAM is unnecessarily bad. I recently had to set a trivial policy, and was doing it correctly.”

“IAM is I think good, logical and granular enough.”

“All of them evolve into monstrosity because of so many conflicting requirements”

“IAM is just complex. I can't think of any implementation”

“IAM is my favorite part of AWS.”

“So much easier to use IAM policies.”

“I’m not convinced that anyone knows how IAM rules and policy rules interact.”

“AWS IAM is extremely well designed when you compare it with the spaghetti monster IAM systems of other clouds”

“+1 on the IAM over engineering, though to AWS credit, I suspect it was evolved rather than design”

“some services fail to achieve the "static stability" you describe”

“IAM going poof due to it being dependent on us-east-1”

“IAM which is always a pain anyway”

“incredibly powerful. It solves this exact problem very well.”

“IAM comes to mind, with fine grained control over everything.”

“it's straightforward to say e.g. "permit traffic on port X from instances holding IAM role Y”

“AWS, GCP, and Azure handle fine-grained access well.”

“If the IAM in us-east-1 goes down, every non-public object or workload that needs any kind of AWS authentication will fail immediately.”

“AWS IAM has caused multiple cross-region outages.”

“That product makes me feel dumb every time I use it”

“IAM is a better set of semantics for securing your infrastructure”

“I've always found AWS IAM quite simple, but then again it is my job”