Undertaking a GreenOps Approach in the Public Cloud
summary
Practical GreenOps guidance for estimating cloud emissions by converting cloud bill metrics to energy (e.g., 1 vCPU-hour ≈ 2.10 Wh), applying regional grid carbon intensity (France ≈46 gCO2/kWh, Germany ≈492, Poland ≈817) and PUE, then using concrete reduction levers: migrate to efficient instance families (Graviton ≈60% lower energy), move workloads to lower-carbon regions (observed ×3–×6 reductions, sometimes paying ~15–20% more), schedule flexible jobs during greener hours, and remove zombie resources. Implementation advice includes building dashboards from invoices with observability tools (Datadog) and adding CI checks in pipelines (Sonar, Terraform) to track and enforce GreenOps practices.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:40GreenOps cloud pillars
- 11:01Cloud CO2 emissions
- 17:42Measuring carbon footprint
- 23:20Optimizing cloud resources
- 30:15Advanced GreenOps
- 41:00Q&A
related talks
56mA Developer's Perspective On Greener Future: GreenOps in practice
32mGreenOps in the cloud
44mCloud computing and carbon emissions
06mEco-DevOps - Building a Greener Future
55mToward a carbon-aware Cloud
41mWriting Greener Software Even When You Are Stuck On-Prem
27mDevGreenOps
27mGreenOps Sustainable engineering 1