Now please do this for NXDOMAIN on Route53. This can be a big problem with acquired domains.
Amazon S3 will no longer charge for several HTTP error codes
11–20 of 77 posts
Re: Amazon S3 will no longer charge for several HTTP error codes
#12Can't imagine a change like this would be made without some analysis.. would love an internal view into a decision like this, I wonder if they already have log data to compute financial loss from the change, or if they have sampling instrumentation fancy enough to write/deploy custom reports like this quickly.
In any case 2 weeks seems like an impressive turnaround for such a large service, unless they'd been internally preparing to acknowledge the problem for longer
Re: Amazon S3 will no longer charge for several HTTP error codes
#13The system works! Just raise your concerns and they'll get around to it in [checks notes] 18 years https://twitter.com/cperciva/status/1785402732976992417
In the same timespan Microsoft released Windows 1 all the way up to XP
Re: Amazon S3 will no longer charge for several HTTP error codes
#14The system works! Just raise your concerns and they'll get around to it in [checks notes] 18 years https://twitter.com/cperciva/status/1785402732976992417
You made more or less the exact same comment on a recent thread. What does it add to this conversation? https://news.ycombinator.com/item?id=40221193
I did, but I think it's worth stressing that this didn't actually have the quick two week turnaround you might assume if you first heard about it from the billing horror story posted on here recently. It's been known about forever and only became a priority when it turned into a PR issue.
Re: Amazon S3 will no longer charge for several HTTP error codes
#15We've done it. Now let's re-engineer our apps to use error codes for 200 responses and get free S3 usage.
Re: Amazon S3 will no longer charge for several HTTP error codes
#16Can't imagine a change like this would be made without some analysis.. would love an internal view into a decision like this, I wonder if they already have log data to compute financial loss from the change, or if they have sampling instrumentation fancy enough to write/deploy custom reports like this quickly. In any case 2 weeks seems like an impressive turnaround for such a large service, unless they'd been interna…
Are you for real? Legitimately baffled by your comment.
How about the financial losses of customers that could be DDoS-ed into bankruptcy through no fault of their own? Keeping S3 bucket names secret is not always easy.
Re: Amazon S3 will no longer charge for several HTTP error codes
#17Now please do this for NXDOMAIN on Route53. This can be a big problem with acquired domains.
I just searched for this and this documentation entry came up:
https://docs.aws.amazon.com/whitepapers/latest/aws-best-prac...
I can't believe that their 'fix' is to set a wildcard dns entry, this feels somewhat like a joke.
Does this mean that a NXDOMAIN response costs more than a successful response?
Re: Amazon S3 will no longer charge for several HTTP error codes
#18The system works! Just raise your concerns and they'll get around to it in [checks notes] 18 years https://twitter.com/cperciva/status/1785402732976992417
Ahh I see the problem. The steps to get it resolved were not to tell the team about it.
The steps were to raise a big enough fuss that it would undermine customer trust if the team didn't fix it.
Re: Amazon S3 will no longer charge for several HTTP error codes
#19Now please do this for NXDOMAIN on Route53. This can be a big problem with acquired domains.
I just searched for this and this documentation entry came up: https://docs.aws.amazon.com/whitepapers/latest/aws-best-prac... I can't believe that their 'fix' is to set a wildcard dns entry, this feels somewhat like a joke. Does this mean that a NXDOMAIN response costs more than a successful response?
It has the same cost as a successful response which can quickly add up to a few hundred dollars per month with a couple of DNS enumeration scans.
Google Cloud and Azure also bill DNS like this. Unless you need some of the advanced features you really shouldn't host your DNS in the big cloud providers.
Re: Amazon S3 will no longer charge for several HTTP error codes
#20AWS is full of dark patterns. You can sign up for the so-called "free" tier and then too easily, unwittingly enable something that suddenly charges you hundreds of dollars before you know it (by getting a bill at the end of the month), even if you're not doing anything with the service except looking around. AWS doesn't give any warning to free tier members that a configuration change is going to cost you, and their terms are also very confusing. For example, PostgreSQL is advertised as free, but "Aurora PostgreSQL" is quite costly.