5 ms·
I know experienced people who have woken up to several thousand dollar AWS bill they didn’t expect. And the large cloud providers have clearly indicated by thei
by ghaff 5y ago
I know experienced people who have woken up to several thousand dollar AWS bill they didn’t expect. And the large cloud providers have clearly indicated by their actions that they’re simply not interested in implementing hard cost circuit breakers.
I use AWS very lightly but I totally understand why someone wouldn’t.
- user3939382 5y ago> the large cloud providers have clearly indicated by their actions that they’re simply not interested in implementing hard cost circuit breakers. I agree, my term for this is “bad faith”. I recently had a free $200 credit for Azure. I setup their default MariaDB instance for a side project, figuring I’d get my feet wet with Azure. I didn’t spend time evaluating the cost bc I figured, how much could the default be if I haven’t cranked up the instance resources at all? Turns out the answer is more than $10/day which I discovered when authentication failed to my test DB. Back to Digital Ocean.
- ghaff 5y agoMy term for it is “you’re not their use case.” For better or worse, they’ve prioritized usages that would much rather have an unexpected few thousand dollar bill than have services paused or shutdown unexpectedly.
- civilized 5y agoBut computers can behave differently based on user choice. Right? So there could be a user option to cut service beyond a fixed spend. It wouldn't be hard to implement, and tons of people would use it. They don't do it. It's not a tragic case of priority and limited engineering resources. They like surprise bills, just like hospitals do. Businesspeople love it when you come to their service and click through their Russian novel of a service agreement that would take a team of lawyers to parse. Once you do that, your money belongs to them! It's their court, their rules! They love it!
- nucleardog 5y ago> It wouldn't be hard to implement, and tons of people would use it. They don't do it. Please describe to me, in detail, how this works. Because every time this comes up everyone claims it's the easiest thing in the world, but if you try and drill into it what they end up actually wanting is generally "pay what you want" cloud services. There are a _ton_ of resources on AWS that accrue on-going costs with no way to turn them off. A "hard circuit breaker" that brings your newly accruing charges to zero needs to not just shut down your EC2 instances, but delete your EBS volumes, empty your S3 buckets, delete your encryption keys, delete your DNS zones, stop all your DB instances and delete all snapshots and backups, etc, etc. The only people I see using a feature like this are some individuals doing some basic proof-of-concept work and... a bunch of people that are going to turn it on not understanding the implications and then when they get a burst of traffic that wipes out their AWS account they're going to publish angry blog posts about how AWS killed their startup. If, like most people, you don't want literally everything to disappear the first time your site gets an unexpected traffic spike, you can already do this by setting up a response tailored to your workload--run a lambda in response to billing alerts that shuts down VMs, or stops your RDS instance but leaves the storage, etc.
- void_mint 5y ago> Because every time this comes up everyone claims it's the easiest thing in the world, but if you try and drill into it what they end up actually wanting is generally "pay what you want" cloud services. Why is it on any (usually a relatively new) user to define how an entire cloud should behave? Users are asking for a feature that helps them stop accidentally spending more than they intended. This feature request is totally fair. Implementing such a feature would be an act of good faith towards new/onboarding users (also obviously just any user with a very specific budget use-case). > The only people I see using a feature like this are some individuals doing some basic proof-of-concept work and... Yes exactly. GCP offers sandboxed accounts for this exact purpose. Why is this such a far reach? > setting up a response tailored to your workload--run a lambda in response to billing alerts that shuts down VMs, or stops your RDS instance but leaves the storage, etc. If you're telling every individual user that falls into a specific category to build a specific set of infrastructure, why is it not acceptable to you to just ask AWS to build it?
- deleted 5y ago[deleted]
- whoknew1122 5y agoIt's not bad faith. It's 'providing the resources you signed up for'. Does it mean you have to go into your planning with more consideration as to cost? Yeah. But how would you feel if your start-up finally goes viral, you're having your best day ever, and then your app just stops working because someone forgot to remove a hard spend limit? Most people would rather see their app continue running. And what does turning off the lights look like? If your database hits your cost limit, do you stop serving requests? Delete the data? To what extent do you want 'cost protection' for resources you signed up for?
- imwillofficial 5y agoIt’s not unreasonable to ask for a mechanism to not be billed thousands unexpectedly. Cloud billing is not easy to understand. I would know, I work for the part of AWS that calculates people’s bills.
- whoknew1122 5y agoIt's not rocket science, either. I would know, I work for premium support. Every time I see an unexpected bill of thousands of dollars, it's because the customer poorly architected their infrastructure. People seemingly want the freedom of complete control without the responsibility that comes with having that much control.
- deleted 5y ago[deleted]
- nlitened 5y ago> If your database hits your cost limit, do you stop serving requests? Delete the data? To what extent do you want 'cost protection' for resources you signed up for? Sounds like a reasonable configurable option rather than “you shouldn’t be able to choose at all”.
- eropple 5y ago
- TriNetra 5y agoYes in some cases the default is quite expensive – the same was there with SQL Azure (though they have changed that recently) and it had created a good amount of bill for us (though for their credit, Azure did refund in all such occasions because we didn't use the capacity at all). However, I don't know why the alert system doesn't have an option to say "here's my budget, alert me as soon as when my daily pace is set to exceed the monthly budget" instead, you have % of budget amount consumed based alerts, like you can get email if you say 50% of my budget is consumed, which happens every month so kinds of defeat the purpose of an alert. We ended up creating a simple solution (cloudalarm.in – in beta) that provides such budgeted pace based alert and more ways to get instant alert which isn't possible with usage based alerts.
- geoduck14 5y agoYup. I used AWS at my last job. We had teams of people using AWS, we had fancy 3rd party tools and extraction metrics to track and report on costs. There were still PLENTY of times when I would just scratch my head "well it looks like EC2s cost an extra $1000 this month. I wonder what happened"
- nucleardog 5y ago> And the large cloud providers have clearly indicated by their actions that they’re simply not interested in implementing hard cost circuit breakers. Since I enjoy tilting at windmills--how do you propose this works? Like, in detail. Because every time I try and drill into details of this with someone, it winds up what they really want is "pay what you want" cloud services. AWS is much, much more than just a place to run a virtual server and many resources accrue on-going costs with no way to "turn them off". When you hit your hard circuit breaker, do they delete all your EBS volumes and data in S3? Your private SSL root? Your user directory? Encryption keys? DNS zones? The number of people that would want all of that removed when they hit their $X/mo limit is likely minuscule in comparison to the number of people that would turn this on not understanding what it really meant and then publishing angry blog posts about how Amazon killed their startup right when they got popular and traffic spiked.
- alexeldeib 5y agohttps://docs.microsoft.com/en-us/azure/cost-management-billing/manage/spending-limit#reaching-a-spending-limit https://docs.microsoft.com/en-us/azure/cost-management-billi... e.g. "virtual machines are stopped and de-allocated. The data in your storage accounts are available as read-only." Most control plane operations will also be blocked. It gets complicated with more complex resource types, but it gets the job done anyway. Note that this functionality is sort of required to support pre-paid plans without allowing them to exceed specific limits, which do exist on Azure. So there's a business dependency on this functionality today, it's not a hypothetical.
- ghaff 5y agoThat wasn’t a value judgement on my part. I’ve made the exact same comment as you previously.
- yjftsjthsd-h 5y agoGive me a page in billing listing everything that can use money, let me enable/disable them manually (this is mostly to allow restricted dev accounts) and select which, if any, should be allowed over the bill total I set. Opt-in, but yes, do let me kill every EC2 instance if I choose.