GreenOps in the cloud
summary
Cloud workloads account for measurable emissions (data centres ~1% of global greenhouse gases and ICT rivals aviation) and the talk gives concrete mitigations: choose regions scoring well on renewables, adopt use renewable-energy regions and serverless event-driven patterns (example: S3 upload → Lambda thumbnail avoids idle 24/7 servers), right-size and auto-scale servers, stop forgotten volumes, prefer Graviton/AArch64 processors and reserved/spot mixes, tier S3 with lifecycle rules (move old objects to Glacier), use CDNs and managed services, and measure with AWS Carbon Footprint, Climatiq or Cloud Carbon Footprint.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:07Carbon emissions in IT sector
- 7:12What is GreenOps
- 7:53Choose cloud regions wisely
- 10:23Design serverless architectures
- 12:34Right size and stop unused resources
- 15:46Use power efficient processors
- 16:28Reserved and spot instances
- 18:34Store data efficiently
- 21:43Use Content Delivery Networks
- 23:55Use managed cloud services
- 25:40Perform well-architected reviews
- 26:43Measure carbon footprint tools
- 28:09Hold cloud vendors accountable
- 30:59Key takeaways and conclusion
related talks
42mUndertaking a GreenOps Approach in the Public Cloud
36mArchitecting in the Cloud for Sustainability
28mArchitecting in the Cloud for Sustainability
36mArchitecting in the Cloud for Sustainability
06mEco-DevOps - Building a Greener Future
57mOptimizing your infrastructure for sustainability
27mGreenOps Sustainable engineering 1
41mWriting Greener Software Even When You Are Stuck On-Prem