https://carbonifer.io/

Command Line Tool to control carbon emission of your cloud infrastructure. Reading Terraform files, carbonifer plan will estimate future Carbon Emissions of infrastructure and help make the right choices to reduce Carbon footprint.

Scope

This tool currently estimates usage emissions, not embodied emissions (manufacturing, transport, recycling...). It is not a full LCA (Life Cycle Assessment) tool.

This tool can analyze Infrastructure as Code definitions such as:

• Terraform files
• (more to come)

It can estimate Carbon Emissions of:

• Google Cloud Platform
  • [x] Compute Engine
  • [x] Compute Instances (generic and custom machine types, and from template)
  • [x] Disks (boot, persistent and region-persistent, HDD or SSD)
  • [X] Machines with GPUs
  • [x] Cloud SQL
  • [x] Instance Group (including regional and Autoscaler)
  • [x] Google Kubernetes Engine (GKE) cluster
• Amazon Web Services
  • [x] EC2 (including inline root, elastic, and ephemeral block storages)
  • [x] EBS Volumes
  • [x] RDS
  • [x] AutoScaling Group

The following will also be supported soon:

• Amazon Web Services
  • [ ] Elastic Kubernetes Service (EKS)
  • [ ] Elastic Container Service (ECS)
• Azure
  • [ ] Virtual Machines
  • [ ] Virtual Machine Scale Set
  • [ ] SQL

NB: This list of resources will be extended in the future A list of supported resource types is available in the Scope document.

Install Carbonifer CLI

Magic one-liner bash script

Using bash and curl. By default, it will install the latest version to /usr/local/bin:

bash curl -sfL https://raw.githubusercontent.com/carboniferio/carbonifer/main/install.sh | sudo bash

if you need more flexibility

bash export DEST_DIR=/path/to/dest/dir export VERSION=v1.2.3 curl -sSL https://github.com/username/repo/install.sh | bash

Go install

If you have go installed, you can use:

bash go install github.com/carboniferio/carbonifer@latest

Go will automatically install it in your $GOPATH/bin directory which should be in your $PATH.

Docker alternative

Alternatively, you can use the Docker image:

bash git clone https://github.com/carboniferio/carbonifer.git cd carbonifer docker build -t carbonifer . docker run -it --rm -v <your_tf_folder_with_config>:/tmp/ carbonifer ./carbonifer --config=/tmp/config.yaml plan /tmp/

Manual install

Download the latest release from releases page

Plan

carbonifer plan will read your Terraform folder and estimates Carbon Emissions.

```bash $ carbonifer plan

Average estimation of CO2 emissions per instance:

resource count replicas emissions per instance

googlecomputedisk.first 1 1 0.0422 gCO2eq/h
googlecomputeinstance.first 1 1 33.5977 gCO2eq/h
googlecomputeinstance.second 1 1 0.4248 gCO2eq/h
googlecomputeregiondisk.regional-first 1 2 0.0844 gCO2eq/h
googlesqldatabaseinstance.instance 1 2 2.0550 gCO2eq/h
googlecomputesubnetwork.first unsupported
googlecomputenetwork.vpc_network unsupported

Total 7 38.3433 gCO2eq/h

```

In case instances are in a managed group (GCP managed instance group, AWS autoscaling group...), the instances appear in the group name, with a count > 1 and emissions are shown for 1 instance. Of course, Total will sum all instances of the group:

```bash

resource type name count emissions per instance

googlecomputeinstancegroupmanager my-group-manager 3 0.5568 gCO2eq/h
googlecomputenetwork vpcnetwork unsupported
googlecompute_subnetwork first unsupported

                                      Total              3        1.6704 gCO2eq/h        

```

The report is customizable (text or JSON, per hour, month...), cf Configuration

Existing terraform plan file

In case you want to read an existing terraform file, you need to pass it as argument. It can either be a raw tfplan or a json plan. This is useful when some variables or credentials are required to run terraform plan. In that case carbonifer plan won't try to run terraform plan for you, and won't expect to have any credentials or variable set (via env var...)

bash carbonifer plan /path/to/my/project.tfplan

Methodology

This tool will:

1. Read resources from Terraform folder
2. Calculate an estimation of power used by those resources in Watt per Hour
3. Translate this electrical power into an estimation of Carbon Emissions depending on

We can estimate the Carbon Emissions of a resource by taking the electric use of a resource (in Watt-hour) and multiplying it by a carbon emission factor. This carbon emission factor depends on:

• Cloud Provider
• Region of the Data Center
• The energy mix of this region/country
  • Average
  • (future) real-time

Those calculations and estimations are detailed in the Methodology document.

Limitations

We are currently supporting only

• resources with a significative power usage (basically anything that has CPU, GPU, memory or disk)
• resources that can be estimated beforehand (we discard for now data transfer)

Because this is just an estimation, the actual power usage and carbon emission should probably differ depending on the actual usage of the resource (CPU %), and actual grid energy mix (could be weather dependent), ... But that should be enough to make decisions about the choice of provider/region, instance type...

See the Scope document for more details.

Usage

carbonifer plan [target]

• target can be
  • a terraform project folder
  • a terraform plan file (json or raw)
  • default: the current folder

Prerequisites

• Terraform :
  • Carbonifer uses Terraform:
  • terrafom executable available in $PATH
  • if not existing, it installs it in a temp folder (.carbonifer)
  • versions supported
• Cloud provider credentials (optional):
  • if not provided, if terraform does not need it, it won't fail
  • if terraform needs it (to read disk image info...), it will get credentials the same way terraform gets its credentials
  • terraform Google provider
  • terraform AWS provider
  • terraform Azure provider

Configuration

| Yaml key | CLI flag | Default | Description |---|---|---|---| | unit.time | | h | Time unit: h (hour), m (month), y (year) | unit.power | | w | Power unit: W (watt) or kW | unit.carbon | | g | Carbon emission in g (gram) or kg | out.format | -f <format> --format=<format> | text | text or json | out.file | -o <filename> --output=<filename>| | file to write report to. Default is standard output. | data.path | <arg> | | path of carbonifer data files (coefficents...). Default uses embedded files in binary | avg_cpu_use | | 0.5 | planned average percentage of CPU used | log | | warn | level of logs info, debug, warn, error

Extending Carbonifer

In order to add support for a new terraform resource type, there is a mapping mechanism where we can declare JQ filters to query the Terraform file and extract the necessary information.