Skip to main content

Filtering AWS Integrations by Tags

When setting up an AWS integration instance, you have the option of adding AWS tags that can limit the AWS entities identified in Virtana Platform. This could be useful if you have entities you do not want included in reports. For example, you might have more compute instances than what you are licensed for in Cloud Cost Management (CCM), so you do not want all compute instances included in CCM reports.

The integration filters are created using AWS tags, which consist of key/value pairs. The tags are created in AWS and help you to identify and organize your resources in AWS. For more information about creating AWS tags, see the AWS Tagging Best Practices and the AWS documentation.

Filter tags can be applied to entities in the following AWS instance types:

  • EC2

  • RDS

  • S3

The supported filter types include the following:

  • Inclusion Filters

    Inclusion filters limit the scope to a set of entities that match a given criteria, based on a tag key or tag value.

    This filter is best used when you have a few, specific items you want selected.

  • Exclusion Filters

    Exclusion filters limit the scope to everything except the selected items that match a given criteria. For example, excluding the tag VPN would return a list of all elements that do not include the VPN tag.

    This filter is best used when you want the majority of given entities available, except for those with certain attributes or tags.

In this section: