Hacker News Reader

Comment by sherburt3 | Hacker News Reader

I believe they changed that shortly after that blog post went viral: https://aws.amazon.com/about-aws/whats-new/2024/08/amazon-s3...

View on HN

I raised that exact same issue to AWS in ~2015 and even though we had an Enterprise support plan, AWS response was basically: well, you problem.

We then ended up deleting the S3 bucket entirely, as that appeared to be the only way to get rid of the charges, only for AWS to come back to use a few weeks later telling us there are charges for an S3 bucket we previously owned. After explaining to them (again) that this way our only option to get rid of the charges, we never heard back.

You have to wonder how many people quietly got burned by that in the 18 years between S3 launching and that viral post finally prompting a response.

Seems an interesting oversight. I can just imagine the roundtable, uhh guys who do we charge for 403? Who can we charge? But what if people hit random buckets as an attack? Great!

> Seems an interesting oversight. I can just imagine the roundtable, uhh guys who do we charge for 403? Who can we charge? But what if people hit random buckets as an attack? Great!

It is amazing, isn't it? Something starts as an oversight but by the time it reaches down to customer support, it becomes an edict from above as it is "expected behavior".

> AWS was kind enough to cancel my S3 bill. However, they emphasized that this was done as an exception.

The stench of this bovine excrement is so strong that it transcends space time somehow.

Even pooper is upset about the stench. Tech is fuckin dumb in the corps, the only logical explanation to me is kickbacks to the CTO or similar.

Pooping at the job is one thing but pooping at the job and trying to sell it as a favor to the customer is a whole different game.

you don't need kickbacks at this level. They're all judged by their 6-month outlook on revenue and their market shares.

This is just obfuscating grift justified by the "well, you own the severless functions!"

> I can just imagine the roundtable

That's the best part!

The devs probably never thought of it, the support people who were complained to were probably either unable to reach the devs, or time crunched enough to not be able to, and who as a project manager would want to say they told their Devs to fix an issue that will lose the company money!

BS, I can't imagine that not a single developer entertains this scenario and voices concerns.

Reply on news.ycombinator.com