I wish AWS had hard spending limits. Azure have one - you spend over the set limit(probably per billing account?) and your services are suspended. Already saved my from unexpected bill this month.
Just setup billing alarms. Spend is reported continuously. These people surprised by end of month bills just aren’t paying attention to all the data AWS shows you on your spend. If they hard shut people down then people would be posting “AWS turned off my services and took my site down blah blah blah”
My First AWS “Free Tier” Hosting Bill Was $990
31–40 of 63 posts
Re: My First AWS “Free Tier” Hosting Bill Was $990
#32I am less surprised that the mental model fell apart. I guess a lot of people think cloud resources are something that is efficiently shared (consider S3, you pay per byte you store, store 0 bytes, pay $0). But that's actually a rare case, most of the time you are provisioning something for your exclusive use; if you have a database server it costs you the same whether it's doing 10000 transactions per second or sitting completely idle and never logged into.
(Incidentally, the true sharing model used to be popular. Shared hosting with no isolation between tenants predated AWS by a decade. You got a chunk of a computer and shared Apache, MySQL, and PHP with hundreds of other randoms. Very cheap!)
Re: My First AWS “Free Tier” Hosting Bill Was $990
#33If using AWS for personal use the first step should always be to set up a billing alarm. https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitori... It’s very helpful. You can still end up overspending but at least you get an email within a day letting you know what’s going on, which can solve a lot of the cost overruns by giving you a chance to act quickly and only get hit with 1/30 the monthly fee.
Re: My First AWS “Free Tier” Hosting Bill Was $990
#34I completely wasted $500 of free google cloud credit from having a 2 core Windows VM "idling" for a couple of days... thank god I checked the balance
Re: My First AWS “Free Tier” Hosting Bill Was $990
#35That said? This article rubs me the wrong way. The suggestion that this problem is caused by "dark patterns" and Amazon being misleading about "pay as you go" screams FUD to me. The screenshots provided right in the article clearly show that what was being done wasn't eligible for free tier. And not understanding that launching a resource, regardless of whether or not you're interacting with it, is consuming the service which launches the resource is a problem with the user, not the marketing. Yes, the author admits that they didn't scrutinize, but that doesn't excuse the position of the article that AWS is somehow doing this to intentionally bilk people.
Re: My First AWS “Free Tier” Hosting Bill Was $990
#36TL;DR: Misleading title. Amazon service came through. * Author clicked through Amazon UI/UX, and ended up with a huge bill. * The UI/UX was confusing and poorly designed -- at no point was he shown he'd pay anything, let alone a lot. * He was refunded the money AND given credits to make up for the hassle. This is one of my key frustrations with Amazon. (1) I'd like services like RDS or similar on a pay-as-you-go fash…
Re: My First AWS “Free Tier” Hosting Bill Was $990
#37AWS should have kept their money and OP should've learned their lesson proper.
Re: My First AWS “Free Tier” Hosting Bill Was $990
#38If we are trading war stories: I was playing around with some tutorial to learn something (probably something cool like programming your own robotic drone using functional erlang or whatever), pushed to github and went to sleep. Woke up a few short hours later and had lots of emails about the machines I was spinning up. Checked and saw that my account had wracked up thousands of dollars overnight (I think 6-8 hours),…
So you’re not as alone as you think, and these aren’t from people trying to learn something, it’s from big enterprise IT organisations.
Re: My First AWS “Free Tier” Hosting Bill Was $990
#39Re: My First AWS “Free Tier” Hosting Bill Was $990
#40If using AWS for personal use the first step should always be to set up a billing alarm. https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitori... It’s very helpful. You can still end up overspending but at least you get an email within a day letting you know what’s going on, which can solve a lot of the cost overruns by giving you a chance to act quickly and only get hit with 1/30 the monthly fee.
Why is this an extra step instead of something AWS always does? As both services and permissions multiply, the user experience of AWS is getting worse and worse. How would you even know to setup CloudWatch if it’s your first time using the service?
Why is it an extra step to set a timer when you turn the oven on? Just set it to 60 minutes.
Why doesn't every toothbrush beep when you didn't brush long enough?
Why aren't the police keeping track of my children when they go outside?