Cloud
AWS, Azure, and GCP, including the billing exports each requires.
Public cloud providers. Each requires a billing export configured on the provider side before cost data will populate.
Providers
AWS
| Field | Value |
|---|---|
| Device type | AMAZON_AWS |
| User role | IAM user with read-only API access |
| Default ports | 443 |
| Collection method | API |
| Required parameters | IP: aws.amazon.com User: Access Key ID Password: Secret Access Key |
| Notes | Under “Cost and Usage Reports”, a cost report must be configured at a daily interval with ZIP compression. See the AWS documentation on managing access keys for IAM users. |
Azure
| Field | Value |
|---|---|
| Device type | MICROSOFT_AZURE |
| User role | Reader and Cost Management Reader |
| Default ports | 443 |
| Collection method | API |
| Required parameters | IP: Tenant ID or Directory ID User: Client ID, from an App Registration Password: Client Secret, generated from the App Registration |
| Notes | Requires an application registered in the Azure tenant under App Registrations, granted the “Reader” and “Cost Management Reader” roles on each subscription to be included in data collection. |
GCP
| Field | Value |
|---|---|
| Device type | GOOGLE_CLOUD_DEVICE |
| User role | Service account with the following project roles: Viewer (roles/viewer), Billing Viewer (roles/billing.viewer), Monitoring Viewer (roles/monitoring.viewer), and Compute Viewer (roles/compute.viewer) |
| Default ports | 443 |
| Collection method | API |
| Required parameters | Service Account Key Path: full path to the service account key JSON file |
| Notes | Download the service account’s JSON key file to the data collection machine. Enable the Cloud Resource Manager, Cloud Billing, Cloud Monitoring, and Compute Engine APIs. Each project also needs a Cloud Billing export with detailed usage cost data, in a BigQuery dataset whose name matches the project name. |