How to Build a Perspective Using Tags for Categorization

Products

• CloudHealth

Issue/Introduction

When building a Perspective in CloudHealth using tag-based categorization, relying on a single asset type may leave out untaggable or newly released AWS resources. Using both "AWS Taggable + Associated Assets" and "AWS Taggable Assets Only" ensures complete infrastructure coverage across your reports.

Resolution

Step 1: Verify Tag Management

Ensure the target tag is enabled in CloudHealth:

1. Navigate to Setup > Tags > Tag Management.

2. Confirm the tag key (e.g., Product) is toggled to Enabled.

Step 2: Choose Categorize

1. In the Perspective Builder, select Categorize to dynamically generate groups based on your tag values.

Step 3: Group Search using "AWS Taggable + Associated Assets"

1. Run the group search using the asset type AWS Taggable + Associated Assets.

2. Review the discovered groups and pull them into your Perspective.

Why this matters: CloudHealth maintains an asset-dependency tree that pulls in both directly tagged assets (like EC2 instances) and their non-taggable dependent resources (like attached EBS volumes).

Step 4: Group Search using "AWS Taggable Assets Only" (Best Practice)

1. Within the same Perspective, run the group search a second time using AWS Taggable Assets Only.

2. If new groups appear, add or merge them into the appropriate existing Perspective groups.

Why this matters: Because CloudHealth's asset-dependency tree is periodically updated, newly released AWS service types might not yet be mapped under "Associated Assets." Running this direct AWS feed search ensures no taggable assets are missed.