Drive an increased ownership of cloud usage across your organization
When it comes to establishing a FinOps practice, allocating costs represents a key building block as it sets you up for success with other important tasks.
For example, once youโve divided your cloud bill up among the different parts of your organization that use it, it becomes easier to manage shared costs, budget, forecast, and more.
In fact, โCost Allocationโ ranked #1 as the most important FinOps capability companies prioritize, according to the FinOps Foundationโs โThe State of FinOps 2023โ survey.
Thatโs why weโre excited to introduce Attribution Groups to the DoiT Product Portfolio, which helps you allocate costs at any granularity. Read on to see how Attribution Groups work and ways that you can use them to better understand your cloud bill.
Mapping cloud costs to teams, apps, and more with Attributions
Before you build Attribution Groups, you must create Attributions in the DoiT Console first. An โAttributionโ is a logical grouping of cloud resources that defines a cost category unique to your company.
For instance, we have six product engineering teams at DoiT, each with a unique name such as โTeam Turingโ. We use Attributions to help us understand each teamโs resource costs. As shown below, we group together all resources with a โteamโ label, or project label, value corresponding to the teamโs name.
Another common use case customers use Attributions for is to define various environment costs. Here we are grouping all Google Cloud projects containing the word โstagingโ to define our Staging Environment costs:
Finally, while the use cases are endless, another application customers use Attributions for is to define costs of different products. Below we group costs of resources tagged with a โproductโ tag value corresponding to the product (Application C) that also appears in a list of AWS accounts.
Allocating your cloud costs with Attribution Groups
Once youโve created Attributions for the cost categories youโd like to allocate cloud cost to, youโre ready to create Attribution Groups!
Letโs return to our example with product engineering teams. Once weโve created an Attribution for each team, we bring them all together under an Attribution Group named โEngineering Teamsโ. Once set up, you can track your teamโs costs alongside any unallocated costs โ resource costs not associated with any of the Attributions in your group โ and decide how you want to split that up.
If there are any overlapping resources between Attributions, by default its costs will be assigned to the Attribution ranking higher on the list. Using the above image as an example, if โBruteforceโ and โNimbusโ shared a GCP project, then Bruteforce would be assigned the projectโs costs by default.
Attribution Groups can then be used in the DoiT Console to build Reports, such as the one below that breaks down each teamโs costs (and unallocated costs) by the top ten services.
You can even break down the costs of Attribution Groups by other Attribution Groups! For instance, below weโve broken down each teamโs spend by environment.
Adopting FinOps requires a cultural shift
Establishing a FinOps practice requires a cultural shift in the way your organization takes ownership of their cloud consumption.
Outside of a handful of โFinOps cultural flag bearersโ, thereโll always be a significant group of stakeholders who arenโt used to being aware of or being held accountable to their share of cloud costs.
Using Attribution Groups, you can drive cost awareness and accountability among these stakeholders, and gain a clearer picture of everyoneโs contribution to your cloud bill.
If youโre a DoiT customer, log in to the DoiT Console to start building your Attributions and Attribution Groups.
Not a DoiT customer? Talk to us about gaining access to the entire DoiT Product Portfolio and on-demand access to over 150 Senior Cloud Architects.
