51–60 of 293 posts
There's a reason there are very well paid positions in companies to guide colleagues on how to use AWS cost-effectively and with lower risk.
I think its all hiding the fact that people don't want to take the time to design (and maintain) scalable infrastructure and instead rely on fake abstractions that pretend to be infinite, always-available, magic, or w/e. I'm sure there is some open source software that helps here.
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 billing department knows exactly what you were running, but they only tell you once a month...
It is sad experience but I disagree with the author here > It’s so difficult to be paranoid about every single technology you use. I would be paranoid with anything related to AWS, I don't want to risk my bankruptcy (or near bankruptcy experience) on small mistakes or the goodwill of the AWS support.
ever since I learnt self-hosting, it feels so liberating
_Learnt_ self-hosting? You mean people this days start from the cloud as a default? …ah, yeah, right. Damn I’m old.
They lead young devs into their framework and make them believe that the only way to serve their sites is through them, and to pay their extortionate prices…
People are not educated to self host. Everything is run in a “droplet” and just a click away.
Let's say 25% of people dont argue with customer service for a chargeback. Best run company in the world /s
It's a Tim foil hat pet conspiracy that I have, but I strongly believe that part important of the business model (or revenue share) is from people making mistakes or forgetting resources; more or less like gym subscriptions where the gym owners are more than happy to sell the [maximum_amount_of _people + 40%] knowing that the absenteeism will give the revenue offset that sustain part of the business.
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 little impetus to actually do the work for the individual teams. Despite that possibly adding up substantial savings for the overall business.
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.
You can set up daily or hourly cost and usage reports on the account. I built a finops function based on it, feeding the data into a Postgres db. Make sure to select incremental updates, if not you’ll en up paying for tb of s3 storage.
It clearly does, it's just different skills/time/energy requirements compared to colocation.
This seems like a glaring bug in the scripts run by that `npx` command. The author is correct, the scripts should 100%: - Choose the lowest cost resource (it's a tutorial!) - Cleanup resources when the `delete` subscript is run I don't think it's fair to expect developers to do paranoid sweeps of their entire AWS account looking for rogue resources after running something like this. If a startup had this behavior wou…
> 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.
This seems like a glaring bug in the scripts run by that `npx` command. The author is correct, the scripts should 100%: - Choose the lowest cost resource (it's a tutorial!) - Cleanup resources when the `delete` subscript is run I don't think it's fair to expect developers to do paranoid sweeps of their entire AWS account looking for rogue resources after running something like this. If a startup had this behavior wou…