Data Storage and Measuring Cloud Computing Emissions
In this blog post, we delve into two primary questions: Is opting for cloud storage more environmentally friendly than utilizing internal data servers, and how can one assess the carbon footprint of using the major cloud storage providers?
When it comes to the environmental impact of storing data, the answer isn’t black and white. For individual users with hard drive storage, it’s generally more eco-friendly to use the storage built into your device, as it avoids the need to power and cool additional devices. Businesses, however, often require more extensive storage solutions. Here, they face three main options:
1. Internal, On-premise Data Centres – The traditional, and increasingly rare option, and often less energy-efficient.
2. Colocation Data Centres: Where customers rent servers in an off-site location – an intermediate option.
3. Hyperscale Data Centres (Cloud Data Centres): These are the most energy-efficient, optimizing machine use, employing advanced cooling technologies, and frequently integrating on-site renewable energy.
Supporting this assertion is a study titled ‘The Environmental Footprint of Data Centers in the United States’ (Siddik et al, 2021), which indicates that hyperscale cloud data centres are superior in delivering more computing workloads with lower water and carbon intensity per workload.
How can we assess the carbon impact of our cloud storage use?
Moving to the second question: how can we assess the carbon impact of our cloud storage use? The good news is that big three – Amazon Web Service (AWS), Microsoft, and Google Cloud – offer tools for this very purpose:
– AWS: Customer Carbon Footprint Tool
– Microsoft (Azure): Emissions Impact Dashboard
– Google Cloud
But what do these tools cover?
Ideally, they would take a comprehensive approach including all emissions (Scope 1, 2, and 3), and with separate reporting of market-based and location-based emissions for Scope 2. It would also be beneficial to understand onsite renewable energy production at the data centres.
Here’s how each service stacks up in terms of emission scopes:
Microsoft’s tool is the most comprehensive, covering all scopes and offering both market-based and location-based options for Scope 2 emissions. Their sustainability efforts are well-documented, with detailed research and updates readily available on their website. They’ve pledged to be carbon negative by 2030 and aim to offset all historical emissions by 2050.
Google Cloud’s tool omits several categories in its emissions reporting, making it less comprehensive than Microsoft’s offering. The excluded categories are:
- Electricity Loss: Emissions from electricity lost during transmission and distribution.
- Fuel Extraction and Transportation: The life cycle emissions from fuel extraction, transportation, and the infrastructure used in generating grid electricity.
- Fugitive HVAC Emissions: Emissions from HVAC system coolants that escape into the atmosphere.
- Small Equipment Emissions: Emissions from minor equipment used by internet service providers’ partners.
- External Networking Equipment: Emissions from Google’s networking equipment located outside of data centres.
- End-of-Life Emissions: Downstream emissions from the disposal and decommissioning of data centre equipment and buildings.
Although less detailed compared to Microsoft’s tool, Google Cloud’s tool does account for some Scope 3 emissions. Google has set targets to achieve net-zero emissions across all operations and its value chain by 2030. This involves reducing the total of Scope 1, 2 (market-based), and 3 absolute emissions by 50% from their 2019 baseline before 2030. Google plans to invest in both nature-based and technology-based carbon removal solutions to offset their remaining emissions.
The Amazon Web Services tool accounts for Scope 1 emissions and market-based Scope 2 emissions but does not cover Scope 3. As a corporation, Amazon has made a commitment to reach net-zero carbon emissions by 2040 and, as of their 2022 report, 90% of their operations were powered by renewable energy.
In conclusion, the decision to opt for cloud storage versus internal servers carries significant environmental implications. For individual users, leveraging built-in storage is generally more eco-friendly, while businesses with larger data needs might find cloud storage, particularly through hyperscale data centres, a more sustainable option. These centres, renowned for their efficiency and renewable energy use, offer a compelling argument because of their reduced environmental impact.
And, thanks to the new tools available, it’s now possible to quantify the emissions associated with the use of cloud computing. However, the tools provided by AWS, Microsoft, and Google Cloud each offer varying degrees of insight into emissions, with Microsoft’s Emissions Impact Dashboard leading in comprehensiveness. It’s essential for users, especially corporate entities, to dive into these tools to obtain a detailed view of their emissions across all scopes. Despite their differences, each tool provides valuable information that can guide users in making more informed and environmentally conscious decisions.