Greenpixie and AWS calculate the impact of your cloud usage in different ways. Their methodologies differ in approach, granularity, timeliness and data sources, so which one to use depends on the outcome you need and the use case in front of you. AWS Sustainability is the service that replaced the AWS Customer Carbon Footprint Tool (CCFT) in 2026.
How does AWS Sustainability work?
AWS Sustainability works top down. AWS starts with the total emissions of a cluster, which in its methodology means an AWS Region such as Frankfurt or Ohio, or a CloudFront edge cluster, and divides that total down until a share lands on your account. Your figure is a slice of AWS's footprint, not a measurement of what your resources drew.
The allocation works in three steps:
- AWS allocates a data centre cluster's emissions, including operational carbon and amortised embodied carbon for buildings and equipment, to the server racks based on each rack's power draw.
- They then allocate each rack's emissions to the services that ran on it in proportion to their share of the rack's resources, measured in usage units such as normalised instance hours for EC2 and gigabytes for S3.
- Then they allocate each service's emissions to customer accounts based on usage for services with a dedicated rack, and spend for all other services.
Scope 2 is built by estimating each cluster's electricity in MWh and multiplying by a location-based grid factor from the Amazon Carbon Methodology Document; the market-based figure then applies AWS's energy attribute certificates. Neither the grid factors nor the allocation factors are shown inside the tool. Embodied carbon is amortised over 6 years for hardware and 50 years for buildings.
AWS Sustainability gives you carbon and water withdrawals across scopes 1, 2 and 3, on market-based and location-based methods, by service, AWS Region and account at a monthly granularity.
What is AWS Sustainability good for?
For CSRD and other annual disclosures, AWS Sustainability gives an annual total per method, with an assurance letter you can hand to your auditor.
What can't AWS Sustainability be used for?
AWS's own guidance says its data "is used for reporting and understanding the high-level impact on a monthly basis" and not to be used for optimisation. Below are some common use cases our customers have told us they struggle to accomplish with the native tool.
| Use case | Why AWS Sustainability falls short | With Greenpixie |
|---|---|---|
| Confirming that rightsizing reduced emissions | You get one account total, published between the 15th and 21st of the following month, and it changes when AWS updates its methodology. A 10% saving from rightsizing, for example, can be masked by a methodology change. | Per resource, per hour |
| Measuring electricity per workload | AWS Sustainability does not share electricity figures, so the kWh behind a workload cannot be read from the tool. | kWh on every line item |
| Reporting emissions per customer | Software vendors who need to report what their product emitted for one customer cannot split AWS Sustainability's one figure per account, service and Region by customer, tenant, product line or tag. | By tag or account |
| Comparing AWS with other cloud providers | AWS says "there is no industry standard for allocating carbon emissions for cloud usage to customers". Each provider uses its own boundaries and factors, so an AWS figure next to an Azure figure compares two methodologies, so the figures are not like for like and the comparison is not useful. | One method across AWS, Azure and Google Cloud |
| Planning a workload for lower emissions | AWS Sustainability reports what already happened, with nothing by instance size, chip or hour. Adrian Cockcroft, head of sustainability at AWS when the tool launched, called it "pretty much useless for optimizing a workload". | Hourly grid intensity per region |
| Choosing an architecture for lower impact | AWS Sustainability offers no recommendations to optimise workloads for carbon efficiency. Under cost-based allocation, a cheaper architecture looks lower carbon. | Model a change from the rate card |
| Measuring AI emissions | AWS Sustainability has no token or model dimension, so AI services appear as service lines. The location-based data covers everything in the account, not just the AI element of it. | Per instance, model and token type |
| Choosing between AI models | Choosing a model on its footprint needs energy per token by model and inference region, which AWS Sustainability does not provide. | Energy per token for 500+ models |
What Greenpixie adds
Greenpixie adds energy, carbon and water columns to every line of the billing data your FinOps team already works with, and leaves the annual disclosure to AWS Sustainability.
For AI, every GPU instance family is included, and the AI token methodology gives energy, carbon and water per token, across scopes 1, 2 and 3, for over 500 open and closed models in varying configurations. The methodology is built on hardware benchmarking and published as a white paper.
Finding which workloads emit the most
Greenpixie calculates at the individual SKU and rate code level, the same granularity as the Cost and Usage Report, joined on SKU code. It typically covers 99% to 100% of relevant SKUs by spend, and you can allocate carbon to a team, product or customer in the same way as cost.
Reading electricity in kWh per line item
Each line item carries total electricity in kWh, the number engineers optimise against, and it does not move when a provider buys certificates.
Reporting water use
Each line item has two water columns, one for cooling water and one for the water used to generate the electricity.
Scheduling batch jobs and choosing Regions by hour
Greenpixie applies grid carbon intensity at hourly resolution for the grid area supplying each Region, so the same instance gets a different carbon figure at 2pm and 2am. That makes time-shifting and Region selection measurable.
Modelling a change before making it
The Greenpixie API serves rate cards with energy, carbon and water per unit for each SKU. You join them to your own billing data on the SKU code at whatever refresh rate you want, up to every 6 to 12 hours, and swapping the SKU models a change before you make it.
Seeing the data inside FinOps tools
Greenpixie's energy, carbon and water columns are generally available inside Flexera, CloudHealth, Cloudability, and Umbrella.
How AWS Sustainability and Greenpixie fit together
| Question | AWS Sustainability | Greenpixie |
|---|---|---|
| What was our AWS footprint last year, for the annual report? | Yes, assured, both methods | Supporting detail |
| Which accounts and Regions carry the most carbon? | Yes, monthly | Yes, down to the resource |
| How many kWh did this workload use? | No | Yes, per line item |
| Did last month's rightsizing reduce emissions? | Not reliably, because of restatements and monthly totals | Yes, per resource, per hour |
| What would moving to Graviton or to Stockholm change? | No | Yes, from the rate card |
| When should this batch job run? | No | Yes, hourly intensity |
| What did our AI tokens and GPU instances emit? | One service line, monthly | Per instance, and per model and token type |
| Can we report it to a customer, per tenant? | No | Yes, by tag or account |
FAQs
Is AWS Sustainability the same as the Customer Carbon Footprint Tool?
Yes, AWS Sustainability is its successor. The Customer Carbon Footprint Tool (CCFT) sat in the AWS Billing console and was deprecated on 30 June 2026 in favour of AWS Sustainability, which adds functionality and does not need Billing console permissions. The emissions data and methodology carry over, so the rest of this page applies to both.
Does AWS Sustainability include scope 3?
Yes. It covers categories 3.2 to 3.4, which are IT hardware, buildings and equipment, fuel- and energy-related activities, and upstream transport. It excludes emissions from developing and maintaining third-party software bought through AWS Marketplace.
Why does AWS Sustainability show 0 for my account?
The console and CSV show a figure once it rounds to 0.001 metric tons CO2e, which is 1 kg, and show 0 below 0.0005. Data Exports keep gram resolution.
How different are Greenpixie's and AWS's numbers for the same account and period?
AWS Sustainability allocates a share of AWS's reported footprint to you, while Greenpixie estimates what each resource drew from the grid, hour by hour, so the figures can vary a lot depending on what you run. Working out why Greenpixie's and AWS's numbers differ is difficult when a large part of your usage is in the "other" service category in the AWS console. Greenpixie provides an audit trail for every number, by resource ID, usage type and hour of the day.
Which carbon intensities and allocation factors does AWS Sustainability use?
AWS does not publish the carbon intensities or allocation factors inside the tool. The grid factors behind the location-based figures are in the Amazon Carbon Methodology Document, the market-based figures depend on how AWS allocates its energy attribute certificates, and the factors that allocate emissions to your account are not shown. AWS says the grid factors "are updated annually and validated as part of Amazon's carbon footprint assurance". You cannot see which factor produced your number, or when it changed.
Learn more
To learn more about Greenpixie's methodology and work with the data, take the Greenpixie Data Explorer course at the Greenpixie Academy.
For the other clouds, read Azure carbon optimization vs Greenpixie and Google Cloud Carbon Footprint vs Greenpixie. For an open-source option, read Cloud Carbon Footprint and its alternatives.
Measure your cloud emissions
See the energy, carbon and water behind your cloud bill
GPX Cloud adds energy, carbon and water data to AWS, Azure and Google Cloud billing data, line by line.
Sources
All statements about AWS Sustainability were checked against the sources below and are accurate as of Nov 10, 2026.
AWS
- AWS Sustainability user guide. AWS documentation
- AWS Sustainability service overview. AWS documentation
- Console visualisations. AWS Sustainability user guide
- Allocation methodology. AWS Sustainability user guide
- Methodology input data. AWS Sustainability user guide
- Calculating your energy usage. AWS Sustainability user guide
- Customer Carbon Footprint Tool release notes. AWS documentation, entries from March 2022 to June 2026
- Customer Carbon Footprint Tool methodology, version 3.0. Amazon Sustainability, October 2025
- Customer Carbon Footprint Tool methodology assurance letter. Amazon Sustainability
- Amazon Carbon Methodology Document. Amazon Sustainability
- Measure and track cloud efficiency with sustainability proxy metrics, part I. AWS Cloud Financial Management blog
- Updated carbon methodology for the AWS Customer Carbon Footprint Tool. AWS Cloud Financial Management blog, April 2025
Third parties
Greenpixie
- Methodology overview. Greenpixie documentation
- AI token methodology. Greenpixie documentation
- Greenpixie's AI Token Methodology: assessing the energy, water and CO2-eq impact of AI tokens. arXiv white paper
- Grid and regions methodology. Greenpixie documentation
- CUR enrichment. Greenpixie documentation
- Greenpixie API. Greenpixie documentation
- GPX Cloud. Greenpixie product page
- Flexera bolsters FinOps offering with Spot Eco, Ocean and Greenpixie partnership. Flexera press release, May 2025
- Greenpixie Data Explorer course. Greenpixie Academy

