Ad · 728×90 desktop · 320×50 mobile

What we learned cutting our cloud bill by 40%

Published 2026-04-24 · FinOps & Cloud Cost

Not a brag. Not a case study. A ranked list of what actually moved the needle when we ran a 90-day cost program on a $3M/year AWS account. Specific numbers, specific mistakes.

What worked (in order of $ impact)

1. Rightsizing non-prod environments (-18%)

Dev and staging were running prod-sized infrastructure. We cut non-prod instance sizes by half and nothing broke. This was the biggest single move. Took 2 weeks.

2. Savings Plans on steady-state (-12%)

We covered about 70% of steady-state compute with 1-year Compute Savings Plans. Immediate savings, no architecture changes. Took an afternoon.

3. S3 lifecycle policies (-5%)

Moved logs older than 30 days to Standard-IA, older than 90 days to Glacier Flexible, older than 1 year to Deep Archive. Took half a day including testing.

4. Killed zombie resources (-3%)

Unattached EBS volumes, orphaned Elastic IPs, load balancers with zero traffic. Took one week including notification period.

5. Moved observability data tiers (-2%)

CloudWatch Logs retention was 2 years by default. Cut to 90 days for most, 1 year for security logs. Application debug logs stopped going to CloudWatch entirely.

What didn't work

Reserved Instances for a year-ago workload shape

We bought RIs based on what we were running. Three months later we refactored and the RIs no longer matched. Lesson: Savings Plans > RIs for anything under active development.

Attempting to kill the Datadog bill

We tried to shift observability to open source and the engineering cost was higher than the Datadog savings. Abandoned after two sprints.

Serverless migration as a cost play

Migrating to Lambda sounds cheap. For our workload (steady baseline), it was more expensive than rightsized EC2. Lambda wins for spiky, low-average-utilization workloads only.

The unglamorous truth

Most of the savings came from boring moves: rightsizing and commitment purchases. The "interesting" architecture changes (serverless, spot, arm64) produced the smallest gains per hour of work.

Tools that helped

Ad · 300×250 responsive

Joined by engineers at enterprises running the systems you build. No spam. No tracking in the emails.