Integrations
Integration Prerequisites
To optimize financial management and ensure complete monitoring of budgets and consumption, your team must have the prerequisites and competencies listed below:
| Provider | Prerequisites | Required Services | Competencies |
|---|---|---|---|
| AWS | AWS Organization, IAM permissions | Cost & Usage Reports, S3 | IAM Administration, Cost Management, Security |
| GCP | Organization-level IAM, API enablement | BigQuery, Cloud Resource Manager | GCP IAM, BigQuery, Security |
| Azure | Microsoft Entra ID, role assignment | Cost Management + Billing, Storage Account | Azure Identity, Storage, Security |
| OCI | Tenancy OCID, Access Policy (IAM), API Key | Usage and Cost Reports, Object Storage | OCI IAM Administration, Cost Management, Security |
Key Steps
(Objective: Integrate billing data into the platform)
These are the main focuses of your configuration in each provider before starting the final integration:
AWS:
- Create IAM user and save ARN.
- Configure Cost & Usage Report export to S3 bucket (us-east-1 region).
- Create IAM policy with least privilege (S3 access, organization listing, IAM simulation).
- Attach policy to user.
- Generate access key and download CSV file.
- Provide bucket path and credentials to the platform.
GCP
- Enable necessary APIs (BigQuery, IAM, Resource Manager).
- Export billing table to BigQuery.
- Create service account and generate JSON key.
- Create custom roles (BigQuery Viewer, BigQuery User, Project Viewer).
- Assign roles at organization, project, and table levels.
- Integrate using service account email and JSON key.
Azure
- Create App Registration and note Client ID.
- Generate secret key and save value and ID.
- Assign role (EventGrid Event Subscription Reader) to App Registration.
- Create storage account and container for exports.
- Configure cost exports (Actual and Amortized) to storage.
- Generate SAS token and connection string.
- Provide Client ID, Secret, Object ID, Subscription ID, storage details, and SAS token to the platform.
OCI
- Create the group and add the responsible members
- Configure a policy with a statement allowing the group to read usage reports in the Tenancy
- Add an API Key, download the private key, and copy the configuration details
- Record the User OCID, Tenancy OCID, Fingerprint, and Region displayed after key creation
- Integrate by providing the collected identifiers and upload the private key file to the platform
Step by step
To ensure that provider data is displayed correctly on the platform, follow the initial integration step-by-step guide, starting with creating an "org" (organization) for each provider, and subsequently integrating the Cost Orchestrator for them within that same organization.
After this step, download the Financial Structure spreadsheet and follow the guidelines in this section for correct completion. After inserting it into the platform, don't forget to integrate the Recommendations specific to each provider, this will ensure that automatic optimization suggestions are made available, helping to improve efficiency and reduce costs.
Important
At each step of this integration process we have a guide for each provider