How is AWS console so broken?

A developer rants on Hacker News that the AWS Management Console is broken for cross-region S3 bucket replication, citing missing monitoring and a batch operation that cannot select source and destination buckets in different regions. The user reports that Claude Code successfully created and executed the job via CLI without hesitation.

A small rant, after painful user experience. I admit I visited it after a while spending on GCP space, but the console looks like it is either not maintained at all, or individual teams just throwing stuff at it and causing a mess. My simple workflow - I want to copy millions of objects from one bucket in us-east-1 to us-west-1 1. I can kick off the replication rule. but oh wait, there is no monitoring, unless you select it in edit rules. Even then, the experience is broken and I have now no idea if anything is happening in the background. 2. There is batch operation. It doesn't work. If I select source region for aws console, I can't see destination region bucket to execute copy batch. Vice-a-versa, if I select destination region, I can't select any buckets from the source region. I can perhaps use a CLI, which is a long list of instructions to follow and execute without pulling my hair out. I asked claude code to just figure out out to create a job and execute it and tell me the state. It didn't even hesitate. Comments URL: https://news.ycombinator.com/item?id=49531472 https://news.ycombinator.com/item?id=49531472 Points: 1 Comments: 1