AWS Launches Sustainability Console for Carbon Emissions Tracking

AWS launches dedicated carbon tracking interface for business customers

Amazon Web Services has introduced the AWS Sustainability Console, a new interface that gives businesses direct access to carbon emissions data from their cloud usage. Previously, this information lived inside the billing console, which meant finance teams controlled access. Sustainability professionals often couldn’t see the data they needed.

The new console changes that. It uses separate permissions, so your environmental team can track emissions without needing access to cost information. For businesses managing net zero targets or responding to supply chain carbon questions, this matters. You can now give the right people the right access.

The tool covers Scope 1, 2, and 3 emissions. It breaks down data by AWS region and individual services such as Amazon EC2, S3, and CloudFront. Historical records go back to January 2022, which gives you enough data to spot trends and measure progress over time.

What the console actually does for your business

The interface provides preset monthly and annual reports in CSV format. You can download these using either the Location-Based Method or Market-Based Method, depending on how your organization accounts for renewable energy. Both approaches align with the Greenhouse Gas Protocol, the framework most auditors and regulators recognize.

Custom reports let you filter by time period, accounts, regions, and specific services. This means you can isolate the carbon footprint of a particular project, department, or geographical operation. For example, a retailer running separate environments for UK and EU customers could compare the emissions profile of each region.

AWS has also released an API for programmatic access. Consequently, you can automate data retrieval and build it into your existing reporting workflows. Finance teams already automate cost reports. Now sustainability teams can do the same with carbon data.

The API supports filtering, grouping, and pagination across different time granularities. You might pull monthly data for detailed tracking or quarterly summaries for board reports. Integration options mean you can feed this information into your corporate sustainability platform or ESG disclosure tools.

How AWS calculates and presents your cloud emissions

The methodology follows the Greenhouse Gas Protocol Corporate Accounting and Reporting Standard. Emissions appear in metric tons of CO2 equivalent, the standard unit for carbon accounting. AWS hasn’t changed how it calculates these figures from the previous tool.

Scope 1 emissions cover direct emissions from AWS-owned assets. Scope 2 includes purchased electricity. Scope 3 captures indirect emissions from the supply chain and other sources. For most businesses, cloud usage sits in their Scope 3 emissions, specifically in the purchased goods and services category.

The console shows which AWS regions generate the most emissions from your workloads. Different regions have different grid carbon intensities. For instance, regions powered by hydroelectric or nuclear energy typically show lower emissions than those relying on coal or natural gas. You can use this data to make informed decisions about where to run workloads.

Amazon QuickSight offers an additional dashboard called Sustainability Proxy Metrics. This visualizes infrastructure usage patterns such as vCPU hours, storage capacity, and data transfer volumes. These proxy metrics help you identify inefficient resource allocation before it translates into unnecessary emissions.

Five practical facts about the AWS Sustainability Console

• Access costs nothing extra and works through the standard AWS Management Console that your teams already use for other services.
• Historical emissions data extends back to January 2022, providing two full years of baseline information for trend analysis and target setting.
• The permissions model separates carbon data access from billing access, so sustainability teams don’t need financial system privileges to do their work.
• Both Location-Based and Market-Based accounting methods are supported, giving you flexibility in how you report renewable energy purchases and contractual arrangements.
• API access enables automated reporting cycles, which reduces manual data handling and makes it easier to include cloud emissions in regular ESG disclosures.

Understanding AWS’s wider decarbonization progress and commitments

Amazon made its Climate Pledge in 2019, committing to net zero carbon across all operations by 2040. That’s ten years ahead of the Paris Agreement timeline. AWS forms a significant part of that commitment, given the energy requirements of data centers.

In 2024, AWS reported 100% renewable energy matching for 24 data center regions. This means the company purchases or generates renewable energy equivalent to what these facilities consume. However, renewable matching doesn’t mean every electron comes from renewable sources at every moment. Grid constraints and weather variability mean the actual energy mix fluctuates.

New data center components now use up to 46% less mechanical energy than previous generations. Meanwhile, AWS claims workloads running on its infrastructure are up to 4.1 times more energy efficient than typical on-premises deployments. If accurate, this translates to a 99% reduction in associated carbon footprint when businesses migrate from their own servers to AWS.

Water consumption has also received attention. AWS aims for water positivity by 2030, meaning it will return more water to communities than it uses in operations. The company reports reaching 53% of this target in 2024, supported by sensors and cloud analytics that optimize cooling systems.

Commercial implications for UK businesses using cloud services

Many businesses now face questions about their supply chain emissions. Public sector suppliers must address Procurement Policy Note 06/21, which requires carbon reduction plans. Large companies preparing for mandatory climate reporting under UK regulations need Scope 3 data. Cloud infrastructure represents a measurable chunk of that total.

