Your cloud has a carbon footprint, and it tracks your bill more closely than you might think. The same idle instances and oversized databases that waste money also waste energy. Here is how to measure your footprint and where the biggest reductions hide.
What drives cloud carbon
Emissions from cloud usage come down to three things: how much compute and storage you consume, how energy-intensive the underlying hardware is, and how clean the electricity grid is in the region where it runs. Two identical workloads in different regions can have very different footprints.
Why cost and carbon move together
Nearly every FinOps win is also a sustainability win. Kill an idle instance and you remove both its cost and its emissions. Right-size a database and you cut both. This is why measuring carbon alongside cost — at the same granularity — is so powerful: your existing cost-reduction work doubles as a decarbonization plan.
The Scope-3 gap
Cloud providers report some emissions data, but it is often delayed and incomplete — particularly Scope-3 (embodied emissions from manufacturing the hardware). To get a usable, timely picture, most teams estimate emissions from usage data using regional grid-intensity factors.
Where the biggest reductions hide
- Idle and orphaned resources — pure waste, cut them entirely.
- Right-sizing — smaller instances draw less power.
- Region choice — running flexible workloads in lower-carbon regions.
- Storage tiering — cold data on efficient tiers instead of hot storage.
Measure it automatically
CloudMonitor estimates kgCO₂e for your AWS EC2 instances, EBS volumes and RDS databases, and its What-If Simulator shows the carbon change of a scenario next to the cost change. The estimates use a single global grid factor, so treat them as directional — good for finding the biggest contributors, not for audited reporting. Explore the carbon footprint feature to make sustainability a byproduct of the FinOps you are already doing.