News for hackers. Stuff that matters.

A comment on Amazon S3 will no longer charge for several HTTP error codes. Parent comment

Re:Amazon S3 will no longer charge for several HTTP error codes by SushiHippie on Monday May 13, 2024 @03:38PM (#40347414)
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?

[ Parent | on HN ]
Re:Amazon S3 will no longer charge for several HTTP error codes by aeyes on Monday May 13, 2024 @03:44PM (#40347488)
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.

[ Parent | on HN ]
Re:Amazon S3 will no longer charge for several HTTP error codes by technion on Monday May 13, 2024 @04:11PM (#40347808)
Cloudflare don't bill like this, part of why I moved off route 53.
[ Parent | on HN ]
Re:Amazon S3 will no longer charge for several HTTP error codes by withinboredom on Monday May 13, 2024 @04:33PM (#40348079)
Neither does Digital Ocean, for that matter.
[ Parent | on HN ]
Re:Amazon S3 will no longer charge for several HTTP error codes by beeeeerp on Tuesday May 14, 2024 @09:04AM (#40354804)
That’s not entirely true - aliases to AWS resources are free (their suggested “workaround”).
[ Parent | on HN ]