{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"FinOps in Action","title":"Why Cloud Costs Are an Architecture Problem ft. Shailaja Beeram | Ep #68","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/b275df6d\"></iframe>","width":"100%","height":180,"duration":1861,"description":"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 resourcesHow NAT Gateways and private endpoints quietly drive unnecessary spendWhat “zombie resources” are and how they accumulate over timeWhy background traffic can mask true resource idlenessThe importance of revisiting architectural decisions as systems evolveThe growing convergence of FinOps and cloud architectureChapters:00:00 - Architecture Drives Cost00:34 - Meet the Guest Architect01:46 - When Cost Became the Job03:04 - Networking Zombie Resources05:32 - NAT Gateway Design Traps07:11 - Spotting Hidden Traffic10:34 - Azure Functions NAT Story12:30 - Private Endpoints and Drift16:53 - Shift Left Cost Awareness19:20 - Balancing Risk and Cost22:46 - Advice for Both Sides26:41 - AI Impact on FinOps27:53 - Volunteering and Closing30:37 - Outro and Sponsor 🎧 Subscribe for more FinOps leadership conversations → https://www.finopsinaction.com/ Quote of the Show:“FinOps… it doesn’t need to be separated. It should be a part of how you think about the architecture.” - Shailaja BeeramLinks:LinkedIn: https://www.linkedin.com/in/shailaja-beeram-82324310a/ Ways to Tune In:Amazon Music:...","thumbnail_url":"https://img.transistorcdn.com/19z3-eWZl6c0TEQCJZvYXIgN4CxYIhl9_e56I_mkpWs/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wYTdj/YWRhNmM4YzM4NzQ0/NDVlNzFhYmE2NmVi/Y2ZiZC5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}