See everything · Carbon Footprint

See the carbon behind your compute.

CloudMonitor estimates emissions for your EC2 instances, EBS volumes and RDS databases from instance size, running hours and data-center overhead — directional numbers you can prioritise with, right next to the dollars.

AWS Azure Google Cloud
Estimated carbon · AWS kgCO₂e / month
ec2 · m5.4xlarge batch-01$560188 kg
rds · db.r5.2xlarge prod$690147 kg
ec2 · m5.large web-02$7018 kg
ebs · 4 TB gp3$3201.6 kg

Directional estimate: power by instance size × 730 h × PUE 1.135 × 0.40 kgCO₂e/kWh.

01 What’s included

Carbon Footprint, in detail.

Estimated kgCO₂e next to your AWS compute spend. Here is exactly what CloudMonitor does — and where its coverage stops today.

Per-resource estimates

kgCO₂e per month for each EC2 instance, EBS volume and RDS database. Stopped instances count at a small fraction of running ones.

A transparent method

Power draw by instance size × 730 hours × a data-center PUE of 1.135 × a grid factor of 0.40 kgCO₂e per kWh. The assumptions are shown on the page.

Carbon in every what-if

The What-If Simulator reports the monthly kgCO₂e change of each scenario next to the cost change.

Equivalents people understand

Totals are also shown as tree-years, which helps the number land in a sustainability update.

02 How it works

Three steps, no agents to install.

1

Connect AWS

Carbon is estimated from the EC2, EBS and RDS inventory CloudMonitor already holds.

2

See the biggest emitters

Resources are ranked by estimated kgCO₂e, with the method spelled out.

3

Cut cost and carbon together

Idle and oversized resources waste both, so the same clean-up lowers both numbers.

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.

03 FAQ

Carbon Footprint
questions.

Something else? Talk to us — a person replies.

How accurate are the carbon estimates?

They are directional, not audited. The model uses one global grid-intensity factor rather than per-region factors and covers EC2, EBS and RDS. Use it to compare options and find the largest contributors, not for regulatory reporting.

Does it include Scope 3 emissions?

No. The estimate covers the operational electricity of running resources. Embodied (Scope 3) emissions are not modelled.

Why do cost and carbon move together?

Both scale with the capacity you keep running. An idle instance burns money and electricity at the same time, so removing waste lowers both.

Are Azure and Google Cloud covered?

Not yet. Carbon estimates cover AWS EC2, EBS and RDS today.

Turn on
the radar.

Create a workspace, connect your first account read-only and see what your clouds have been hiding.

FREE PLAN · NO CREDIT CARD · READ-ONLY ACCESS