AWS Sustainability コンソール発表、Scope1〜3排出量をAPIで取得可能に Announcing the AWS Sustainability console: Programmatic access, configurable CSV reports, and Scope 1–3 reporting in one place

AWS has unveiled the new AWS Sustainability console, a successor to the long-standing Customer Carbon Footprint Tool (CCFT). The new console consolidates greenhouse gas emissions reporting for AWS workloads and adds capabilities aimed squarely at enterprises facing growing regulatory and stakeholder pressure to disclose climate data.

The most significant addition is programmatic access. Until now, CCFT data was available only through the AWS Management Console or static CSV downloads, which made integration with internal sustainability platforms cumbersome. The new console exposes emissions data via APIs, allowing customers to pull figures directly into ESG dashboards, ERP systems, or audit pipelines. Reports can also be generated as configurable CSVs, letting teams slice data by account, Region, or service to match the granularity required by internal stakeholders or external auditors.

A second headline feature is unified reporting across Scope 1, 2, and 3 emissions in line with the Greenhouse Gas Protocol. Scope 1 covers direct emissions, Scope 2 covers purchased energy, and Scope 3 spans the broader value chain. For AWS customers, cloud usage typically falls under their own Scope 3 inventory, but AWS now provides visibility into its associated Scope 1 and 2 footprint as well. This integrated view is intended to give customers a clearer methodological basis when their own disclosures are challenged by auditors or regulators.

The timing reflects a sharp tightening of climate disclosure rules worldwide. The EU's Corporate Sustainability Reporting Directive (CSRD) is now phasing in mandatory reporting for tens of thousands of companies, while the SEC in the United States and Japan's SSBJ are advancing their own frameworks. Hyperscalers have responded competitively: Microsoft offers the Emissions Impact Dashboard for Azure, and Google Cloud provides its Carbon Footprint tool, both of which already supported some level of API or BigQuery export. AWS's previous tool was widely seen as lagging in flexibility, so this update appears intended to close that gap.

For practitioners, the practical implications are notable. Sustainability teams that previously stitched together spreadsheets each quarter can move toward continuous, automated reporting. FinOps and platform engineering groups may also find value in correlating emissions data with cost and architectural choices, such as Region selection or instance family. AWS has historically published methodology documents describing how it allocates emissions to customers, and the granularity offered here is likely to invite further scrutiny from sustainability consultants and assurance providers.

While AWS has not detailed every methodological change, the move toward API-first access and Scope 1-3 unification suggests the console is positioned as foundational infrastructure for compliance-grade reporting rather than a purely informational tool. Customers preparing for assurance engagements should still validate AWS-reported figures against their own boundary definitions, but the new capabilities materially reduce the manual effort involved.