Cloud Billing Sources
Cloudaware FinOps relies on provider billing exports and APIs to ingest detailed cost and usage data. This guide summarizes the requirements for each major cloud.
AWS
Cloudaware supports AWS cost ingestion through modern and legacy mechanisms:
AWS Data Exports (CUR 2.0) or Cost & Usage Reports (CUR) – recommended for most environments.
Legacy Detailed Billing Reports (DBR) – supported for customers that still rely on historical DBR pipelines.
Steps:
Add AWS Payer/management account to Cloudaware.
Create one or more CUR or Data Export (CUR 2.0) configurations that:
Deliver reports to an S3 bucket in a supported format and cadence.
Include all accounts.
Use hourly or daily granularity as required by your reporting needs.
Grant Cloudaware access to the S3 bucket and manifest paths according to the billing integration guide.
Configure the AWS Billing integration in Cloudaware (payer/management account is recommended).
Cloudaware is designed to handle very large, consolidated billing files and offers analytics over blended and unblended rates, reservation and Savings Plans utilization, and other AWS billing metrics.
See also: AWS Billing
Azure
Cloudaware ingests Azure costs from supported agreements and exports, including:
Microsoft Customer Agreement (MCA) and Pay‑As‑You‑Go subscriptions.
Legacy Enterprise Agreement (EA) enrollments.
Steps:
Add Azure Active Directory to Cloudaware.
Enable cost exports (for example, to Azure Blob Storage or via Cost Management APIs) for the relevant enrollments and subscriptions.
Ensure that exports include all required subscriptions and that Cloudaware has read access to the storage account or API.
Configure the Azure Billing integration in Cloudaware.
See also: Azure Billing
Google Cloud
For Google Cloud, Cloudaware uses Billing Export to BigQuery and/or file exports:
Steps:
Add Google service account to Cloudaware.
Enable Billing Export in the Google Cloud console for each billing account in scope.
Choose a BigQuery dataset (and/or Cloud Storage bucket) where cost and usage data will be written.
Grant Cloudaware access to the dataset/bucket using the roles described in the integration guide.
See also: Google Billing
Other Sources
Cloudaware can also ingest costs from:
Oracle Cloud – via supported billing export mechanisms.
Kubernetes clusters – via OpenCost or other supported cost attribution integrations.
Custom cloud or reseller billing sources – via Google BiGQuery or Salesforce connectors for BI Analytics.
Next Steps
After configuring billing exports for each provider:
Confirm that Cloudaware is receiving and processing new data (on CMDB records)
Review Data Health & Freshness to understand expected latency and how to detect missing or delayed data.