FinOps for sustainability
summary
Combines FinOps and GreenOps by pulling AWS GCP and Azure cost and billing into BigQuery and running Cloud Carbon Footprint to estimate emissions, then using that joint dataset for decisions. Demonstrates region tradeoffs: moving from US East to EU North cuts estimated emissions by ~45× while raising monthly cost ~6%, so cost and carbon don’t correlate. Describes culture of continuous optimization, KPIs, reserved‑instance/committed‑use negotiation, region shifting and software/architecture choices for embodied carbon. Cloud Carbon Footprint BigQuery AWS GCP
AI-written summary · about
chapters (18)
- 0:00Intro
- 3:22Cloud is critical to every business but is a fundamentally different consumption model...
- 4:28Cloud FinOps is an evolving cloud financial management discipline and cultural practice that
- 5:50FinOps principles
- 9:50FinOps maturity model
- 10:44FinOps personas
- 13:21Phases of FinOps
- 14:25Key performance indicators
- 15:02Adoption roadmap for FinOps
- 20:34Fundamental difference - GreenOps and FinOps
- 23:21What goes into Cloud Carbon Footprint Calculation?
- 27:00GreenOps Capabilities
- 28:31Green Software Principles
- 33:28GreenOps Strategy Map Approach Plan your personalized strategy for your organization and map out the individual
- 34:59In the end it's a balancing act
- 36:42Cloud SustainableOps is an evolving cloud management discipline and cultural practice that
- 37:27Sustainable Ops - What good looks like
- 38:06SustainableOps adoption roadmap
related talks
20mFinOps and GreenOps successes on AWS: A customer story
32mGreenOps in the cloud
19mFinOps for business results
12mFinOps on AWS: Accelerated outcomes to maximize ROI
06mEco-DevOps - Building a Greener Future
42mUndertaking a GreenOps Approach in the Public Cloud
56mA Developer's Perspective On Greener Future: GreenOps in practice
41mFinOps and Cloud Cost Optimization