131–140 of 293 posts
While I don't like Amazon one but, I appreciate that you don't go into the Evil Big Tech trope. Things at that scale are indeed complicated and hard to coordinate. That said: fuck, that's expensive and poorly explained! Not doing anything cloud without hard limits!
Genius really.
Earlier quoted context omitted.
My team was migrating from one cloud provider to another and I was tasked to go through the soon to be deleted accounts in the old provider and delete resources that we were absolutely sure were serving no purpose whatsoever. You'd wonder why this wasn't something done on the regular. Ended up saving at least $4000 dollars a month. And this was mostly sandbox environments that people forgot about.
I can well believe it, I know in my own team's account I can save hundreds a month and multiple thousands a year. I keep raising this but it's never prioritized as it means taking my time from developing our products Essentially my manager then loses dev time to reduce a bill that due to institutional accounting practices they never actually see!
Earlier quoted context omitted.
There's certainly wastage in large organisations. Over provisioning or keeping that huge S3 bucket full of data from some long forgotten project. I suspect a lot of the huge AWS customers just eat this because it's so hard to mitigate. If a business has hundreds of AWS accounts it becomes very hard to track, and if each account can only shave a few hundred dollars a month off their individual bill then there's very l…
My team was migrating from one cloud provider to another and I was tasked to go through the soon to be deleted accounts in the old provider and delete resources that we were absolutely sure were serving no purpose whatsoever. You'd wonder why this wasn't something done on the regular. Ended up saving at least $4000 dollars a month. And this was mostly sandbox environments that people forgot about.
Earlier quoted context omitted.
> It is very unusual for AWS not to issue refunds in situations like this ...when asked to. But what percentage of mistakes like this end up just being "eaten" by the end-user, not realizing that they can ask for a refund? What percentage don't even get noticed?
I encountered similar situation twice and AWS did not issue a refund both times. I'm avoiding AWS like plague now. Not going to rely on goodwill of support person handling my ticket today.
Why are people still doing the major cloud thing? I just don't get it. The story of "it's easier" is fake. The story of "you won't need highly paid technical experts to maintain things" is fake. The story of "it's cheaper" is fake. The story of "you can't run your own computers it's too complex for ordinary companies to work out" is fake. Its all fake and people still are diving headlong into the clouds, falling thro…
Earlier quoted context omitted.
> do paranoid sweeps of their entire AWS account looking for rogue resources That's the thing that annoys me the most about AWS. There's no easy way to find out all the resources I'm currently paying for (or if there's a way, I couldn't find it). Without an easy to understand overview, it feels like I don't have full control of my own account.
The people who write these tutes have (I imagine) an unlimited budget with some special account which maybe leads to this situation
"Billing alerts" are a joke, give us hard spend limits. Then offer a way to set those limits during onboarding. Building a business on blank cheques and accidental spends is shady. It's also a large barrier to adoption. The more times devs see reports like, "I tried [random 20-minute tutorial] and woke up to a bill for my life's savings and luckily support waived the fee this one time but next time they're coming for…
Dear Customer, You have reached your Configured Maximum Monthly Spend Limit. As per your settings we have removed all objects from S3, All RDS Databases, All Route53 Domains, all ESB volumes, all elastic IPs, All EC2 instances and all Snapshots. Please update your spend limit before you recreate the above. Yours, AWS
It wouldn’t solve the problem for usage-based billing, but it would have solved the problem here.
Earlier quoted context omitted.
Regulate it. Asking Amazon to do something makes little sense. Create laws that force Amazon, and all the rest, to respect their users money. By default, corporations will do what makes them money, not what is ethical or good for the economy.
You trust the government far too much. Regulated industries always end up costing the consumer more. See: medical care and education for examples.