GreenOps and Sustainable Cloud Computing Cheat Sheet

Updated 2026-05-21

GreenOps (Green Operations) is the discipline of measuring, managing, and reducing the carbon and energy impact of cloud workloads — applying operational rigor to environmental outcomes the same way FinOps applies it to cost. Cloud computing accounts for roughly 1–2% of global electricity consumption today, with data center demand projected to reach 620–1,050 TWh by 2026 driven by AI growth. What makes GreenOps distinctive is that waste and carbon are the same problem: an idle VM drains budget and emits needlessly, so the discipline converges naturally with FinOps. Practitioners who internalize the GHG Protocol's Scope 1/2/3 structure, the SCI formula, and carbon-intensity APIs hold the conceptual toolkit needed to make every architectural decision both cost-efficient and climate-efficient.

What This Cheat Sheet Covers

This topic spans 15 focused tables and 123 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Emissions Scopes and Carbon Accounting FundamentalsTable 2: Key Carbon Measurement Formulas and MetricsTable 3: Cloud Provider Carbon Measurement ToolsTable 4: Carbon-Aware Scheduling — Time and Space ShiftingTable 5: Instance and Compute Efficiency for Lower CarbonTable 6: Idle Resource Detection and Cloud Waste EliminationTable 7: Storage Tiering, Lifecycle, and Data MinimizationTable 8: Network Egress and Data Transfer Carbon Trade-offsTable 9: Sustainable AI and ML Inference Carbon FootprintTable 10: GreenOps Maturity Model and KPIsTable 11: FinOps and GreenOps IntegrationTable 12: Reporting Frameworks and Sustainability Disclosure RegulationsTable 13: Vendor Sustainability Commitments and Power Purchase AgreementsTable 14: Green Software Engineering Principles and PatternsTable 15: Common Reduction Patterns and Quick Wins

Table 1: Emissions Scopes and Carbon Accounting Fundamentals

The GHG Protocol's three-scope framework is the universal standard for categorizing cloud emissions, underpinning every sustainability disclosure from CSRD to SBTi target-setting. Understanding which scope covers which source determines where reduction efforts will have the most impact and how to attribute cloud provider emissions to your workloads.

Concept	Example	Description
Scope 2 emissions (cloud)	`carbon_footprint_kgCO2e.scope2.location_based` in BigQuery export	Indirect emissions from purchased electricity — the dominant scope for cloud workloads; calculated as energy consumed × grid carbon intensity.
Scope 3 emissions (cloud)	Server GPU manufacturing, data center construction materials	Value-chain emissions not controlled by your org; for cloud customers these include hardware manufacturing (Scope 3 of the provider), apportioned to usage. Typically represents 80–97% of total organizational emissions.
Scope 1 emissions (cloud)	On-site backup diesel generator at a colocation facility	Direct emissions from sources your org controls; minimal for pure cloud workloads but relevant for hybrid or on-premises data center components.
Location-based method (LBM)	CO2 = kWh × grid average intensity (e.g. 400 gCO2/kWh for US East)	Reflects actual CO2 from the physical grid mix at the datacenter location; the primary developer-facing measure in tools like Google Cloud Carbon Footprint.
Market-based method (MBM)	LBM emissions minus renewable energy credits purchased by AWS	Adjusts location-based figures for market instruments (RECs, PPAs) procured by the cloud provider; shown by default in AWS CCFT.
Carbon intensity (gCO2eq/kWh)	`437 gCO2/kWh` (Texas peak demand) vs. `5 gCO2/kWh` (Québec hydro)	Grams of CO2-equivalent emitted per kilowatt-hour of grid electricity; varies by region, hour, and season — the key signal for carbon-aware scheduling.

Table 1: Emissions Scopes and Carbon Accounting Fundamentals

Concept	Example	Description
Scope 2 emissions (cloud)	`carbon_footprint_kgCO2e.scope2.location_based` in BigQuery export	Indirect emissions from purchased electricity — the dominant scope for cloud workloads; calculated as energy consumed × grid carbon intensity.
Scope 3 emissions (cloud)	Server GPU manufacturing, data center construction materials	Value-chain emissions not controlled by your org; for cloud customers these include hardware manufacturing (Scope 3 of the provider), apportioned to usage. Typically represents 80–97% of total organizational emissions.
Scope 1 emissions (cloud)	On-site backup diesel generator at a colocation facility	Direct emissions from sources your org controls; minimal for pure cloud workloads but relevant for hybrid or on-premises data center components.
Location-based method (LBM)	CO2 = kWh × grid average intensity (e.g. 400 gCO2/kWh for US East)	Reflects actual CO2 from the physical grid mix at the datacenter location; the primary developer-facing measure in tools like Google Cloud Carbon Footprint.
Market-based method (MBM)	LBM emissions minus renewable energy credits purchased by AWS	Adjusts location-based figures for market instruments (RECs, PPAs) procured by the cloud provider; shown by default in AWS CCFT.
Carbon intensity (gCO2eq/kWh)	`437 gCO2/kWh` (Texas peak demand) vs. `5 gCO2/kWh` (Québec hydro)	Grams of CO2-equivalent emitted per kilowatt-hour of grid electricity; varies by region, hour, and season — the key signal for carbon-aware scheduling.