Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Add preventive costs desc #536

Merged
merged 1 commit into from
Aug 15, 2023
Merged

docs: Add preventive costs desc #536

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/infracost_cloud/actual_costs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Infracost Cloud enables you to see actual costs using your AWS account's Cost an
This page outlines how you can give Infracost Cloud read access to your AWS CUR data (and resources listings), which Infracost requires to provide this functionality. We plan to build similar functionality for Azure and Google in the future.

:::info
This feature is in private beta, email [[email protected]](mailto:[email protected]) if you'd like access.
This feature is in private beta. Before following this document, email [[email protected]](mailto:[email protected]) to request access.
:::

## Connect Infracost Cloud to existing AWS CUR S3 bucket
Expand Down
8 changes: 7 additions & 1 deletion docs/infracost_cloud/guardrails.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,13 @@ Guardrails help you control costs by monitoring pull requests (PRs) and triggeri

<img src={useBaseUrl("img/infracost-cloud/guardrails/cost-saving.png")} alt="Cost savings from guardrails" />

Guardrails also have an audit trail of the pull requests that triggered them:
## Preventive costs

We figure out how much you've saved on guardrails by looking at the difference between the costliest run that activated the guardrail and the final cost when you made your latest change. So, let's say an engineer opens a pull request with a change that would've increased the cost by $10k, but the guardrail is triggered. Your team then works to reduce the cost, and the changes finally get approved and merged with an increased cost of $2k. In this case, you've saved $8k because of the guardrail.

But, there's an exception when you decide not to make a change after it activates the guardrail. Suppose you propose a change that would cost an extra $7k, but the guardrail is triggered. If you then decide it's too expensive and discard the changes by closing the pull request, we count that as a saving of $7k, because you avoided that extra cost.

Guardrails also have an audit trail of the pull requests that triggered them so you can see details of the preventive costs:

<img src={useBaseUrl("img/infracost-cloud/guardrails/guardrail-events.png")} alt="Guardrail events" />

Expand Down