Solved: Help us understand FinOps maturity & cloud cost challenges

🚀 Executive Summary TL;DR: Cloud cost overruns stem from poor visibility and lack of ownership, exemplified by forgotten high-cost instances. The solution involves a multi-pronged FinOps approach, combining automated cleanup scripts, proactive policy-as-code guardrails, and fundamental organizational shifts towards showback and chargeback for sustained financial accountability. 🎯 Key Takeaways Implement ‘Janitor’ scripts (e.g., AWS Lambda) to automatically identify and terminate untagged or abandoned cloud resources, acting as a reactive cost control. Enforce ‘Policy as Code’ using tools like Sentinel or Open Policy Agent (OPA), and Service Control Policies (SCPs) to prevent expensive or untagged resource provisioning at the IaC or AWS Organization level. Drive ‘Organizational Change’ through FinOps practices like ‘showback’ (displaying team-specific cloud spend) and ‘chargeback’ (allocating costs to team budgets) to foster a culture of financial ownership. Struggling with runaway clou