Why put carbon next to cost?
For most cloud workloads, emissions track the capacity you keep running. That means the work FinOps teams already do — removing idle instances, rightsizing, shutting down forgotten environments — is also the most effective way to reduce cloud emissions. Showing both numbers side by side turns sustainability from a separate project into a by-product of cost work.
How the estimate works
CloudMonitor estimates monthly emissions per resource with a deliberately simple, transparent model:
- a power draw for the instance size, from a few watts for nano instances to well over a kilowatt for the largest;
- × 730 hours a month (stopped instances count at 5% of running);
- × a data-center PUE of 1.135 for cooling and overhead;
- × a grid factor of 0.40 kgCO₂e per kWh.
EBS volumes are estimated per terabyte, and RDS databases at 1.2 times their equivalent instance class. Totals are also shown as tree-years, which helps the number make sense in an update to leadership.
What it is — and isn’t
These are directional estimates, not audited figures. The model uses one global grid factor rather than per-region intensity, covers EC2, EBS and RDS on AWS, and does not include embodied (Scope 3) emissions. Use it to find your biggest contributors and compare options. For formal reporting, use your provider’s own sustainability tooling.
Model the change first
Every scenario in the What-If Simulator reports its monthly kgCO₂e change next to the cost change. For background on measurement approaches, read the cloud carbon footprint guide.