FinOps in Action | Why Cloud Costs Are an Architecture Problem ft. Shailaja Beeram

Why Cloud Costs Are an Architecture Problem ft. Shailaja Beeram | Ep #68

May 7, 2026 / 31:01/E68

Are “idle resources” really the problem, or just the easiest one to fix?

In this episode of FinOps in Action, I sit down with cloud architect and engineer Shailaja Beeram to explore a fundamentally different perspective: cost inefficiencies don’t start in the billing file, but in architectural decisions made long before deployment.

Drawing on over 15 years of experience across AWS, Azure, and GCP, Shailaja explains how the way systems are designed, scaled, and evolved over time has a far greater impact on cloud spend than most teams realize.

From “zombie” networking resources to overlooked outbound traffic patterns, this conversation unpacks the hidden layers of cloud cost and why FinOps and architecture must converge to solve them.

Here’s what we talked about:

Why cloud inefficiencies often stem from architecture and not just unused resources
How NAT Gateways and private endpoints quietly drive unnecessary spend
What “zombie resources” are and how they accumulate over time
Why background traffic can mask true resource idleness
The importance of revisiting architectural decisions as systems evolve
The growing convergence of FinOps and cloud architecture

Chapters:

00:00 - Architecture Drives Cost

00:34 - Meet the Guest Architect

01:46 - When Cost Became the Job

03:04 - Networking Zombie Resources

05:32 - NAT Gateway Design Traps

07:11 - Spotting Hidden Traffic

10:34 - Azure Functions NAT Story

12:30 - Private Endpoints and Drift

16:53 - Shift Left Cost Awareness

19:20 - Balancing Risk and Cost

22:46 - Advice for Both Sides