Previously, getting this information meant chasing your cloud provider or making rough estimates. The AWS Sustainability Console removes some of that friction. You can pull exact figures for your usage, broken down by service and region. This helps you answer tender questions, complete SECR disclosures, or respond to investor ESG queries with actual data rather than approximations.

The regional breakdown creates opportunities for emissions reduction without changing your total cloud spend. Moving workloads from high-carbon regions to lower-carbon alternatives might reduce your footprint while maintaining performance. For applications that don’t require specific geographic hosting, this becomes a practical lever.

However, emissions aren’t the only consideration. Data sovereignty rules, latency requirements, and customer location all constrain where you can realistically host services. A UK business serving UK customers will likely need UK-based infrastructure regardless of its carbon intensity. Nevertheless, for backup systems, development environments, or global applications, you now have carbon data to inform those location decisions.

Supply chain transparency matters more as corporate sustainability expectations tighten. Major customers increasingly audit their suppliers’ environmental performance. Demonstrating that you track and manage your cloud emissions shows due diligence. The API access means you can integrate this into automated reporting, rather than scrambling for data when a customer requests it.

Where AWS sits compared to other major cloud providers

Microsoft Azure and Google Cloud Platform both offer similar carbon reporting tools. Microsoft provides the Emissions Impact Dashboard, which also covers Scope 1, 2, and 3 emissions from Azure usage. Google’s Carbon Footprint tool reports emissions data and shows how their infrastructure improvements reduce customer footprints over time.

All three providers use variations of the Greenhouse Gas Protocol methodology. They differ in how they present data, what granularity they offer, and how they account for renewable energy purchases. The accounting methods affect reported figures significantly, so comparing raw numbers across providers requires careful attention to methodology.

For businesses using multiple cloud providers, this creates both an opportunity and a challenge. You can now get emissions data from each platform, which is better than no data. However, consolidating it into a single view of your total cloud footprint requires manual work or custom integration. No standardized format exists yet for cloud carbon reporting, though industry groups are working on it.

The practical effect is that businesses with multi-cloud strategies need to track each provider separately. Your total Scope 3 emissions from cloud usage become the sum of AWS, Azure, and GCP footprints. Each provider’s dashboard shows only its own piece of your infrastructure.

Questions about methodology, accuracy, and what the data actually represents

Carbon accounting for cloud services involves assumptions and estimates. AWS doesn’t measure the actual carbon emissions from each individual virtual machine you run. Instead, it allocates total data center emissions across customer workloads based on resource consumption. The methodology document explains this process, but it still relies on modeling rather than direct measurement.

Location-Based and Market-Based methods produce different results. The Location-Based method uses the average grid carbon intensity for each region. The Market-Based method accounts for renewable energy contracts and certificates. If AWS has purchased renewable energy for a region, the Market-Based figure will be lower, sometimes dramatically so. Your choice of method affects reported emissions, so consistency matters more than which method you pick.

The Scope 3 boundary is particularly fuzzy. It includes embodied carbon in hardware manufacturing, employee commuting, and other indirect sources. Different organizations draw this boundary differently, which means AWS’s Scope 3 reporting might not align perfectly with your own definitions. For most purposes, this doesn’t matter. You’re tracking changes over time, and the methodology remains consistent period to period.

Historical data starts in January 2022, which limits how far back you can look. If you need to establish a baseline from 2020 or 2021, you’ll need to estimate or use alternative sources. For forward-looking target setting, two years provides enough information to understand your usage patterns and identify reduction opportunities.

Recommended resources for cloud carbon management and reporting standards

The Greenhouse Gas Protocol publishes the standards that underpin most corporate carbon accounting. Their Corporate Accounting and Reporting Standard explains Scope 1, 2, and 3 categories in detail. The Scope 3 guidance specifically addresses purchased goods and services, which is where cloud emissions typically appear in your inventory.

Amazon’s sustainability reporting site provides detailed information about AWS’s infrastructure improvements, renewable energy projects, and methodology. The reports include data center efficiency metrics, water usage, and renewable energy capacity by region. This context helps you understand what sits behind the numbers in the Sustainability Console.

For UK businesses, the Procurement Policy Note 006 sets out carbon reduction plan requirements for government suppliers. While it doesn’t prescribe specific cloud reporting methods, demonstrating that you track and manage cloud emissions supports compliance. The guidance emphasizes measurement, reduction targets, and progress reporting, all of which the AWS tool facilitates.

Our compliance support services help UK businesses navigate carbon reporting requirements, including how to incorporate cloud emissions data into broader ESG disclosures and reduction strategies.