Skip to main content
CloudBit Logo
Cloud

The most common AWS cost leaks (and how to fix them)

NAT Gateways, forgotten snapshots, unused disks and environments running overnight: where AWS budget disappears without anyone noticing.

· 6 min read · CloudBit team

Data transfer and NAT Gateways

NAT Gateways charge per hour and per gigabyte processed. When private instances pull container images or talk to S3 and DynamoDB through the NAT, the bill grows quickly. VPC gateway endpoints for S3 and DynamoDB (no hourly charge) and a nearby private image registry usually fix it.

Storage nobody deletes

Detached EBS volumes, snapshots of instances that no longer exist, old AMIs and buckets without lifecycle rules pile up month after month. An S3 lifecycle policy and a periodic review of unused snapshots and volumes recover money with no risk.

Environments running after hours

Development and test environments are rarely used at night or on weekends. Shutting them down automatically on a schedule can cut their cost by more than half.

Oversized instances

AWS Compute Optimizer analyzes actual CPU and memory usage and recommends smaller sizes or more efficient families such as Graviton. Combined with Savings Plans for the steady baseline, savings are usually significant.

Logs without retention

CloudWatch log groups keep everything forever by default. Setting retention per environment (for example, 14 days in development and 90 in production) and exporting to S3 what must be kept longer prevents a silent leak.

Want to apply this at your company?

Book a free 30-minute technical consultation.

Talk to a specialist