I've recently faced an overwhelming situation where a DDoS attack led my AWS S3 account to rack up a staggering bill of $15.5k for data transfer. After opening a support case, AWS kindly reduced the bill to about $10.5k, which I appreciate, but it's still far beyond what I can afford. I was really hoping the final amount would drop to something manageable, like $100–$200, but that's not the case. I've already reached out to AWS for further reconsideration, but I'm looking for any additional advice or alternative steps I can take. Has anyone here experienced a similar situation and found a way to negotiate for a further reduction? What are the potential consequences if I can't pay this? I'm quite anxious about it, so any helpful advice would be greatly appreciated. Please keep the comments constructive!
3 Answers
From what I've heard, AWS usually expects you to pay the entire bill even in situations like this. I suggest you approach them directly and propose a settlement plan, stating that you can't afford the full amount and can only manage to pay around $300 or $500. Being upfront about your financial limitations may help.
I think your best bet is to keep negotiating with AWS support to see if there’s any room for additional reductions. Also, I'd highly recommend using CloudFront with S3 moving forward; it provides an extra layer of protection against such issues.
Honestly, I thought AWS would be a bit more forgiving in these types of situations. It seems like major cloud providers have zero flexibility on these matters, and it's a risk everyone should be aware of when deploying anything online. Just remember, if your bucket is public, DDoS attacks can hit you hard, no matter what.
AWS has definitely shifted gears from being customer-friendly to focusing on profits now. It’s not like the old days where they would just waive charges.
Yeah, I told them the same thing. I can handle some payment, but certainly not what they initially billed me!