Alistair Scott ری ٹویٹ کیا
It is time for Proactive FinOps. Let’s talk about how we can be proactive with tagging cloud resources across many cloud providers. 💜
One of the first tasks assigned to the FinOps teams is to determine "who is using what" - that is, which teams, business units, products, etc. are spending the most on cloud. To accomplish this, they use tags. Tags are simply key-value pairs added to resources. Without tags, it all falls apart.
However, FinOps teams face challenges because all tools available are reactive. These tools begin by analyzing cloud bills and providing visibility of tags from there. This means that they are looking at resources that are already running in production and costing money.
“AHA!” - A customer recently shared, “I want all resources to be properly tagged. But if they are not, I would rather a resource not be tagged at all than be tagged incorrectly.” and that was our “aha” moment. We need to shift tags left into the CI/CD too!
So here it is, it’s live: you can now define your tagging policy in Infracost Cloud, by stating what are the required tag, and what the values they should have. These will be automatically checked in the engineering workflow, and if you have selected to, Infracost will tell the engineer if their code doesn’t contain the right tags and blocks the Pull Request from going to production.
Two big benefits:
1. No more untagged or mis-tagged resources in your cloud bills;
2. Save engineering time: they no longer need to go back and forth making multiple pull requests to fix tags.
On top of this, you will see a chart of conformity over time. See the pictures. You can get started right now by adding Infracost to your GitHub / GitLab environment, or if you’d like a live demo just DM me.
Read more: infracost.io/blog/finops-ta…
English
