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.

Who told you that?

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.

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.

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

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.

Wow that's.... Pricey. What is your kWh cost?

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.

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.