Virus HQ ← All notes

Cutting AWS spend by 58% without slowing anything down

Sagar Rathod · Solutions & Systems Architect ·

A multi-region fintech platform came to me with a familiar problem: the AWS bill kept climbing, margins were shrinking, and nobody on the team could say with confidence why. Spend was sitting at roughly $20-25K a month.

  • ~58% lower monthly AWS spend overall
  • 75% lower Redis costs
  • 64% lower RDS costs
  • 86% lower S3 spend
  • No performance degradation

The work ran over three months in four phases. The fixes weren't discount programs or a one-off cleanup that drifts back within a quarter. They were structural changes across Redis, RDS, S3, Glue, ALB, and ECS. Here's the way I approach this kind of work.

1. Get visibility before touching anything

Most "cloud bills are out of control" problems are really visibility problems. Before changing a single resource, break spend down by service, environment, and workload, so every big line item has an owner and a reason to exist. The cost work then becomes a ranked list instead of guesswork.

2. Fix the architecture, not the invoice

Reserved capacity and savings plans have their place, but they lock in whatever you're paying for today, including the waste. The bigger wins come from asking whether each component is shaped right for the load it actually carries. The usual places to look:

3. Prove performance doesn't regress

Cost cuts that hurt latency or reliability aren't savings, they're deferred incidents. Every change should ship with before-and-after metrics for the things users feel, and a way to roll back. In this engagement the bill came down by more than half with no performance degradation.

4. Make it stick

The last step is keeping the savings: infrastructure as code (Terraform here) so changes are reviewed, clear ownership of each cost center, and alerts when spend moves. A one-time cleanup decays. A structural fix holds.

Is this worth it for you?

If your bill is in the tens of thousands per month and nobody can explain the biggest line items, there's almost certainly structural waste. I start with a short preliminary scan, and implementation is priced as a share of the savings, so the work pays for itself.

Questions people ask

How do you reduce AWS costs without hurting performance?

Break spend down by service, environment and workload first, then fix components that are shaped wrong for their real load: oversized Redis clusters and RDS instances, S3 data with no lifecycle rules, over-provisioned Glue jobs, and ALB/ECS sprawl. Ship every change with before-and-after metrics and a rollback path. On a multi-region fintech platform this cut AWS spend by ~58% with no performance degradation.

Why not just buy reserved instances or savings plans?

Reserved capacity and savings plans lock in whatever you pay for today, including the waste. They have their place, but the larger savings come from fixing the architecture first.

Which AWS services usually waste the most money?

The usual places are caches (Redis) sized for a peak that never comes, databases (RDS) never revisited after launch, S3 data kept forever in the most expensive tier, Glue jobs with far more capacity than needed, and load balancer and container (ALB, ECS) sprawl.

How do you keep AWS savings from creeping back?

Manage infrastructure as code (Terraform) so changes are reviewed, give each cost center a clear owner, and alert when spend moves. A one-time cleanup decays; a structural fix holds.

Facing something similar?

Book a free 30-minute architecture call. Describe what you're building or what's breaking, and you'll leave with a clear diagnosis and next steps.

Talk to me