Inadvertent public buckets leading to data loss is what created those hoops. Trying to take the ammo out of the footgun.

https://www.theregister.com/2022/12/14/aws_simple_storage_se...

You really need to think carefully about whether you want to expose an S3 bucket publicly. There are probably some valid reasons out there, but if you're not an AWS expert, it's likely that you're making a mistake. If I find out the name of your bucket I could cost you thousands of dollars of egress tonight before you wake up in the morning. It's _especially_ likely to happen to hosters of open source binaries because of people absent-mindedly downloading artifacts from CI jobs. No malice required. They make the mistake but you pay the bill.

Given the amount of data breaches that have happened from S3 buckets being accidentally publicly accessible, it definitely makes sense to me.