using AWS
-
Who told you that?
The Downloadable RAM Fairy
-
Oh, it's expected costs.
Like, figure out the compute requirements of your code, multiply by the cost per compute unit (or whatever): boom, your cost.
Totally predictable.
Compared to suddenly having to replace a $20k server that dies in your data center.
So much easier.Except when your code (let's be honest, the most likely thing to have an error in it... At least compared to some 4+ year old production hardware that everyone runs) has a bug in it that requires 20x compute.
But maybe that is a popularity spike (the hug-of-death)! That's why you migrated to the #cloud anyway, right? To handle these spikes! And you've always paid your bills so... Yeh, here's a 20x bill.Good point. Maybe it depends on what I want to happen when that load spike comes.
-
This post did not contain any content.
I'm very new to programming and somehow have a job where I have to write Python scripts. Someone on my team mentioned that we use AWS and now I'm scared. Can someone explain how you accidentally rack up such a bill?
-
These horror stories make me afraid to even learn AWS with trials
First thing I learned in a video course was setting a spending budget for your account. I set a $10/month limit and never broke it in 6 years.
-
I'm very new to programming and somehow have a job where I have to write Python scripts. Someone on my team mentioned that we use AWS and now I'm scared. Can someone explain how you accidentally rack up such a bill?
Just make sure whatever resources you spin up you're spitting down. This stuff though tends to happen when people accidentally let a a script that creates and destroys instances run over the weekend and it didn't appropriately clean up instances for you...
Or you thought you would try your hand at training in llm and then realized you spent way too much money on the infrastructure and resources
-
I'm very new to programming and somehow have a job where I have to write Python scripts. Someone on my team mentioned that we use AWS and now I'm scared. Can someone explain how you accidentally rack up such a bill?
It's actually difficult. You can set a budget so AWS will alert you when you hit it.
They have a price calculator that'll calculate costs before you do anything.
Inbound Internet is free. Only outboard costs you anything.
Network transfers between VPC's using private links are free.
AWS accounts are free.
Lambda functions are ultra cheap as you only pay for the time you use it.
S3 is object storage with 11 9's of uptime and it's cheaper than any enterprise NAS.
Basically you'd have to setup something wrong and ignore it for weeks to incur a large bill.
-
Who told you that?
The cloud computing salesmen
-
Good point. Maybe it depends on what I want to happen when that load spike comes.
Saw that Grafana gets special notifications permissions on iOS for emergencies - expensive charges should wake up whoever’s on the hook for them
-
The cloud computing salesmen
And all the senior management that believed their horseshit.
-
This post did not contain any content.
I never have that problem with Digital Ocean
-
This post did not contain any content.
That's why pay-as-you-go payment model is completely unfitting for the world of computers.
Prices can rack up dramatically without you noticing.
-
Good point. Maybe it depends on what I want to happen when that load spike comes.
wrote on last edited by [email protected]Maybe it depends on what I want to happen when that load spike comes.
I don't know what they wanted to happen, but at my old place the load spike overloaded the UPS units.
Me: "we really shouldn't be running these at
859095%."Brass: "That's not 100. Find room to ingest this company we bought when the CEO made a friend at a circlejerk."
Overnight server update check: blip
UPS: Bypass mode, bitches!
¯\_(ツ)_/¯
-
This post did not contain any content.
-
This post did not contain any content.wrote on last edited by [email protected]
asdf
-
I'm very new to programming and somehow have a job where I have to write Python scripts. Someone on my team mentioned that we use AWS and now I'm scared. Can someone explain how you accidentally rack up such a bill?
wrote on last edited by [email protected]AWS has a multitude of different offerings with confusing pricing structures. They have zero incentive to make them understandable.
That said, chances are your new company has people who understand this already and know how to manage it. Hopefully, they'll put up some guardrails that prevent you and others from running up a big bill. I wouldn't expect a junior programmer to know how to do this, but that's ok as long as the company is managed right. Granted, that can be a big if sometimes.
-
It's actually difficult. You can set a budget so AWS will alert you when you hit it.
They have a price calculator that'll calculate costs before you do anything.
Inbound Internet is free. Only outboard costs you anything.
Network transfers between VPC's using private links are free.
AWS accounts are free.
Lambda functions are ultra cheap as you only pay for the time you use it.
S3 is object storage with 11 9's of uptime and it's cheaper than any enterprise NAS.
Basically you'd have to setup something wrong and ignore it for weeks to incur a large bill.
Or leak your creds and let a crypto miner in. But your point still stands.
-
I enabled Cloudtrail to log all DynamoDB read/write data events when trying to troubleshoot an issue. Even though I only left this enabled for a few days, the Cloudtrail line item was $5k more than it should have been. My back of the napkin math with assumptions came out to be 100 times less than that, so I had a really awkward support email asking them to reverse the charges, which they did fortunately.
wrote on last edited by [email protected]A lot of the times this comes down to a user error.
For example, very similar to your case, I knew someone that enabled Cloudtrail, and configured some things to have Cloudtrail logs dumped on S3. Guess what? Dumping things on S3 also creates a Cloudtrail that gets logged to S3 that Cloudtrail logs. Etc
Doing things like that and creating a loop can get you massive bills
-
I'm very new to programming and somehow have a job where I have to write Python scripts. Someone on my team mentioned that we use AWS and now I'm scared. Can someone explain how you accidentally rack up such a bill?
Can someone explain how you accidentally rack up such a bill?
For example: You can deploy your Python script as a Lambda. Imagine somewhere in the Python script you'd call your own lambda - twice. You basically turned your lambda into a Fork Bomb that will spawn infinite lambdas
-
A lot of the times this comes down to a user error.
For example, very similar to your case, I knew someone that enabled Cloudtrail, and configured some things to have Cloudtrail logs dumped on S3. Guess what? Dumping things on S3 also creates a Cloudtrail that gets logged to S3 that Cloudtrail logs. Etc
Doing things like that and creating a loop can get you massive bills
Yeah, in my case, I wasn't familiar with the settings for Cloudtrail Data Events, and didn't realize you could select which events to log, based on the actor or resource, as opposed to all events in DynamoDB. That would have saved me a lot processing power to filter the logs to look for the actions I was looking for.
-
asdf
There's lots of costs to AWS. They'll rope you in with the whole free tier for compute and storage. But AWS has charges for outbound traffic, detailed logging, elastic IPs, etc.
It's a whole job to just do cost analysis for cloud services.
