# Viewing your carbon footprint
**CCFT deprecation notice**
The CCFT will be deprecated on June 30th 2026 in favor of the new AWS Sustainability service which offers additional functionalities and does not require Billing console permissions. [AWS Sustainability user guide](https://docs.aws.amazon.com/sustainability/latest/userguide)
You can use the Customer Carbon Footprint Tool (CCFT) to view estimates of the carbon emissions associated with your AWS products and services.
**Note**
CCFT isn't supported when using billing transfer in the following scenarios:
When signed in as the management account transferring its bills (bill source account) or a linked account under the bill source account, you can't access CCFT. Additionally, when signed in as the bill transfer account, you can't view CCFT data that reflects emissions from your bill source accounts.
**Topics**
+ [Getting started with the Customer Carbon Footprint Tool (CCFT)](#ccft-gettingstarted)
+ [Understanding the Customer Carbon Footprint Tool (CCFT)](ccft-overview.md)
+ [Calculating your energy usage](ccft-energy.md)
+ [Understanding your carbon emission estimations](ccft-estimation.md)
## Getting started with the Customer Carbon Footprint Tool (CCFT)
The Customer Carbon Footprint Tool is available for all accounts. Your data is updated monthly.
**Note**
If a report isn't available for your account, your account might be too new to show data, or your carbon footprint is under 0.5 kgCO2e in the reporting month. For more information, see [Understanding the Customer Carbon Footprint Tool (CCFT)](ccft-overview.md).
**To use the Customer Carbon Footprint Tool**
1. Sign in to the AWS Management Console and open the AWS Billing and Cost Management console at [https://console.aws.amazon.com/costmanagement/](https://console.aws.amazon.com/costmanagement/).
1. On the navigation pane, choose **Customer Carbon Footprint Tool** under **Cost and Usage Analysis**.
1. Under **Customer Carbon Footprint Tool**, choose your **Start month** and **End month**.
### IAM policies
You must have the IAM permission `sustainability:GetCarbonFootprintSummary` to access the Customer Carbon Footprint Tool and data. For more information regarding IAM permissions, see [Identity and Access Management for AWS Billing](security-iam.md).
### AWS Organizations users
If you're signed in as a management account of AWS Organizations, the Customer Carbon Footprint Tool dashboard and spreadsheet download report the consolidated member account data for the duration that those member accounts were a part of your organization.
If you're a member account, the Customer Carbon Footprint Tool reports emission data for all the periods. This is regardless of any changes that might have occurred to your account's associated membership in an organization.
# Understanding the Customer Carbon Footprint Tool (CCFT)
**CCFT deprecation notice**
The CCFT will be deprecated on June 30th 2026 in favor of the new AWS Sustainability service which offers additional functionalities and does not require Billing console permissions. [AWS Sustainability user guide](https://docs.aws.amazon.com/sustainability/latest/userguide)
This page defines each console section, so you can understand the information provided in depth.
The unit of measurement for carbon emissions is metric tons of carbon dioxide-equivalent (MTCO2e), an industry-standard measure. This measurement considers multiple greenhouse gases, including carbon dioxide, methane, and nitrous oxide. All greenhouse gas emissions are converted to MTCO2e using their respective Global Warming Potential (GWP) values as defined by the Intergovernmental Panel on Climate Change (IPCC). This standardized approach enables organizations to express the climate impact of various greenhouse gases in a single, comparable unit.
Carbon emissions data is available for the previous 38 months. This is to allow a simple process for annual comparisons for the past three years. New data is usually published between the 15th - 21st of the month after the usage occurs. The Customer Carbon Footprint Tool shows your carbon footprint at the 0.001 MTCO2e (1 kgCO2e) resolution. If your emissions are lower than 0.0005 MTCO2e (0.5 kgMTCO2e) in the reporting month, it will appear as `0`. To see your carbon footprint at the 0.000001 MTCO2e (1 gram) resolution, see [Data Exports](https://docs.aws.amazon.com/cur/latest/userguide/what-is-data-exports.html).
To calculate your energy usage using the CCFT location-based emissions data, see [Calculating your energy usage](ccft-energy.md).
To learn more about historical changes to the features, methodology, and other information, see the [https://docs.aws.amazon.com/ccft/latest/releasenotes/what-is-service.html](https://docs.aws.amazon.com/ccft/latest/releasenotes/what-is-service.html).
**Your carbon emissions summary**
This section shows your estimated AWS emissions and estimated emissions savings. The tool shows Scope 2 and Scope 3 emissions calculated using the market-based method (MBM) by default. You can see your emissions calculated using the location-based method (LBM) by choosing **LBM** in the **Calculation method filter** on the dashboard. Emissions savings are the difference between the carbon footprint emissions calculated using the location-based method (LBM) and the market-based method (MBM). For more information about LBM and MBM, see [Input data](ccft-overview-input.md).
**Your AWS carbon emissions**
This section shows trends in your carbon emissions over time, broken down by your top AWS Regions. You see the top 5 Regions by default and any other Regions are grouped under **Other**. To see emissions across all Regions, choose the **Emissions by AWS Region** tab.
**Your emissions by service**
This section shows the carbon emissions resulting from your usage of Amazon Elastic Compute Cloud (EC2), Amazon Simple Storage Service (S3), and Amazon CloudFront (CloudFront). Any other AWS products and services are grouped under **Other**.
**Your emissions by AWS Region**
This section shows the carbon emissions associated with each applicable AWS Region. For example, `US East (Ohio)`, `Europe (London)`. Emissions from global services, such as Amazon CloudFront, are reported under **Global**.
To see your emissions by scope (Scope 1, 2, 3) see [What is AWS Data Exports?](https://docs.aws.amazon.com/cur/latest/userguide/what-is-data-exports.html)
## Downloading your carbon emissions data
You can access your carbon emissions data in bulk using one of the two options available on the top right of the Customer Carbon Footprint Tool console page.
**Download CSV**
Choose this option to download a CSV file containing your historical data up to 38 months. This file includes data by month, service, and AWS Region. The data in this file is always calculated using the latest methodology version.
**Download CSV (legacy version)**
Choose the dropdown next to **Download CSV** to find this option. This option is temporarily present after a new methodology version is released. This contains your carbon estimates using the previous methodology calculations. You can use this to compare data between the different methodology versions. For example, methodology version 2 is released on April 2025; the **Download CSV** (legacy version) will contain data calculated with version 1.
To access your historical data using previous methodologies after a new one is released, make sure you have a **Data Export **set up. We will not override data exported to your Amazon S3 bucket that is calculated using previous methodologies.
**Create custom data export**
Choose this to navigate to the **Data Exports**. Then, you can create carbon emissions data exports using basic SQL and visualize your data by integrating with Quick. By using custom data exports, you can access account level details for all accounts in a given organization.
# Calculating your energy usage
**CCFT deprecation notice**
The CCFT will be deprecated on June 30th 2026 in favor of the new AWS Sustainability service which offers additional functionalities and does not require Billing console permissions. [AWS Sustainability user guide](https://docs.aws.amazon.com/sustainability/latest/userguide)
**Note**
The energy data calculated using this method is for informational purposes only. Do not use this information for optimization.
This method is not supported in the Canada (Central) and Africa (Cape Town) Regions due to their specific power infrastructure.
The Customer Carbon Footprint Tool (CCFT) provides data to calculate the energy use of your cloud carbon footprint. By combining the Scope 2 location-based emissions method (LBM) data with publicly available grid emissions factors, you can determine the estimated energy footprint of your AWS workloads. For more information about energy emission factors used by Amazon, see [Amazon Carbon Methodology Document](https://sustainability.aboutamazon.com/carbon-methodology.pdf).
**Note**
Do not use the total LBM emissions provided in the CCFT to calculate your energy usage, use instead Scope 2 LBM from [Data Exports](https://docs.aws.amazon.com/cur/latest/userguide/what-is-data-exports.html) (column: `total_scope_2_lbm_emissions_value`). The total LBM number includes Scope 1 and Scope 3, which are not part of the energy calculation, and using this data will result in over-estimated energy figures.
To determine the estimated energy consumption behind your cloud carbon footprint, divide the location-based emissions by the corresponding grid emissions factor. Be sure to apply unit conversions as needed:
`Energy consumption = Location‐based emissions / Grid emissions factor`
**Example**
If the grid emissions factor was 500 kg CO2e/MWh, and your cloud usage generated LBM emissions are 100 MTCO2e in the US West (Oregon) Region in 2025, calculate energy usage as follows:
1. Multiply 100 MTCO2e by 1,000 to convert metric tons to kilograms.
1. Divide the result by the grid emissions factor of 500 kgCO2e for the US West (Oregon) Region.
`(100 MTCO2e * 1000) / 500 kgCO2e/MWh = 200 MWh`
# Understanding your carbon emission estimations
**CCFT deprecation notice**
The CCFT will be deprecated on June 30th 2026 in favor of the new AWS Sustainability service which offers additional functionalities and does not require Billing console permissions. [AWS Sustainability user guide](https://docs.aws.amazon.com/sustainability/latest/userguide)
The Customer Carbon Footprint Tool quantifies customer-specific greenhouse gas (GHG) emissions associated with the use of AWS cloud services. The tool covers the full range of cloud products.
The methodology adopted in the Customer Carbon Footprint Tool is based on the data sources and allocation methods outlined in the following standards:
+ [GHG Protocol](https://ghgprotocol.org/) and its underlying standard [ISO 14064](https://www3.epa.gov/ttnchie1/conference/ei16/session13/wintergreen.pdf)
+ [GHG Protocol Product Life Cycle Accounting and Reporting Standard](https://ghgprotocol.org/product-standard/) and associated [Information and Communication Technology (ICT) sector guidance](https://ghgprotocol.org/sites/default/files/2023-03/GHGP-ICTSG%20-%20ALL%20Chapters.pdf).
+ [ISO 14040](https://www.iso.org/standard/37456.html) and [ISO 14044](https://www.iso.org/standard/38498.html) for Life Cycle Assessment (LCA)
The Customer Carbon Footprint Tool methodology uses elements from these standards to define our [system boundaries](ccft-overview-boundaries.md), [input data](ccft-overview-input.md), and [allocation approach](ccft-overview-allocation.md) and is updated over time based on evolving data, climate science, and more. To see the full methodology document for the current version of the methodology and the third-party verification letter see [Reports](https://sustainability.aboutamazon.com/reporting) on the *Amazon Sustainability* page. When AWS releases a new version of the methodology, historical data is recalculated using the updated version to ensure accurate comparisons over time.
**Note**
Scope 2 and Scope 3 FERA market-based emissions (MBM) are estimates based on projected purchases of Energy Attribute Certificates (EACs), and are subject to change. To mitigate, AWS will recalculate previous year’s emissions using the actual EAC purchases in H1 of the following year. For example, 2025 data will be republished by June 2026 using the latest and greatest inputs.
## Regions, usage, and billing data factors
Electricity grids in different parts of the world use various sources of power. Some use carbon-intense fuels (for example, coal), and some are primarily low-carbon hydro or other renewables. The locations of Amazon's renewable energy projects also play a role, because the energy produced by these projects is accounted against our emissions from Regions on the same grid. As a result, not all AWS Regions have the same carbon intensity.
There are some Regions where high usage results in relatively low emissions. There are others where the low usage results in higher emissions. For example, emissions from usage in European AWS Regions often represents a smaller share of total emissions even if that is an area with high usage, because there are more renewables on the grid. AWS Regions in Asia Pacific can represent a larger share of total emissions even when customer usage in those Regions is smaller, given the lower availability of low carbon energy in some Asia Pacific Regions. Carbon estimates are based on usage only, and one-time charges such as upfront Savings Plan purchases, won't result in similar increases in carbon emissions.
## Customer Carbon Footprint Tool and Amazon's carbon footprint report
Amazon's carbon footprint report is a part of our annual sustainability report. This covers Scope 1 through 3 emissions for all Amazon operations, including Amazon Web Services. The customer carbon footprint report provides you with the emissions that attribute to your own AWS usage. For more information, see [Amazon Sustainability](https://sustainability.aboutamazon.com/).
**Topics**
+ [Regions, usage, and billing data factors](#ccft-estimation-billing)
+ [Customer Carbon Footprint Tool and Amazon's carbon footprint report](#ccft-estimation-report)
+ [System boundary](ccft-overview-boundaries.md)
+ [Input data](ccft-overview-input.md)
+ [Allocation approach](ccft-overview-allocation.md)
# System boundary
**CCFT deprecation notice**
The CCFT will be deprecated on June 30th 2026 in favor of the new AWS Sustainability service which offers additional functionalities and does not require Billing console permissions. [AWS Sustainability user guide](https://docs.aws.amazon.com/sustainability/latest/userguide)
The system boundary defines what activities and related emissions are accounted for in the CCFT calculations. The CCFT is informed by the GHG Protocol’s classification of emissions, which breaks down a company’s emissions into three `scopes`.
+ **Scope 1**: Emissions are direct emissions from owned or controlled sources.
+ **Scope 2**: Emissions are indirect emissions from the production of purchased energy.
+ **Scope 3**: Emissions are all indirect emissions (not included in scope 2) that occur in the value chain of the reporting company, including both upstream and downstream emissions (for example, manufacturing of hardware, end-of-life emissions).
**Scope 1**
The CCFT includes emissions from fuel combustion in emergency backup generators and emissions from refrigerant use and natural gas consumption in AWS-owned or controlled facilities. This includes locations where AWS has operational control on the server racks deployed that support cloud services (for example, "colo" data centers). The model also includes emissions from certain edge sites (CloudFront emissions are included).
**Scope 2**
The CCFT reports Scope 2 emissions from AWS owned or controlled facilities that support cloud services, as well as certain edge sites (For example, CloudFront emissions are included), using both the market-based method (MBM) and location-based method (LBM) calculations.
**Scope 3**
The CCFT accounts for:
- Emissions from fuel- and energy-related activities (FERA under the GHG Protocol). This includes upstream emissions from purchased fuels and electricity, as well as emissions from transmission and distribution losses, for facilities within the system boundary.
- IT hardware embodied carbon - manufacturing emissions from server racks deployed in AWS-owned or operated data center facilities.
- Data center building embodied carbon - manufacturing emissions from AWS owned or operated data center buildings.
- Non-IT equipment embodied carbon - manufacturing emissions from non-IT equipment deployed in AWS owned or operated data center facilities.
The Customer Carbon Footprint Tool excludes emissions associated with AWS warehouses, manufacturing facilities, and offices. These emissions are not attributable to the provision of cloud services. Any emissions stemming from sites ran in customer facilities (for example, Amazon Cloud Extension, Embedded Points of Presence, AWS Outposts sites) are not covered by Customer Carbon Footprint Tool at this time. For more information, see the [CCFT Methodology Document](http://sustainability.aboutamazon.com/aws-customer-carbon-footprint-tool-methodology.pdf).
# Input data
**CCFT deprecation notice**
The CCFT will be deprecated on June 30th 2026 in favor of the new AWS Sustainability service which offers additional functionalities and does not require Billing console permissions. [AWS Sustainability user guide](https://docs.aws.amazon.com/sustainability/latest/userguide)
This section outlines the sources of data and transformations that occur upstream of the Customer Carbon Footprint Tool to define Scope 1, Scope 2, and Scope 3 carbon emissions for each AWS cluster. To understand the full methodology, see the [CCFT Methodology Document](http://sustainability.aboutamazon.com/aws-customer-carbon-footprint-tool-methodology.pdf).
**Scope 1**
Amazon generates and assures Scope 1 activity data for its annual footprint every year. To bridge the gap between Amazon's annual reporting and CCFT's monthly cadence, AWS uses unassured primary Scope 1 activity data to determine monthly emissions for the current month. Some of the activity data might not be available at the time of publishing the monthly report, therefore translating in an underestimation of Scope 1 emissions. We update our estimates when recasting, to align Scope 1 emissions reported in the CCFT with the assured data.
**Scope 2**
Similar to Scope 1, the CCFT methodology closely follows Amazon’s footprint methodology. In line with Amazon’s approach, we prioritize accuracy of data at the time of publishing in the CCFT, only falling back to other sources (for example, estimated energy consumption) when the primary source of data (for example, actual energy consumption) is not reasonably available.
AWS first estimates cluster and month level location-based (LBM) emissions by estimating energy consumption (MWh) and multiplies this by LBM emission factors.
Location-based method (LBM) is a GHG Protocol method used in Scope 2 carbon emissions accounting that reflects the average emissions intensity of grids where energy consumption occurs.
After LBM, AWS considers market-based contractual instruments such as Energy Attribute Certificates (EACs), Power Purchase Agreements (PPA) etc., to reflect our carbon-free energy projects and calculate market-based (MBM) emissions. This is in line with the Quality Criteria outlined in the GHG Protocol Scope 2 guidance.
Market-based method (MBM) is a GHG Protocol method used in Scope 2 carbon emissions accounting that reflects supplier-specific emissions intensity after accounting for Energy Attribute Certificates (EACs). For example, a company’s renewable energy purchases.
To learn more about the differences between LBM and MBM, see [GHG Protocol Scope 2 Guidance](https://ghgprotocol.org/sites/default/files/2023-03/Scope%202%20Guidance.pdf).
**Scope 3**
Fuel and energy related activities: For upstream emissions from purchased fuels, AWS collects fuel activity data and applies emission factors for fuel extraction, production, and transportation. For upstream emissions of purchased electricity and transmission and distribution (T&D) losses using location-based emissions (LBM), AWS multiplies the estimated energy consumption (MWh) by the relevant emission factor. For market-based emissions (MBM), AWS also accounts for Energy Attribute Certificates (EACs).
IT hardware: AWS uses a comprehensive cradle-to-gate approach that tracks emissions from raw material extraction through manufacturing and transportation to AWS data centers. The methodology employs four calculation pathways: process-based life cycle assessment (LCA) with engineering attributes, extrapolation, representative category average LCA, and economic input-output LCA. AWS prioritizes the most detailed and accurate methods for components that contribute significantly to overall emissions.
Buildings and equipment: AWS follows established whole building life cycle assessment (wbLCA) standards, considering emissions from construction, use, and end-of-life phases. The analysis covers data center shells, rooms, and long-lead equipment such as air handling units and generators. The methodology uses both process-based life cycle assessment models and economic input-output analysis to ensure comprehensive coverage.
The Scope 3 emissions are then amortized over the assets' service life (6 years for IT hardware, 50 years for buildings) to calculate monthly emissions that can be allocated to customers. This amortization ensures that we fairly distribute the total embodied carbon of each asset across its operational lifetime, accounting for scenarios such as early retirement or extended use.
To ensure data quality, we use a Composite Quality Score (CQS) system and perform multiple validation checks throughout our calculation process. This systematic approach lets us provide customers with detailed, verifiable carbon footprint data while maintaining transparency about our calculations and assumptions.
# Allocation approach
**CCFT deprecation notice**
The CCFT will be deprecated on June 30th 2026 in favor of the new AWS Sustainability service which offers additional functionalities and does not require Billing console permissions. [AWS Sustainability user guide](https://docs.aws.amazon.com/sustainability/latest/userguide)
The carbon allocation model uses a top-down approach to calculate customers' carbon footprint associated with the AWS cloud service usage. AWS prioritizes `physical allocation` (also known as usage-based allocation) and consider `economic allocation` as a secondary option.
The model takes operational and capital emissions associated with each AWS cluster and performs a series of transformations to break down such emissions into several logical segments. Conceptually, the model works using the following logical transformation workflow:
1. Allocate cluster-level emissions (for example, operational carbon emissions as well as building and equipment amortized embodied carbon) to server racks in the cluster, using the server racks' power draw. Add the server racks amortized embodied carbon associated with each rack in that given cluster.
1. Allocate carbon emissions associated with server racks to AWS cloud services based on utilization of server racks resources, accounting for interdependencies. We use physical allocation for services with dedicated server racks, and economic allocation for other services.
1. Allocate carbon emissions associated with each cloud service to individual customer accounts. We use physical allocation for services with dedicated server racks, and economic allocation for other services.
![\[A diagram of AWS carbon emissions, showing the three steps of logical workflow.\]](http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/images/ccft-allocation-v02.png)