Onboard Providers to Yotascale

Yotascale will need READ access to your provider account and a few metrics to properly report costs.

In summary, what we need access to is:

Cost Usage Reports:

These have different names for each provider

• AWS: Cost and Usage Report (CUR) files. These are shared via an Assume Role with permissions to read from an S3-bucket/prefix

• Azure: Cost Management Export data. These are shared via an App Registration process stored in a storage account/container/directory

• GCP: BigQuery dataset table exported via a parquet file to a bucket/prefix via a
  ”service account

Container Insights:

• To get Container metrics we can either collect them via a Prometheus agent that you need to run your clusters

• Provider container Insights: if you do have it enabled. These usually incur additional recurring costs.

• Cost Optimization Reports:

Yotascale will aggregate all the provider recommendations and will give a consolidated view. Moreover, Yotscale will allocate recommendations to business contexts (Teams, Departments, Applications, Product, Projects, Cost Centers, etc). This is possible via the matching business rules created in Yotascale with the provider recommendations reports.

These Cost Optimization Reports are:

• AWS: Trusted Advisor

• Azure: Advisor

• GCP: Recommendations Hub

How to access this information:

• AWS: via a CloudFormation Template with a YAML file that creates a custom role that uses the “assume role” to Read data

• Azure: via App Registration and sequence of UI and Azure CLI commands to enable it

• GCP via a Service Account created in the UI