[teaearlgraycold]

I just set up an S3 bucket - probably the most common use case for IAM policies. My policy file was invalid in a way that AWS never warned me about and looked good to my untrained eyes. After a few hours of debugging GPT-4 was able to explain I needed to break up my rules into bucket-level and key-level sections. Afterwards the 403 errors went away.

Just sharing my story. IAM sucks and GPT-4 is a good backup for configuring it.

[Eridrus]

I guess I did not try to deal with anything key related, so that's probably why it was simpler for me.

I do agree that everything about it is horrific, though I'd be surprised and impressed if an LLM were able to generate your key setup from scratch.