Interesting. It takes me exactly 2 steps.

terraform plan && terraform apply

Terraform that shit bro.

Maybe through the GUI, it's a single step with the CLI.

Please elaborate. How is this achieved in one step with the CLI?

Well, you'll have a two-hundred line IAM policy and a half-dozen API calls encoded into a script, but once you have that script its just one step! All you do is run the script!

And if something in the script goes wrong midway through, you've automated a big mess! I love it!

Really should, I've always thought AWS was just a bunch of hacked together services and it kinda shows. This is why you don't let the engineers talk to the customers... er design for the customers.

With this.

https://github.com/salesforce/policy_sentry

(Disclaimer: I am the author)

Not one step exactly, but it is by far the easiest way to write least privilege IAM policies. Otherwise, it becomes impossible to ensure IAM policies are written securely and at scale. This way, all custom IAM policies are written with the exact same methodology.

Not OP but pretty sure they just mean this

`aws s3api create-bucket --bucket somecoolname --region us-west-2 --grant-write iamuser`

And now a single user has access, such scalability!

Well technically this could also be a group.

I don’t know why all the hate for IAM permissions here.

They are complicated but also extremely powerful if setup correctly.

We manage all of our IAM policies and groups with terraform and it’s incredibly easy to understand imho

Hella hate. Personally I found grappling with what they were initially difficult but then I finally dug in and watched howto propaganda...great job whoever did that at amazon. It’s the one thing I don’t hate about the company. [1]

It’s a ton easier for on boarding and giving contractors temporary access to resources.

*former worker at 3rd party merchant

[1] https://www.aws.training/LearningLibrary

If you think that effectively making a few json files, doing a crs on them and deploying via cloudformation is a difficult process, maybe you'd like to provision a server for storage and authorize access in a more simple way?

I think you just proved OPs point. For tons of simple use cases for S3 (nowhere near the complexity/flexibility of running a server), what you described is complex. You just hand waved over what has become obvious to you after experience (correct json schema, crs, and knowing to use cloud formation and how to use it).