With cost monitoring enabled in env0 you will be able to see how much each Environment and Project you are running costs.
To be able to see a project's costs you need to have the "Edit Project Settings" permission.
We utilize Terratag to automatically tag all of your cloud resources and determine exactly how much they cost over time.
In order to setup cost monitoring you will need to provide credentials that enable env0 to query your cloud provider's billing API. Below are guides for how to set up credentials in each cloud provider:
- Go to the Project Settings of the desired project.
- Select the Credentials tab.
- Check the appropriate cloud provider checkbox, and select the credential you created in the steps linked above.
- Click Save.
- env0 tags resources in your Terraform, in order to query your cloud provider for the actual costs. You can see which tags are applied in the Terraform plan. Some resources might not be tagged, in which case the cost reported on env0 will be lower than expected.
- env0 will call your cloud provider's API in order to query the cost. This might incur additional charges from your cloud provider.
Cost estimation is a tool that can be used to help reviewers of deployment plans. Once activated for a project, every deployment plan would trigger a cost estimation calculation. This way, you can view a plan and its cost estimation, and decide whether or not to deploy this plan.
We are using the open source infracost tool to make the cost estimation.
In order to activate cost estimation for your project, go to "Project Settings", and then to the "Policies" tab. Check the "Cost estimation" checkbox, and save.
Cost estimation is supported in self-hosted agents from version 0.2.82. In order to activate cost estimation in a self-hosted agent, you'll need to create your own secret API KEY for infracost.
You'll need to:
- Create an API key for infracost - see infracost documentation.
- Save that API key in your AWS Secrets Manager.
- Create an
INFRACOST_API_KEYsecret environment variable in env0, referencing the API key stored in Secrets Manager.
Updated 3 months ago