Ask HN: Has AWS ever surprised you with a bill?

4 noway_bro 4 7/7/2025, 12:30:16 AM
I’m validating a small tool that could’ve caught a $42k DynamoDB spike before it snowballed — within 10 minutes, via Slack alert.

Trying to talk to 10 devs or engineers who’ve been hit by unexpected AWS charges (Lambda loops, S3 egress, log retention, etc).

Not selling anything. Just want to understand:

- What caused it? - How you found out? - What you tried after? - Would a $15/mo tool with IaC cost-diff + Slack alerts have helped?

If that’s you (or your team), I’d love to hear from you.

Comments (4)

shiva0801 · 30m ago
Yep — we got hit with a ~$1.8k bill spike on AWS due to a Lambda function caught in a recursive loop during a staging deploy. It kept calling itself due to a misconfigured trigger — we didn’t catch it for ~6 hours because it wasn’t high-traffic, just persistent.
noway_bro · 48s ago
And $15/m would be interesting to not have this problem ever again? Is there anything else that would be cool to have with that?
muzani · 9h ago
Yeah, it's a meme at this point that if you're learning AWS, expect to be homeless because you left the EC2 on. Maybe not that bad, but I feel like most people have the logging to detect spikes etc, except those who don't know how to do logging.
scarface_74 · 7h ago
Funny enough, AWS has added recursive lambda call prevention within the last two years.

https://docs.aws.amazon.com/lambda/latest/dg/invocation-recu...