You already have a tagging strategy in place and you’ve mastered exploring your costs by services, attributes, and tags. So what’s next?
Another great way to discover savings opportunities (or simply gain more context for your bill) is to examine what hasn’t been given a particular value for a tag. The easiest way to find resources that are missing tags is to use the Bill Analysis tool.
This guide assumes you have already created User-Defined Cost Allocation Tags from your AWS Console. If you have not, follow the steps below to do so for your AWS resources.
There are two kinds of Cost Allocation tags:
This creates a
resource created by tag automatically on all resources.
User-Defined cost allocation tags, once created, appear in Billing > Cost Allocation Tags. You must use the AWS Tag Editor to create these tags.
Key-Valuetags and assign them to your resources.
Now you are ready to use Cost Allocation Tags to analyze your bill in Metricly.
tag valuefrom Options > Group By. In this example, we are grouping by the
service, to gain more insight into your untagged resource spend.
Regionto get an idea of where your missing resources are located
Usage Typefor a specific, granular list of costs such as EBS volume usage.
Use this information to triangulate resources you are paying for that may have gone unlabeled. Keeping untagged resources to a minimum is a great way to prevent cost creep!
You can search for resources where no value for a given tag has been specified. This can be particularly useful for tags that clearly divide your resources by applications, departments, and projects.
* Not Specified *. This selects all costs that have no value for the