Amazon S3 will no longer charge for several HTTP error codes

Re:Amazon S3 will no longer charge for several HTTP error codes by beeeeerp on Monday May 13, 2024 @09:28PM (#40350642)

It’s still a huge problem for people that have purchased domains. I bought one that apparently used to be a BT tracker, and gets on the order of several hundred NXDOMAIN requests per second.

I understand it’s still hitting Route53 infrastructure, but I’m not using it, and it’s not commonplace to charge for NXDOMAIN records. Because of this, I’m unable to host at AWS (prohibitively expensive for my use-case).

It’s worth mentioning that DNS infrastructure for things like this are very cheap (I used to self-host the DNS infrastructure for this domain for ~$2.5/mo), so the up charge is even worse that what AWS is charging for bandwidth. If they brought it in line with actual costs, I wouldn’t have as much of a problem.

[ Parent | on HN ]

Re:Amazon S3 will no longer charge for several HTTP error codes by paulddraper on Monday May 13, 2024 @10:10PM (#40350956)

A book could be written about AWS "overcharged" services

[ Parent | on HN ]

Re:Amazon S3 will no longer charge for several HTTP error codes by beeeeerp on Tuesday May 14, 2024 @12:38AM (#40351655)

Totally agree with this. In their defense (not that I like it), obviously the market is willing to pay what they charge. It’s unfortunate that the other big cloud providers haven’t driven prices down that much.

[ Parent | on HN ]