Jeff Barr acknowledges S3 unauthorized request billing issue | Hacker News Reader

Jeff Barr acknowledges S3 unauthorized request billing issue

old.reddit.com

63 pointsbelter18 comments

Open articleView on HN

Better late than never I suppose

https://twitter.com/cperciva/status/1785402732976992417

AWS will always do the right thing...After they have tried everything else? :-)

They'll do the right thing after the issue blows up on HN/Twitter and makes them look bad, but no sooner.

This is why transparency leads to responsibility, which leads to good outcomes.

True for private corporations, true for gov'ts.

Very American.

It's called Distributed-Denial-By-Bill, a service provided by your [name cloud year].

Better now than sooner I suppose since they got to collect for all those unauthorized access 'uses'. And by reacting 'swiftly' now that it has come to their attention, come out looking like a good player. If they really felt bad about it, there should be retroactive credits at the least.

It's not enough. They should refund customers for all such requests that they billed for.

> whoa there, pardner!

> Your request has been blocked due to a network policy.

Reddit, like Xitter and Instagram and other popular venues of online discussion, have really been enshittified out of being good internet participants. Presumably the purpose of the post in the article is to publicize something, but the site operator has decided (for some reason I'm not prepared to work out) that I'm not allowed to see it.

At least newspapers don't have rules about who is allowed to buy them.

Using a VPN? Reddit has been cracking down on them, probably because they've pivoted into selling their data to AI companies and they want to deter industrial-grade scraping which comes from the same IP ranges as most VPN providers.

I don't agree with reddit's decision, but you can still use a VPN if you have an account.

It’s dishonest to not disclose what esoteric networking / system configuration is causing this, because it’s blindingly obvious from your outsized reaction that this is the case.

I'm am sorry that you were blinded by my reaction. I don't know if it counts as esoteric, but it's probably my Proton VPN connection through Germany that made the server decide not to serve the page. Whether that's "the cause" or not is a matter of opinion.

It still used to work with the "old" sub domain, but no more.

Is this applicable to public & private buckets alike? Like if I keep making requests with the wrong token?

Yes. If a request is unauthorized, the bucket owner pays for the API operation anyway.

In case you missed it: https://news.ycombinator.com/item?id=40203126

hn post which leads to reddit which leads to twitter smh

Reply on news.ycombinator.com