- Cost allocation views
- Cost allocation using virtual tags
- Cost allocation categories
- Cost allocation business mapping (New !)
All options will help you to build a query on related resources so you could easily filter and group by them in the Cost & Usage Explorer to be able to dive into the actual costs.
Cost Allocation views
When you need to combine several values of keys together to be able to use them as a group for cost allocation this is the option you should chose.
For example for the Environment Tag you have several values representing the same env. i.e "Prod1, prod2, Prod3).
From the Views menu (accessed by clicking Cost Allocation > Views) you can merge several tag values for one tag key, as shown below.
Cost allocation by virtual tags
When you want to combine several tags together such as "Prod" , "prd" and "prod" and group them together to be able to dive into their costs this is the option you should chose.
Cost allocation categories
When you need to group several filters together to be able to use them as one group for cost allocation this is the option you should chose.
From the Categories menu (accessed by clicking Cost Allocation > Categories), you can merge several filters together to use them in the Cost & Usage Explorer.
Note that if there is overlapping data, the overlapping data will show in each of the categories, resulting in total costs of more than 100%. In addition, using this option will not show what is not allocated.
Cost allocation business mapping
Visualize all your cloud costs, accurately! Users love Anodot’s Cost Allocation > Categories for grouping costs, but two categories can share the same costs, which means you can’t use categories to easily visualize total spend, total unallocated costs, or split costs.
That’s where business mapping comes in! Under the Cost Allocation > Business Mapping menu, you can now quickly and easily use our rules engine to target and map costs to any business object or cost center you’d like. Each successive business mapping will only contain costs that have yet to be allocated, even if they would otherwise be captured in that next mapping’s rule.
This enables you to create visualizations in the Cost & Usage Explorer that display total combined costs without overlap and to determine which costs are yet to be allocated.
You can also create business mappings to split shared costs amongst other business object mappings. For example you can divide one AWS Business Support billing line item amongst multiple teams.
Anodot provides three options for dividing shared costs:
- Equal – The targeted costs are split evenly, i.e., 50-50
- Custom – The targeted costs are split by custom percentages, i.e., 25%-25%-50%
- Ratio – The targeted costs are divided proportionally based on the relative percentage of direct costs already attributed to each selected mapping, i.e., if Map1 contains $10 of costs, and Map2 contains $5 of costs, the new map will be split between Map1 and Map2 using a ratio of 2:1
For more information on business mapping, see here.
