Linked Accounts Appear in Multiple Perspective Groups in CloudHealth

Products

• CloudHealth

Issue/Introduction

It is possible for a single AWS linked account to appear under multiple groups within a CloudHealth Perspective. This behavior typically occurs due to the way asset keys or resource identifiers are used and tracked across accounts.

Cause

When a resource’s key or tag is created in one account but later referenced or utilized in another, reporting features may attribute that resource to multiple groups. For example, if a resource originated in one AWS account but is now associated with a different linked account, and the Perspective grouping relies on resource tags or keys, the resource can appear in the group corresponding to its original account. This often results in entries that show $0 cost in the group where the resource no longer resides, as CloudHealth is using the LinkedAccountId column to filter accounts for reporting.

If you notice a linked account or resource showing in several groups (possibly with a $0 cost in some), review the statement detail drilldown. Examine whether the ResourceID or key originated from an account that differs from the current linked account. If grouping is dependent on keys that have traveled between accounts, multiple group assignments can occur.

Resolution

Maintain Asset Origin: Keep assets in their original AWS account to prevent overlapping group assignments within a Perspective.

Rebuild Perspective with Unique Filters: Consider rebuilding the Perspective using a filter category or attribute that is unique to the target account (such as a consistently applied and unique tag), rather than attributes or keys that could span multiple accounts.

Applying these workarounds should help ensure that each linked account and asset appears in only the intended group within your CloudHealth Perspectives, improving reporting clarity and cost allocation accuracy.