3 ms·
Can you share the gory details so we can learn more about this? It would be interesting to study what happened, in detail. Perhaps there was a misconfiguration?
by movedx 4y ago
Can you share the gory details so we can learn more about this? It would be interesting to study what happened, in detail. Perhaps there was a misconfiguration?
- sleepyhead 4y agoI made a video about it but it is not published yet. I hope to publish it soon here: https://www.youtube.com/channel/UCkc8xf5A7qCQydN6tG0BmmQ https://www.youtube.com/channel/UCkc8xf5A7qCQydN6tG0BmmQ There was no misconfiguration, just millions of DNS requests but not millions of actual users. I was in contact with AWS support multiple times. The only solution was so use AWS Shield Advanced. They did refund most of the charges but it was too risky for me. Even after I moved DNS provider there was DNS requests to the R53 zones. I can highly recommend https://dnsimple.com https://dnsimple.com though.
- movedx 4y agoYeah, the problem is, dnsimple.com isn't going to NOT charge you for the same thing. They have T&Cs too. I'm guessing AWS refunded close to 100% of fees associated with provable bad DNS requests.
- sleepyhead 4y agoWhy is it a problem that dnsimple is not going to charge for bogus DNS requests? (or any DNS requests for that matter). AWS did do a refund but it requires me to monitor usage and do some investigation. I really don't want to spend time monitoring DNS requests.