The scariest thing to me about AWS is that I might accidentally bankrupt myself while I learn to use it. – tieTYT
Welcome to this post, where we’ll be diving into some of the most frightening and costly AWS horror stories.
It’s no secret that AWS can be a powerful tool for businesses, but it can also be a dangerous one. One of the scariest things about AWS is the potential for accidentally racking up a huge bill while you learn to use it.
Unfortunately, there are plenty of real-world examples of this happening, as AWS doesn’t provide strict ways to restrict consumption on accounts.
These horror stories can not only be painful for your savings, but also compromise your secure posture. Join us as we explore some of the most shocking tales of AWS gone wrong.
- $300k bill after AWS account hacked!
- 34k $ billing, what the actual fuck?
- 15k bill after 3 years of unknowingly having aws running.
- Can’t pay 10k aws bill
- My forgotten account has a $20,000 bill, how screwed am I?
- I am charged ~$60K on AWS, without using anything
- Hacked AWS Account is facing $200,000+ in charges after support ticket
🏴☠️ YC - Hacker News
Dev gets $4000+ AWS bill overnight.— flavio (@flaviocopes) June 29, 2022
Is this our collective nightmare? pic.twitter.com/ONHMQjotek
Good morning, $2700 AWS bill!— Chris "Not So" Short (@ChrisShort) July 4, 2020
Can we acknowledge how ridiculous it is that startups and even individuals can bankrupt themselves...— Gergely Orosz (@GergelyOrosz) June 28, 2022
... with an AWS bill?
I cannot fathom why Amazon does not do anything meaningful to allow setting e.g. limits on accounts. Why do we need to hear stories like this on repeat? pic.twitter.com/B7EMYPXA0j