Introduction

The Public Cloud Integration extracts information about the Cloud Spend from AWS, Azure and Google Cloud. Based on Tags (AWS, Azure) resp. Labels (GCP) assigned in the Cloud environment, this cloud spend information can not only be aggregated onto the level of your Cloud Accounts but also associated with Software Artifacts.

📘

Nomenclature

For easier readability, we will use the term "Tag", understanding that the term "Label" is used in GCP.

Cloud Provider Specific Handling

For the different cloud providers, there are some differences in the extraction of the cloud spend information

1. AWS

For AWS, cloud spend information is extracted for all scanned AWS Accounts automatically. In addition, for all Tag groups which are configured with a mapping to Software Artifacts in VSM, the Public Cloud integration will evaluate Cost Allocation tags setup in AWS.

2. Azure

For Azure, cloud spend information is extracted for all scanned Azure Resource Groups and Azure Subscriptions automatically.

3. Google Cloud

For GCP, cloud spend information is extracted for all scanned Google Cloud Projects automatically.

Representation of Cloud Spend Information in VSM

Within VSM, the Cloud Spend information is displayed in different places.

Cloud Accounts

For each Cloud Account, the Cloud Spend Last 30 Days is displayed, and also the Cloud Spend Yesterday.

Software Artifacts

If a mapping between Cloud Accounts and Software Artifacts has been established, the cloud spend information will also be associated to these mapped Software Artifacts.

1. If the Cloud Account is mapped to a Software Artifact based on tags on the Cloud Account, its cloud spend is fully assigned to that Software Artifact and stored on the relation between the Cloud Account and Software Artifact.
2. If the Cloud Account is mapped to a Software Artifact based on AWS Cost Allocation Tags, that cloud spend is assigned to the Software Artifact and stored on relation.
   For each Software Artifact the total cloud spend across the relations to all Cloud Accounts is then aggregated, again for both the "last 30 days" and "yesterday".

Example

The AWS Account "Team Cider" contains some EC2 instances tagged as microservice:order-history. For yesterday, AWS captured a cloud spend of $42 for the cost allocation tag order-history. Also, the Azure Resource Group "order-history" is tagged as microservice:order-history, and has a cloud spend of $36 for yesterday. Then, $42 resp. $36 will be stored as the Cloud Spend Yesterday on the relations between these Cloud Accounts and the Software Artifact, and $42 + $36 = $78 as the Cloud Spend Yesterday on the Software Artifact "order-history".