An AWS IAM Security Tooling Reference

Re:An AWS IAM Security Tooling Reference by dangus on Monday August 26, 2024 @11:15PM (#41364290)

Hmm, that’s interesting. This sounds more like an organizational structure and ownership problem than a code problem to me.

I’ve been at multiple companies where we’ve decided to build a set of modules that could be used somewhat universally for products, and then we’d basically say “hey if you don’t want to use this, either convince us that your needs are justified or do whatever you want and DevOps/SRE can’t support you.” Some of it we went as far as calling self-service.

If you have a menu of options than people can’t pick things that aren’t on the menu.

I also find that developers really just shouldn’t have almost any cloud infrastructure rights, with few exceptions.

You could also go the embedded SRE/DevOps route where the embedded infrastructure engineer on the product team can steer each separate product into following more standard approaches.

I’m also going to take a wild guess that your ops to developer ratio is too low.

[ Parent | on HN ]

Re:An AWS IAM Security Tooling Reference by tchalvakspamm on Tuesday September 03, 2024 @11:48AM (#41436106)

So youuuuu’re the person who creates the obstacles to actually getting anything done at many of the organizations I have worked at.

“We only have 3 menu options of ways to do things” is great for creating hierarchies, and rarely works for actually creating any innovation.

[ Parent | on HN ]