FAQ

How does Infracost work?#

Infracost has a CLI and a Cloud Pricing API backend service, as well as many CI/CD integrations. The CLI parses the Terraform plan JSON file to find supported resources and uses cost-related parameters to find any applicable prices for that resource. The Cloud Pricing API returns the prices, which the CLI then uses to calculate the monthly costs. The results can be output in table, HTML or JSON format.

What Terraform versions are supported?#

Infracost works with Terraform v0.12 and above.

To change the path to the terraform binary, set the INFRACOST_TERRAFORM_BINARY environment variable:

INFRACOST_TERRAFORM_BINARY=~/bin/terraform_0.13 infracost breakdown --path /path/to/code

Terragrunt users should see this page.

Does Infracost need cloud credentials?#

That depends on how you run Infracost, since we run Terraform internally, which sometimes needs cloud credentials:

  • When Infracost is run against a Terraform directory, Terraform will need access to cloud credentials, e.g. when running terraform init and terraform plan. These commands are only used to produce plan JSON files and no changes are made to your Terraform state or cloud resources.
  • When Infracost is run against a Terraform plan JSON file, cloud credentials are not needed.

How does Infracost get cloud prices?#

Infracost gets prices from the Cloud Pricing API, which we continually update with the latest cloud vendor prices.

What data is sent to the Cloud Pricing API?#

No cloud credentials or secrets are sent to the Cloud Pricing API. Infracost does not make any changes to your Terraform state or cloud resources.

The Cloud Pricing API needs the relevant data to return a unique cloud price point. We also send the count of Terraform resource types to the Cloud Pricing API to enable us to better prioritize support for new resources. Additional context such as the operating system, Terraform version, type of CI system, and Infracost version are also sent alongside error tracking events so we can identify and fix issues quickly.

Here is an example request to the Cloud Pricing API for a t3.micro instance and the returned response:

Example request:#

query {
products(
filter: {
vendorName: "aws",
service: "AmazonEC2",
productFamily: "Compute Instance",
region: "us-east-1",
attributeFilters: [
{ key: "instanceType", value: "t3.micro" },
{ key: "tenancy", value: "Shared" },
{ key: "capacitystatus", value: "Used" },
{ key: "operatingSystem", value: "Linux" },
{ key: "preInstalledSw", value: "NA" }
]
},
) {
prices(
filter: {
purchaseOption: "on_demand"
}
) { priceHash, USD }
}
}

Example response:#

{
"data": {
"products": [
{
"prices": [
{
"priceHash": "2f1bc092c9e34dc084a4d96d19ef47ca-d2c98780d7b6e36641b521f1f8145c6f",
"USD": "0.0104000000"
}
]
}
]
}
}

Can I run my own Cloud Pricing API?#

Yes! Please email hello@infracost.io for details.

What's the difference between Infracost and Terraform Cloud's cost estimation?#

The key differences are:

  1. Infracost supports over 140 resources. Terraform Cloud supports 43 resources.
  2. Infracost can be used to model usage-based resources and do what-if analysis.
  3. Infracost has a CLI tool that can be used in your terminal or integrated into your workflows regardless of the source control and CI/CD system being used.
  4. Infracost can be used with Terragrunt.
  5. Infracost can output HTML reports or JSON and be used alongside other tools.

Do you offer support?#

Yes! If you need help integrating Infracost in to your workflow, or want to talk about something else, please email hello@infracost.io. You can also join our community Slack channel to chat with us.