Ask HN: Has AWS ever surprised you with a bill?
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.
(
13 comments
| 4 points
| on HN
)
https://docs.aws.amazon.com/lambda/latest/dg/invocation-recu...
So while the road you are looking down has some validity, it is also a high-churn product idea that only holds value for people who are brand new to AWS. I'd be hesitant to dedicate much time to such a narrow market.
I personally don't use any AWS constructs, just reserve EC2s as needed and host everything myself.