5 ms·

How does this compare to the FOSS aws cost estimator for TF that's already available? https://github.com/antonbabenko/terraform-cost-estimation https://github.

• aliscott 6y ago
  We cover 70+ resources across AWS and GCP (the tool you mentioned only covers 12 AWS resources) and we support a number of integrations including GitHub Actions and Atlantis (https://www.infracost.io/docs/integrations/ https://www.infracost.io/docs/integrations/) so you can see diffs in pull requests. We're seeing a lot of users who are using multiple tools for deploying their services, for example Terraform + Kubernetes or CloudFormation + Serverless. In the future we want to work across multiple tools so we can support these use-cases as well.
• mikegreen 6y ago
  I'm hoping that Infracost doesn't need the entire state file shipped to an outside service/server, like the one mentioned here does. State files should be considered secret.... $ terraform state pull | curl -s -X POST -H "Content-Type: application/json" -d @- https://cost.modules.tf/
  • aliscott 6y ago
    Agree, state files can contain sensitive information. We parse the Terraform client side and only send the details to the API that are needed to determine the price, i.e. the instance type, region, etc.
  • dastx 6y ago
    They have a jq script[0] that removes everything but the necessary data for the cost estimation. [0] https://github.com/antonbabenko/terraform-cost-estimation/blob/master/terraform.jq https://github.com/antonbabenko/terraform-cost-estimation/bl...