Skip to content
Switch branches/tags


Failed to load latest commit information.
Latest commit message
Commit time

Terraform AWS pricing module

Terraform module, which calculates the AWS infrastructure cost in a variety of ways. This is not a traditional Terraform module because it does not create AWS infrastructure resources but using Terraform plan and Terraform states as input. is entirely free cost estimation service, which is part of that is currently in active development.

Join the mailing list on to stay updated!

If you are looking into alternative ways calculating AWS infrastructure costs (for free), you can use or terraform-cost-estimation.

This is not an official HashiCorp product.


  • Calculate costs before creation:
    • tfplan
  • Calculate costs after creation:
    • tfstate
  • Calculate costs from multiple sources (local, remote states, specified resources)
  • Optionally, using
  • Can be executed on restricted CI/CD platforms where Terraform can run

Supported resources

  1. EC2 instances (on-demand) and Autoscaling Groups (Launch Configurations and Launch Templates):
  • aws_instance
  • aws_autoscaling_group
  • aws_launch_configuration
  • aws_launch_template
  1. EC2 Fleets (on-demand)
  • aws_ec2_fleet
  1. EBS Volumes, Snapshots, Snapshot Copies
  • aws_ebs_volume
  • aws_ebs_snapshot
  • aws_ebs_snapshot_copy
  1. Elastic Load Balancing (ELB, ALB, NLB)
  • aws_elb
  • aws_alb / aws_lb
  1. NAT Gateways
  • aws_nat_gateway
  1. Redshift Clusters
  • aws_redshift_cluster


Using AWS Pricing API: Terraform state or plan as JSON

provider "aws" {
  region = "us-east-1"

module "pricing" {
  source = "terraform-aws-modules/pricing/aws//modules/pricing"
  # content can be Terraform state or plan as JSON fetched from any source (see examples)
  content = jsondecode("{\"version\": 4, \"terraform_version\": \"0.14.4\", ...")

Using AWS Pricing API: Terraform plan as JSON from local file

provider "aws" {
  region = "us-east-1"

data "local_file" "local_plan" {
  filename = "local_plan.json"

module "pricing" {
  source = "terraform-aws-modules/pricing/aws//modules/pricing"
  content = jsondecode(data.local_file.local_plan.content)

Using AWS Pricing API: Specified resources

provider "aws" {
  region = "us-east-1"

module "pricing" {
  source = "terraform-aws-modules/pricing/aws//modules/pricing"
  resources = {
    "aws_instance.this#5" = { # Note: This means 5 instances (`count = 5`)
      instanceType = "c5.xlarge"
      location     = "eu-west-2"
    "aws_instance.this2" = {
      instanceType = "c4.xlarge"
      location     = "eu-central-1"

Run in automation

@todo: Describe in more details...

# Project1 (with real EC2 resources):
terraform plan -out=plan.tfplan > /dev/null && terraform show -json plan.tfplan > plan.json

# Project2 (terraform-aws-pricing module):
TF_VAR_file_path=plan.json terraform apply
HOURLY_PRICE=$(terraform output -raw total_price_per_hour)

if HOURLY_PRICE < 10 then
  terraform apply plan.json # (from Project1)
  echo "Crash! Boom! Bang!"


AWS provider

Set AWS provider's region to us-east-1 or sa-east-1 when using modules/pricing because AWS Pricing service is only available in these regions.

You can also pass provider explicitly as described in the official documentation.

Debug & development tips

  1. debug_output = true will return more output which is often helpful only for development and debug purposes.

  2. call_aws_pricing_api = false will not call AWS Pricing API. Wrong filters produce a lot of noise, so it makes sense to disable this option when developing new filters.

  3. AWS Pricing API should always return one response for the filter. Running these commands can help identify available filters to put into modules/pricing/ (see dev directory also):

    aws pricing describe-services --service-code AmazonEC2 --format-version aws_v1 --max-items 1 --region us-east-1

    aws pricing get-products --region us-east-1 --filters file://filters.json --format-version aws_v1 --service-code AmazonEC2

Ephemeral Terraform backend

Sometimes, you may want to not store Terraform state in backend when dealing with pricing, you can use backend "inmem":

terraform {
  backend "inmem" {}

When you use this type of backend, there is no way to run terraform output.

Known issues/limitations

  1. Autoscaling groups resources
  2. When changing values price is sometimes higher after the first run because it is calculated based on keys and there can be some previous keys. Solution is to update code to include some unique key/prefix. Or just disable terraform state (no state = no past).
  3. At some point later, maybe add support for other providers like Azure and Google Cloud



Module created and managed by Anton Babenko.

Please reach out to Betajob if you are looking for commercial support for your Terraform, AWS, or serverless project.


Apache 2 Licensed. See LICENSE for full details.