Some AWS Assets are not categorized in my Region based Perspective groups.

Products

• CloudHealth

Issue/Introduction

When creating Perspectives in CloudHealth and using "Region" as the "Asset Type" to "Categorize," many assets are falling into the default "Assets Not Allocated" group instead of the Region that they are provisioned in.  

Cause

"Region" categorization (in its current implementation) supports a subset of AWS Assets.  Not all AWS assets can be categorized by Region.  This is expected behavior.  

Here is a list of the supported AWS asset types that can be categorized in a Region.  All others are excluded and will fall under "Assets not Allocated" instead.  Cost will not be missing.  It will instead be included in the Assets not Allocated total. 

AwsWorkspaceBundle
AwsInstanceType
AwsEc2ApplicationLoadBalancer
AwsLoadBalancer
AwsDynamoDbTable
AwsS3Bucket
AwsSecurityGroup
AwsRdsSubnetGroup
AwsRdsSecurityGroup
AwsRdsInstanceReservation
AwsRdsInstance
AwsImage
AwsSnapshot
AwsRedshiftSnapshot
AwsRedshiftCluster
AwsAvailabilityZone

Resolution

This is expected behavior.  It is recommended that the Region filter, which is available in reports, be used to more completely view the cost on an AWS Region basis.  If fuller grouping in a Perspective is desired, then other criteria such as Asset tagging can be used.