System boundary
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 3 emissions are not included in the CCFT today.
- Scope 1
The CCFT includes emissions from fuel combustion in emergency back-up generators from AWS-owned or controlled facilities that support cloud services. The CCFT also includes emissions from certain edge sites (For example, CloudFront emissions are included), using both the market-based method (MBM) and location-based method (LBM) calculations.
- 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.
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
