Cloud Carbon Report Analyzer
See your AWS, Azure, Google Cloud and Oracle carbon reports in one view, with what drives them.
Before you start: what to have readyShow
- One export per cloud. The query or steps for each are just below.
- A year or more of months, for the trend and the reporting view. Azure keeps 12 months.
AWS delivers your emissions as a Data Exports table, CARBON_EMISSIONS: monthly, by account, service and Region.
- In Billing and Cost Management, open Data Exports and create an export of the carbon emissions table, as CSV, to an S3 bucket. The management account’s export covers every member account.
- Once it has been delivered, download the CSV files for the months you want and load them here as they are.
- Or, if the export is in Athena, type the table below and run the query: one file for a whole range of months.
-- Finitizer Cloud Carbon Report Analyzer: AWS CARBON_EMISSIONS export,
-- one row per month, account, service and region (MTCO2e, as AWS reports).
-- Run it in Amazon Athena, then Download results (CSV).
SELECT
substr(cast(usage_period_start AS varchar), 1, 7) AS usage_period_start,
usage_account_id,
product_code,
region_code,
max(model_version) AS model_version,
sum(total_lbm_emissions_value) AS total_lbm_emissions_value,
max(total_lbm_emissions_unit) AS total_lbm_emissions_unit,
sum(total_mbm_emissions_value) AS total_mbm_emissions_value,
max(total_mbm_emissions_unit) AS total_mbm_emissions_unit,
sum(total_scope_1_emissions_value) AS total_scope_1_emissions_value,
max(total_scope_1_emissions_unit) AS total_scope_1_emissions_unit,
sum(total_scope_2_lbm_emissions_value) AS total_scope_2_lbm_emissions_value,
max(total_scope_2_lbm_emissions_unit) AS total_scope_2_lbm_emissions_unit,
sum(total_scope_2_mbm_emissions_value) AS total_scope_2_mbm_emissions_value,
max(total_scope_2_mbm_emissions_unit) AS total_scope_2_mbm_emissions_unit,
sum(total_scope_3_lbm_emissions_value) AS total_scope_3_lbm_emissions_value,
max(total_scope_3_lbm_emissions_unit) AS total_scope_3_lbm_emissions_unit,
sum(total_scope_3_mbm_emissions_value) AS total_scope_3_mbm_emissions_value,
max(total_scope_3_mbm_emissions_unit) AS total_scope_3_mbm_emissions_unit
FROM cur_database.carbon_emissions
WHERE date_parse(substr(cast(usage_period_start AS varchar), 1, 10), '%Y-%m-%d')
>= date_add('month', -13, date_trunc('month', current_date))
GROUP BY 1, 2, 3, 4
ORDER BY 1;It needs the sustainability:GetCarbonFootprintSummary permission. Figures are in metric tonnes, location-based and market-based, Scope 1 to 3. AWS column reference.
Or drop the files here: CSV, gzip or Azure’s JSON. They are read in this browser and sent nowhere unless you choose to share them for a review.
Want this done on your real bill?
Cloud Cost Audit: We go through your real AWS or Google Cloud bill and hand you a ranked list of what to cut first. From $1,500, fixed. Nothing paid upfront.
Questions
Where do I get my cloud provider’s carbon report?
Every major cloud now provides one, free. AWS delivers a CARBON_EMISSIONS table through Data Exports; Google Cloud writes a Carbon Footprint table to BigQuery each month; Azure shows emissions under Carbon optimization in the portal, with an export; Oracle Cloud has Carbon Emissions Analysis with a CSV download. "How to get your data" at the top of the page has the query or the steps for each.
Why do the clouds’ numbers not add up the same way?
Because they count differently. AWS and Google report both location-based figures (what the local grid emitted) and market-based ones (after their renewable energy purchases); Azure’s portal reports market-based only. Google reports kilograms, AWS and Oracle tonnes. This page converts the units and never adds a location-based figure to a market-based one: pick a basis, and any cloud that does not report it is listed as left out.
Where do cloud emissions go in our sustainability report?
For a cloud customer, all of the provider’s emissions are Scope 3, usually Category 1, purchased goods and services, even the parts the provider calls its Scope 1 and 2. The reporting view totals them by your fiscal year on the basis you choose. Check your own reporting framework for which basis it asks for; most ask for both.
Is my data uploaded?
No. The files are read by JavaScript in this browser and never sent anywhere, unless you choose "Share for a review" under the results, which saves the files you loaded for Finitizer to look at, under a reference you can quote.
Why did last year’s figures change when I exported them again?
Providers revise their models and restate earlier months: AWS now restates the previous year with utility invoice data, and both AWS and Google record a model version on every row. When the files you load span two versions, the page says so. For a report, export the whole year in one go so every month uses the same model.
Related tools
Cloud Workload Carbon Calculator
Where you run a workload changes its carbon far more than which cloud you pick.
OpenGreenest Cloud Region Finder
Every AWS, Azure and Google Cloud region, carbon and price side by side.
OpenFOCUS 1.4 Validator
Check a billing export against FOCUS 1.4, with no file size limit.
OpenMore tools for: Carbon and sustainability, Billing data, allocation and governance
The provider reports what happened. Finitizer shows what to change.
Finitizer puts carbon beside cost for the resources you run, so the regions, services and idle capacity behind both show up in one list, ranked by what changing them would save.
See how Finitizer works