Good News – Now Easily Track Cost Of Untaggable AWS Resources
Tags are the most useful things when it comes to tracking and managing your AWS cloud cost. Using tags you can define logical groupings of your AWS cloud resources. You can define groups based on cost-centers, departments, applications and environments. AWS cost allocation is centered around properly tagging all your resources.
But you cannot tag all the AWS resources you use! How would you track cost of those untaggable resources? How would you track costs like one time subscriptions and recurring partial upfront reservation costs? How would you track cost by component or by project when proper tagging conventions are not followed by your team? Botmetric’s new AWS Cost Allocation is here to help you track and allocate your AWS spend more efficiently.
Before we even kick into internal feature details of Botmetric’s AWS Cost Allocation, this feature assumes you have enabled tags in your AWS account. If tags are not enabled for reports in your account, you can enable them from here. While the application on Cloud scales to a level where application is distributed across multiple micro services and departments, having the cost tracking per component or by micro service will become a tedious process. In such cases, AWS tags naming feature comes to rescue in service like “Amazon EC2”. See the full list of services support tagging here.
Fundamentally, there are the following two main reasons why organizations and businesses struggle to track their cost on AWS:
- Resource owners have not added proper tags or are not following defined conventions
- Resource itself is not taggable
Botmetric’s Cost Allocation can help you in allocating costs to specific cost-centers/business-units and fill the gaps left by AWS. It helps you become more efficient in tracking your AWS costs. Let’s take a step-wise look at how you can get started with Botmetric’s AWS Cost Allocation.
Using Botmetric AWS Cost Allocation
Start off with analyzing your AWS resource usage cost.
- Go to Botmetric Cost Allocation dashboard
- Select the required AWS account
- Select a specific Tag Key (eg: Cost-Center, Department, Component, etc)
- Select a specific month from the list
- Click on Analyze.
Your AWS account’s billing data will be analyzed and results will be loaded into two sections as, UnallocatedCost and Allocated Cost.
Sum of cost of all the line items where the selected tag value is empty.
Sum of cost of all the line items where the selected tag value is not empty.
From here, cost can be distributed in two ways.
- Select each line item and allocate them to a specific Tag Value (eg: Finance, Operations, etc).
- Distribute unallocated cost proportionally.
Distribute unallocated cost proportionally
You would want to use this part of Botmetric AWS Cost Allocation in order to allocate cost proportionally for costs like ‘AWS Business Support’ and ‘EC2 Data Transfer’ costs. These kind of spends cannot be broken down to the finer levels of details and hence are better to be proportionally distributed.
Let us say, for Tag Key ‘component’, the already properly allocated cost is $400, unallocated cost is $100 and total cost is $500. Component1 has allocated cost of $300, Component2 has allocated cost $100. This feature will distribute the unallocated cost of $100 proportionally to $60 and $40 to Component1 and Component2 respectively.
Click on Allocated Cost section.
Click on Distribute unallocated cost proportionally checkbox to distribute the cost across the tag values, based on the existing ‘allocated cost’ of each tag value, the ‘unallocated cost’ will be distributed proportionally.
Click on Generate Report button to download the report.
Select each line item and allocate them to specific Tag value
Click on Unallocated Cost section.
The cost data will be rendered by service with two options at each row.
- Resource With Id : Grouping of all the line items where resource id is present. Ex: i-a12bcedf
- Resource Without Id : Grouping of all the line items by record id. Ex: 1234567890
Browse and allocate.
Decide on which one of the two types of resources you would want to start allocating first. If your team has the required tagging discipline then you would mostly need to go for allocating resources without Id. This would include spends like partial upfront reservation recurring charges. But let’s go over both the possibilities.
- a) Resource with Id:
- Click on Resource with Id link.
- Select the tag value, row in the table them Click on Allocate.
Note: You can now allocate at most 5 rows in a single click.
- b) Resource without Id:
- Click on Resource Without Id link.
- Select the tag value, row in the table and click on Allocate.
Generate report after allocation.
After you are done allocating AWS resource spends from the unallocated section. All those resource spends would now have moved to the allocated section. So, now you can go follow the below steps to generate the final report.
- Click on Allocated Cost section.
- If required tick the checkbox to Distribute unallocated cost proportionally
- Click on Generate Report button to download the report.
So, there you go. You now have a potent addition to the array of features Botmetric’s AWS Cost Analyticshas. Give it a try and share your feedbacks and suggestions. We always love to hear from you. You can always raise a feature request or let us know if something in Botmetric can be improved.
Visit our product updates section to keep a tab on Botmetric product updates regularly.
Currently, you can use this Cost Allocation feature to allocate cost of last two months. The ability to allocate current month cost is also coming very soon.
If you haven’t yet tried Botmetric, get started with a 14-day free trial today and explore cost saving opportunities and track and allocate your AWS Cloud spend better!
Latest posts by Rajeev Kumar (see all)
- Simplify the Cost Incurred By your Enterprise with AWS Cost Savings - July 18, 2017
- A Start-up’s Resolution to Cloud Sprawl Using SaaS-based Cloud Management Platform - July 13, 2017
- 10 Design Principles for AWS Cloud Architecture - June 27, 2017