← everything
Billing shock
When the AWS bill arrives and nobody can explain it.
The bill is the most common reason people end up here, and it is almost never the compute. It is the NAT gateway processing charge on traffic you thought was internal, the cross-AZ transfer inside your own cluster, the egress on a restore you ran once, the CloudWatch ingestion from a log line someone left at debug. AWS will let a misconfiguration bill you indefinitely: there is no hard spending cap, Budgets only notify, and by the time Cost Explorer shows you the shape of it the money is already spent.