Menu

11 things quietly inflating your AWS bill (and how to find them in an afternoon)
πŸ“°

11 things quietly inflating your AWS bill (and how to find them in an afternoon)

DEV Community: cloudΒ·AndrΓ© PizzettiΒ·10 days ago
#ksKiy2TH
#devtocloud#devto#dev#spot#cost
Reading 0:00
15s threshold

Most AWS bills don't explode. They creep. A test server nobody turned off, a disk left behind after an instance was deleted, logs that are kept forever. None of them is dramatic on its own, which is exactly why they survive for years.

After more than 25 years in tech, I keep finding the same culprits. Here is the list I check first, with the quickest way to spot each one.

1. Servers that are running but barely working

An EC2 instance is billed every hour it runs, whether it serves a thousand requests or none.

How to spot it: in CloudWatch, look at CPUUtilization for the last 14 days. An instance that averages under 10% and never goes above 40% can usually drop one size, which roughly halves its price. One that never passes 5% may not be needed at all.

Watch out: CPU isn't everything. Check memory too (it needs the CloudWatch agent) before downsizing.

2. Disks with no server attached

When you terminate an instance, its EBS volumes are not always deleted.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.