consoleme VS iamlive

Why are you using (very expensive) GPT, or any LLM for that matter, when this was already a solved problem using rulesets? Netflix for example has open source that does this already: https://github.com/Netflix/consoleme

Instead of analyzing your code, you just run your code with no permissions and it automatically detects permission failures and thens open those permissions, with a UI showing you what it did so you can remove any permissions you don't want.

That actually seems much more secure than trying to divine the rules from reading the code.

What value is the LLM adding here?

You may also want to look into Netflix’s ConsoleMe https://github.com/Netflix/consoleme

This is the way. I’ve seen this happen countless times. It’s happened to me too. It’s happened to colleagues.

The worst case I’m aware of from first-hand knowledge was a large cluster of resources that got deployed for a product demo by a sales engineer and forgotten about. Turned into a nice ~$100,000 surprise in the quarterly budget.

Netflix built a tool for managing IAM permission requests as an auditable workflow, called ConsoleMe: https://github.com/Netflix/consoleme

There’s this tool as well https://github.com/Netflix/consoleme among others, check them out and see if the overhead is ok for you all now, but keep it simple to start.

Perhaps Consoleme from Netflix is a useful tool for you?

For sure, you can DM me. Might want to check out https://github.com/Netflix/consoleme too

The tool is in a similar space to iamlive, policy_sentry, and consoleme (all of which are worth checking out too if you're interested in making AWS security easier) but the main points of difference I see are:

After you read the resources, you can stand on the "shoulders of giants" https://github.com/Netflix/consoleme

Also things like this (same guy) if you have a sandbox to play in with wider permissions and are trying to build a more scoped profile: https://github.com/iann0036/iamlive

I know there is a tool called iamlive that logs all API calls on your local machine. So you can run commands as an admin user locally while this is running, and find out what permissions were needed. Then you tear down the infra you just deployed, and add those same permissions to a service user of some kind (e.g. a CICD role) to avoid over-privileging it. It's messy but it can be helpful.

actually Ian (aws hero) has a tool that does exactly this

https://github.com/iann0036/iamlive

I have used https://github.com/iann0036/iamlive with great success in the past. On high level, the approach you are describing is iamlive on steroids and UX improved.

Kudos on launch, will check your beta

Thanks! Permissions are determined per resource or datasource. There's no easy way that I had found, especially if you want this done statically, https://github.com/iann0036/iamlive does it by inspecting your api calls but there's always a look up somewhere. Hopefully ill manage to get a few community contributions and get the ball rolling, i've made it as easy as I could to add support for other resources without you even really having to know golang.

IAM isn’t fun, but there’s lots of options.

https://pypi.org/project/access-undenied-aws/ will allow you to start with least privilege and fix specific issues.

https://github.com/iann0036/iamlive allows an admin to perform the action via CLI and capture the policy.

Access advisor can inspect how you actually use the role and give suggestions on what to remove.

A more helpful suggestion is to experiment with these tools and then find gaps in IAM actions and submit those as feature requests via your TAM.