Skip to main content

Resource Groups in Virtana Platform

Resource groups provide you the ability to combine and filter resources in your cloud environment, across cloud platforms. Using resource groups, you can more precisely identify the sources of increases or decreases in cloud spend and align cost data to your larger business context.

Virtana Platform provides pre-created but unconfigured resource groups for Applications, Business Units, and Environments. You can define these resource groups by selecting which CSP accounts to include, as well as which tagged resources you want included in the group. You can include account resources from multiple cloud service providers (CSPs), so you can analyze data across cloud environments.


AWS and Azure use the term tag, while GCP uses the term label. Virtana uses "tag" as a general term to refer to functionality that you can apply to resources to segment your CSP account.

Tags or labels used in your CSP environment are discovered and pulled Into Virtana Platform. If you want to modify the tag list, you must do so in your CSP.

When you edit a resource group in Virtana Platform, you first select the scope. The scope reflects the specific accounts in any of your CSP environments that you want to be part of the group. You then choose from the tags that are available for the accounts you selected. Tags limit the group to only those resources that are assigned the tags you select. Tags allow you to more precisely organize your data by various categories.

The scope for resource groups is based on accounts associated with billing data, not on the data sources configured in the cloud integrations. Accounts for each cloud provider are based on the following:

  • AWS: Master Payer Account and Linked Accounts. Linked Accounts include all linked accounts from the billing data, not just linked accounts configured in the cloud integration in Virtana. 

  • GCP: Master Payer Account and Projects. Projects are discovered from the billing data.

drawing showing the relationships of accounts with tags and attributes


Let's assume you want to assign some subset of your GCP and AWS resources to resource groups. You want one resource group that includes resources associated with applications in your GCP and AWS environments.

In your GCP and AWS accounts, tag names are used inconsistently. Applications might be tagged "App", "app", or "APP". The tag for business units might be "Business Unit", "BU", or "bu".

On the Create Resource Group page, you select the initial resources from your AWS and GCP accounts that you want included in the resource group. In this example, you select GCP Project A-1, Project A-2, and Project A-3. This is the initial scope of the group.


You then select the tags you want. Only tags assigned to resources in the accounts you selected will display in the list. You want to more precisely limit the resources in this resource group to any entity tagged as an application. So you select the primary label "App".


However, you know that some applications have been mislabeled using an "APP" tag. You want to be sure to capture those resources as well. So you click Add Rule and select the same accounts you selected for the previous scope. Then select the tag "APP". If data is not labeled "App", but is labeled "APP", it will still be included in the resource group.

Next, you add the AWS resources. You would select Add Rule and follow the same procedure as you did for GCP.


When you are finished selecting your GCP and AWS resources and tags, you can access the Results Preview tab to see a list of entities to be included in the resource group.


Related Topics

Resource Groups Page

Edit an Unconfigured Resource Group