Tag Resources

Cloudaware Tag Analyzer allows to review the tagging coverage across all clouds and tag resources directly from Cloudaware account.

Requirements

AWS

To tag AWS resources from Cloudaware, download Cloudaware Tagging policy: Admin → AWS Accounts → ADD AMAZON ACCOUNT → Using Access & Secret Keys → select Tagging in 'Please use one of those'. Review and apply the policy.

Azure

To tag Azure resources from Cloudaware, create a custom role in your Azure portal using CLI or Rest API*. The role should include a 'modify' permission granted for all resource types (e.g. Azure Virtual Machine) you would like to be able to tag in Cloudaware. Assign the role to Cloudaware.

*To be able to create custom roles in Azure portal UI, your organization needs Azure AD Premium P1 or P2.

GCP

To tag GCP resources from Cloudaware, ensure that the permissions for labels are in place on a custom role created for and assigned to Cloudaware.

Billing Tags: Google Cloud Platform does not provide the cost data split by instance out of the box. In order for Cloudaware to display the cost on an instance level, every GCE instance in your environment needs to have a tag (e.g. instance-name: actual-name-of-this-instance) applied.

Tag Analyzer

1. Log in to your Cloudaware account → Tag Analyzer

2. Select a cloud provider. Pick the object type from the list (e.g. AWS EC2 Instances).

3. Review the column 'Not Tagged Objects'. Click the number of objects to drill down into Objects Explorer.

4. Select AWS EC2 instances a tag to be applied to, and proceed by clicking TAG AWS EC2 INSTANCES.

5. Review the existing tags. Click + ADD TAG to apply a new tag.

New tags and their values will appear in your AWS Console.

Bulk tagging: Cloudaware supports adding up to 44 tags on AWS, 49 tags on Azure, and 64 tags on Google resources.

CaTags Creation

СaTags are Cloudaware-specific fields used for parsing row tag data that is received from cloud providers. CaTags for AWS, Azure, Google and vCenter related objects can be created in Cloudaware Tag Analyzer.

Cloudaware has a concept of Fuzzy and Exact caTags that serve to define fields with tags written in different ways. For example, if tags 'env', 'environment' and 'Environment' are applied and considered to mean the same based on your organization tagging policy, create a fuzzy caTag to unite their values under one tag 'Environment'. However, If tags 'environment' and 'Environment' must be treated as separate entities, create Exact caTag:

If you would like to create caTags on objects that are not currently supported in Tag Analyzer or custom objects, follow these steps:

1. Log into your Cloudaware account. Select Setup in the main menu under your username.

2. Type Objects in the Quick search bar on the left → select the custom object in question.

3. Under the section 'Custom Fields & Relationships' click New.

4. Select successively:

Data Type: Text
Field Label: tag name (format: companyname_tagname)
Length: 255
'Field Name' is populated automatically. Remove the API Name input by default (1) and replace it by the one in the format caTag_tagname (see the example below)

1
2

5. Click Next → select 'Visible to all' → Next → Save.

Navigation For Tagging

Access Tag Analyzer using:

list views (e.g. Running Instances for AWS EC2 Instance) selecting the instance under question
the tab 'DETAILS' on a resource (see MORE → TAG AWS EC2 INSTANCES)

the tab 'TAGS' on a resource → + ADD TAG

Tags With Blank Values

In cases when tags with bank values are applied in AWS Console, Cloudaware Tag Analyzer may detect them as Tagged Objects showing empty values. Create two list views to observe the difference.

Cloudaware Navigator → AWS EC2 Instances → Custom Views (on the left) → + (Create New View) → Query Mode → copy the queries below → Save View

Query sample for No Tag

Replace TAGNAME with your Tag Name:

CODE

`Deleted From AWS` equals null and `Tags JSON`[$["TAGNAME"]] equals null -> 
`Instance Name or ID`, `Account`.`Account Name` as "Account", `Application Tier`.`Application`.`Name` as "Application", `Tags JSON`[$["TAGNAME"]] as "Tag: 'TAGNAME'", `Tags`

Query sample for Tag <Name> is empty

Replace TAGNAME with your Tag Name:

CODE

`Deleted From AWS` equals null and `Tags JSON`[$["TAGNAME"]] equals '' -> 
`Instance Name or ID`, `Account`.`Account Name` as "Account", `Application Tier`.`Application`.`Name` as "Application", `Tags JSON`[$["TAGNAME"]] as "Tag: 'TAGNAME'", `Tags JSON`