Cloud spend
Costs → Cloud shows what the clouds billed for everything, not only AI, from each cloud’s own cost data. It answers the question the AI figures cannot: how much of the cloud bill is AI, and where the rest goes.
Connectors
Section titled “Connectors”Three spend connectors read whole-cloud cost. They share the costs table with the AI vendors but are kept out of every AI figure, the reconciliation and the API keys tab.
| Connector | Source | Grouped by |
|---|---|---|
| AWS (Cost Explorer, all services) | ce:GetCostAndUsage, unblended cost, daily | Service, and a cost allocation tag you name, or the linked account when no tag is set |
| Azure (Cost Management, all services) | Cost Management query, actual cost, daily | Service, and a tag you name, or the resource group when no tag is set |
| Google Cloud (billing export) | The standard usage cost export table in BigQuery | Service, and a label you name, or the Google Cloud project when no label is set |
For AWS, the tag must be activated as a cost allocation tag under Billing before Cost Explorer will group by it. For Google Cloud, the service account needs BigQuery Job User on the project named in the table (it runs the query) and BigQuery Data Viewer on the export dataset — see the setup guide; credits are applied, so the figure matches the invoice.
Each connector reads its full history once (Cost Explorer keeps 14 months, or 38 with multi-year history on; Cost Management and the billing export keep what they were given), then re-reads the last 31 days on each sync so late corrections are picked up.
The screen
Section titled “The screen”- Cloud bill, of which AI services, and everything else. AI services are Bedrock, SageMaker, Azure OpenAI and AI services, Vertex AI, Gemini and the other managed AI APIs.
- By provider, with each provider’s AI part.
- By project: the tag, account, resource group or Google Cloud project, whichever the connector groups by.
- By service, with AI services marked.
- By day, with the AI part.
What it is not
Section titled “What it is not”It is not the AI reconciliation. Bedrock and Azure OpenAI appear here as part of the cloud bill and, through their own connectors, in the AI figures; the two screens answer different questions and are not added together.