This is a great and chilling article from @QuinnyPig about a tragedy waiting to happen because of @awscloud free-tier service ( not really free) .
People hurting themselves over financial predicaments happened a lot, and it can happen to AWS users.
lastweekinaws.com
People hurting themselves over financial predicaments happened a lot, and it can happen to AWS users.
lastweekinaws.com
Surprise AWS bills can hit you in ways you don't expect, even excluding obvious faults like compromised accounts. I put multiple budget alerts on my AWS account for limits like 100$,500$,1K$ and yet I received a surprise bill of 14K USD!
Ask me how:
Ask me how:
I simply did a test for a customer using a scenario that will cost around 1000 to 1500 USD, so when my billing alerts showed up for 500 and 1K USD, I was comfortable because I expected it.
I then failed to verify the infrastructure was stopped (I restarted by mistake)
I then failed to verify the infrastructure was stopped (I restarted by mistake)
I usually ping my infra to be sure it stopped, and the pings timed out (because I restarted them not stopped) so I thought all is well, and logged off.
Little did I know it restarted and kept running, and I didn't have billing alerts beyond 1000 $.
So they kept racking $$$
Little did I know it restarted and kept running, and I didn't have billing alerts beyond 1000 $.
So they kept racking $$$
Until I received a failed credit card transaction for about 14000 $.
Luckily I was able to prove to AWS support through cloudtrail logs that this was made in error and for unused infrastructure, so after a month they canceled it all out.
Always set exaggerated billing alerts
Luckily I was able to prove to AWS support through cloudtrail logs that this was made in error and for unused infrastructure, so after a month they canceled it all out.
Always set exaggerated billing alerts
جاري تحميل الاقتراحات...