Infracost diff – “git diff” but for cloud costs

Infracost diff – “git diff” but for cloud costs

Recently we released a new infracost diff command inspired by git diff. This shows a diff of monthly cloud cost estimates between the current and planned state of Terraform projects. At a high-level this might seems like a simple exercise of subtracting the current state’s cost estimate from the planned state, but cloud costs are rarely that simple to deal…

Cloud Costs Are Shifting Left

Cloud Costs Are Shifting Left

“Shift left” has become a popular buzzword for both Software Engineering and DevOps. It means introducing processes earlier in the software development cycle. The “shift left” principle started with testing. In a traditional waterfall model testing is performed just before release. Shift left testing started it earlier by introducing practices such as Test-Driven Development (TDD)…

Cloud cost alerts are too late: trigger notifications before launching

Cloud cost alerts are too late: trigger notifications before launching

Most cloud providers enable users to set budget alerts on their actual cloud spend. This is a critical safety net as usage-based resources could incur a lot of cost (e.g. data transfer). There is also another safety net that companies should set up, and that is catching significant cost changes to their infrastructure before going…

Terraform cloud costs directly from pull request to management

Terraform cloud costs directly from pull request to management

Last week I wrote about giving cloud cost estimates to DevOps teams via pull requests as they make changes to infrastructure components. The hope is to create a “Prius Effect” for cloud costs: it was observed that many Prius drivers would drive more efficiently simply because they were presented with immediate feedback on the Prius dashboard. In…