Cloudability Tag and label mapping
Why would you map tags and labels?
Along with using Linked Accounts to keep a clear line between a cloud vendor resources, tags help you to allocate who owns which resources and the costs that are associated with them. For more information, see Consolidated Billing for Organizations . Without tags, it is difficult to know who owns a particular resource and what its purpose may be. Cloudability allocates these tagged items. It can also be used to find things that aren't tagged or can not be tagged.
"Three simple tagging rules" link takes you to a third party web site (AWS).
Only actual resource usage can be tagged
There is a lot of spending data included in your monthly cloud vendor bill which isn't classified as direct resource usage (you can use a transaction type filter to find these) and therefore are unable to be tagged. For more information, see Use Transaction Types to split variable vs. recurring charges .
- Monthly recurring Reserved Instances fees. At the beginning of each month, the cloud vendor applies 720 (or 744) hours of pre-pay for each partial or no upfront reserved instance. Because the hours are pre-paid before they are applied to instances, the cloud vendor does not allow tagging of those fees.
- Sign up fee for Reserved Instances . For all upfront and partial upfront reservations, you'll pay a one-off sign up fee.
- Cloud Vendor Support Fees. For regular business support or enterprise support.
- Tax. In Australia, for example, you'll see GST as an item which can not be tagged.
Actual resources that are unable to be tagged
- CloudWatch MetricMonitorUsage
- EBS snapshots - Although these can be tagged, when the cloud vendor reports on them, spending is collapsed to account/region with no resource ID or tags made available.
Things that can be tagged
- EC2, RDS, and Redshift instances
- S3 buckets, including storage, and request costs
- DataTransfer will inherit the tags of its resource source (for example, the tags from S3 bucket, EBS volume...)
- Additional EBS volumes (note EBS volumes provisioned with an EC2 instance will now inherit tags from the EC2 instance)
- RDS storage
- Direct Connects (using the CLI) (see Tagging AWS Direct Connect Resources)
Tags & Labels FAQ
Can I map multiple tag keys to a single tag dimension in Cloudability utilizing a tool like regex or wildcards?
At present, Cloudability does not allow you to map multiple tag keys to a single dimension using regex or wildcards.
How does Cloudability handle multiple tag keys?
At present, Cloudability does not allow you to map multiple tag keys to a single dimension using regex or wildcards. If the same resource has multiple tag keys then Cloudability will pick up the first tag key which is added to the tag dimension and ignore other keys.
How can I extract a value from a tag?
-
Using Tag Explorer: Navigate to Insights > Tag Explorer, under Taggable Spend tab, apply filter for ' Tags & Labels' Dimension. In the chart, you can mouse hover to different Tag and view the tag values.
-
Using Reports: You can generate a report by including a specific Tag(Value) dimension in the report. The result will display all the different Tag(values) for different Tag(Keys).
Q: What is the limit on tags that can be mapped in tags and labels?
A: In Cloudability, the current limit for 'Tags & Labels' is 30. In future, Cloudability will likely increase this limit.
Q: Can we add more than 30 tag and label mappings?
A: Cloudability has increased the number of available 'Tags & Label' mappings in Cloudability by 20. This means customers can now have up to 50 reporting dimensions in the platform that are specific to mapped tags and labels. This will particularly help customers who are multi-cloud and have many tag or label keys in their environment. Cloudability administrators can add these additional mappings in the 'Tag & Labels' Mapping feature.