I tried something or other on aws. I only needed the 'definitely free, no cost whatsoever we will suspend the account before you hit whatever limits we set - that I didn't even hit a fraction of' tier free trial month to do whatever it was I was doing.
At the end of the 'totally free' month they charged me something like £1.80. Obviously £1.80 is inconsequential, it is the fact there was any charge at all given everything I had been told - I can't remember what I did, probably learned to set up a vpn or something simple - I didn't even use it beyond setting it up and testing it.
I made sure I burned the account in a big firey pit and I will never go back to them for anything I am paying for (news that I doubt is keeping Jeff Bezos up at night, but it isn't inconceivable I might have bigger projects in the future). I doubt they could figure out what the charge was for. Presumably chatgpt hallucinates their billing now which might be an improvement.
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.
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.
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
What I referenced earlier actually happened to me with Azure once. Unfortunately, I discovered at that last minute, but they thankfully just closed that account and never charged me.
So 50€/month assumes an average of 263W used 24/7, though considering I also have two switches and a workstation/backup server as well as the inefficiency of an UPS, that is realistic.
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?
You're gonna be fine. Honestly, if your team has given you permissions to do something accidental like this then it's on them. You're not gonna get stuck with the bill. You're not gonna get fired. It wouldn't be your fault.
It's really only scary when you're doing it solo with your own back information lol.
If you spin it up, fucking own it. When you're done with it, shut it down. I have long lost count of the number of times I've reached out to a team to ask about the coin miner they are running on some random EC2 instance only to find out that some jackass spun it up for a test, gave it a public IP, set the VPC to allow any inbound traffic, installed all kinds of random crap and then never updated it. Nor did it get shutdown when the test ended. So, a year and a half later, when the software was woefully out of date, someone hacked it and spun up a coin miner. Oh, and the jackass who set it up didn't bother to enable logging or security monitoring. But, they sure as hell needed the ability to spin stuff up on their own. Because working with IT to get it done right would be too hard for their fragile little ego.
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
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.
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
Years ago, I played with AWS then contacted their support to make sure any AWS billing to my account was disabled.
I thought I'd try it again recently, and couldn't log in.
I still don't think I'm missing anything.
I'd rather have VPS or server providers where I know exactly what I'm getting per month no matter what, tho I've ran near data transfer surcharges.