All articles

5 min read

7 places AWS waste usually hides

Idle EC2 is the obvious one. The bigger surprises tend to live in EBS, snapshots, NAT Gateways, and data transfer.

1. Unattached EBS volumes

When an EC2 instance is terminated, its EBS volumes can stay behind and keep billing every month. Filter volumes by state “available” to find them.

2. Old EBS snapshots and AMIs

Snapshots from long-gone instances pile up quietly. Agree a retention policy and use Amazon Data Lifecycle Manager to enforce it.

3. Idle and oversized EC2

Instances running at single-digit CPU for weeks are candidates for rightsizing, Graviton, or shutdown. Check memory and peak load before acting.

4. Dev and test running 24/7

Non-production environments used 50 hours a week but billed for 168. Instance Scheduler can cut that compute cost substantially.

5. NAT Gateway data processing

Traffic to S3 or DynamoDB through a NAT Gateway is charged per GB. A free gateway VPC endpoint often removes that charge.

6. Inter-AZ and inter-region transfer

Chatty services across Availability Zones add up. Look at the DataTransfer line items in your Cost and Usage Report.

7. S3 in the wrong storage class

Rarely accessed objects sitting in S3 Standard. S3 Intelligent-Tiering or lifecycle rules move them automatically.

Want us to check your account?

The AWS scan is free. You only pay 25% of savings we verify.

Get a free scan