News for hackers. Stuff that matters.
Re:Awsviz.dev simplifying AWS IAM policies by icedchai on Wednesday July 10, 2024 @09:09AM (#40926470)
The main problem is it's a huge time suck. When writing IAC like Terraform, you'll probably spend more time configuring IAM roles and permissions than you do the actual infrastructure. Also, in my experience, nobody reviewing your code will check if it's correct, least privilege, etc. And when you get it wrong (too restrictive), the error messages can be difficult to diagnose, depending on the service. So most people will err on the side of more permissions than needed.
Re:Awsviz.dev simplifying AWS IAM policies by presspot on Wednesday July 10, 2024 @12:01PM (#40928342)
I have hard this from many developers. Are there any good solutions or best practices I should look into?
Re:Awsviz.dev simplifying AWS IAM policies by guiriduro on Thursday July 11, 2024 @03:25AM (#40934408)
For the security sanity checking of terraform infra code, take a look at Checkov.
Re:Awsviz.dev simplifying AWS IAM policies by turtlebits on Wednesday July 10, 2024 @01:59PM (#40929580)
Don't use Terraform? If you want to create individual resources one by one, go for it. Use something like CDK which abstracts a lot of the boilerplate away.
Re:Awsviz.dev simplifying AWS IAM policies by icedchai on Wednesday July 10, 2024 @02:55PM (#40930170)
I wound up with a job at a TF-heavy company. I personally despise Terraform. The language is anemic and there's too much copy-paste code.
Re:Awsviz.dev simplifying AWS IAM policies by sgarland on Wednesday July 10, 2024 @06:48PM (#40932244)
…and compiles into CloudFormation, which is of the devil.

I also have issues with infrastructure being declared imperatively. I’ve seen countless bugs and incidents caused by CDK surprises.

You get precisely what you ask for with a declarative language.