Manage connections
Find a connection, read its checks, see what each source has delivered, choose which workspaces see its cost, sync it on demand, update its credentials, and remove it.
A connection is made once for the organization. It then feeds cost into every workspace it is associated with. This page covers what happens after a connection is saved; each provider page covers how to connect it.
Before you start
- Open Integrations in the sidebar, or Settings, then Integrations.
- Connecting, renaming, updating and removing connections needs the Owner or Integration owner organization role. Syncing needs the Owner, Integration owner or Editor organization role. See Access model.
Find a connection

Collection status in the page's header shows what each cost source has delivered; see Collection status.
The page has these cards:
- Connected lists one row per integration with the number of its connections (of its clusters, for Kubernetes), its Status and its Last sync. The status is the worst of its connections' statuses, so one broken Azure subscription shows on the Azure row; Last sync is the most recent of them.
- Data sources lists what Costfluent connects to: AWS, Azure, Google Cloud, OVHcloud, Scaleway, Anthropic, OpenAI, Cursor, ClickHouse Cloud, Datadog, GitHub, a FOCUS export and Kubernetes. A source you already use is marked "Connected".
- Upload as CSV lists the custom provider, which takes the cost of a source with no direct connection as FOCUS CSV files.
- Not available yet lists known sources with neither a connection nor an upload path. Each one's Contact us opens the contact form on the website, where you can ask for it. The card appears only while there is one.
- Apps lists the apps announced for Costfluent. They are not available yet.
Select an integration to open its page. It has two tabs: Manage lists the integration's connections, and Connect holds the setup steps and the button that adds a connection. Kubernetes has the same two tabs: its connections are clusters, Connect holds the agent's install steps and Add cluster, and each cluster's page holds its health and default rates as well; see Kubernetes.
On Manage, each row is one connection, named by the display name you gave it, with its Status beside the name. The account the provider verified has its own column, with a button to copy it: the AWS account ID, the Azure tenant ID under Tenant ID, or the Google Cloud billing account ID. A custom provider has no account, so that cell stays empty. The row also shows Workspaces, the workspaces the connection feeds ("None" when it feeds none, with a count of those you cannot view), and Last sync, then three controls: a sync button, a gear that opens the connection, and a menu with Rename and Remove connection.
Read a connection's status
The Status of a connection says what collection is doing:
| Status | Meaning |
|---|---|
| Pending | Saved, not collected yet |
| Connecting | The first contact with the provider is in progress |
| Importing | Collecting its first months; it reads Active once its first import has finished |
| Active | Collecting normally |
| Syncing | A collection is running now |
| Degraded | The credentials work, but expire soon, or the provider refused access to its savings recommendations; open the connection to see which |
| Paused | Not collected, because your organization has more connections than the limit set for it; only the oldest ones collect |
| Error | The last collection or the latest credential check failed; open the connection to see why |
| Disabled | Not collecting |
Select the name, or the gear on its row, to open the connection. Its page is titled with the connection's name, which also ends the breadcrumb above it, and its address ends with the connection's ID, which starts with prv_. The Public API and the Terraform provider use the same ID. The header shows the connection's Status, Sync for those who may sync it (Sync a connection), and for Owners and integration owners More actions, which holds Remove connection. A Paused connection says so above the cards under Collection paused, with a link to contact us about the limit.
Under Connection status, the page says how far the connection's data reaches, "Cost data through" a day or "No cost data committed yet", and once data has arrived, what the last 30 days add up to. An AWS connection's first collection reads Cost Explorer while its data export has not delivered a file yet, so that figure appears within minutes of connecting; the export's rows replace it once they arrive. Owners, integration owners and the partner that manages the organization see the figure for every connection. Anyone else sees it only when they can view a workspace that reads the whole connection, not just some of its accounts.

The page holds these cards:
- Connection shows the connection's name, its account ID with a button to copy the ID, and its Last sync, and, for Owners and integration owners, Rename and Update credentials, which reads Test connection on AWS and Google Cloud (Update credentials). An error from the last collection is shown here in red; when the collection failed, How to fix this opens the troubleshooting section of the provider's page, and when the credentials are the cause, the credentials button sits beside the error. When Costfluent's own processing failed, the error says so, nothing in the connection needs changing, and Contact us opens the contact form instead.
- Connection status says whether the stored credentials still work. Its badge reads Healthy, Degraded, Error or Not checked. Below it, Authentication and Cost data access each read Passed, Failed or Not run. A failed check is open, with what it means, the provider's own message and How to fix this, which opens the troubleshooting section of the provider's page; select any other check to see what it means.
- Credits lists the credit grants of the connection's billing account, what each has left and the day paid usage is projected to start, for those who may read the whole connection; see Credits.
- Workspace access lists every workspace with a checkbox; see the next section.
- Imports lists each Billing period of your plan's backfill, newest first, with its Records, Amount and Provider total, the day it was Restated, if it was, and its Status: Imported, No data available or Not collected. A month marked No data available is a real gap: the connection collected for it and nothing arrived. Not collected marks a month older than the connection's first collection, which Collect older months on the card collects on request; a line under the table says so whenever a month reads Not collected. View collection status opens this connection's row on Collection status, which explains the amount, the provider total and the restated day, and who sees the amounts. See How it behaves.
- Sync history lists the connection's recent collection runs with when each Started, its Records and its status: Complete, Incomplete or Failed. An incomplete run published its data without the rows it could not import, and says how many. If the history cannot be loaded, Retry loads it again.
- Accounts on AWS and Subscriptions on Azure list what the connection reaches, each with its ID, a button to copy it, and its state:
- Collecting: collected by this connection.
- Covered: its cost arrives through another account's collection, such as an AWS member account billed to the management account. A line under the table says so whenever an account reads Covered.
- Unavailable: reachable but not collectable, for example an Azure subscription where the connection holds no cost role. The reason is shown.
A Google Cloud connection has no such card: it is one billing account, which Connection shows.
Run the checks
- Open the connection.
- In Connection status, select Run checks. "Checks started. The results appear here when they finish." confirms the request.
- Wait on the page. The checks run in the background, and the page updates itself when they finish.
Run checks is available to Owners and integration owners. After a run it rests for a short while before it can be started again, and "Available again" under the button says when. An organization runs checks on one connection at a time: Run checks pressed while another connection's checks are queued or running is refused, with a wait of a minute.
Collection status
Collection status shows every cost source of the organization on one page: how it delivers, when it last did, how far its data reaches and when its next delivery is due, and under each source, its months and the days no collection covered. Kubernetes clusters are not listed, because their cost comes from their agent's reports rather than from a collection; see Kubernetes.
- Open Integrations, then Collection status in the page's header. On a connection's page, View collection status on the Imports card opens the page with that connection's row already open.
- Select the arrow at the end of a source's row to show its months, and again to hide them.

Each row shows:
- Source: the connection's name, with Late beside it when its delivery is overdue (see below), and Importing while its first import has not finished.
- Delivery: how the source's cost arrives.
- Last import: how long ago a collection or upload of it last completed.
- Data through: the last day its imported data covers.
- Next delivery: the day its next data is due, counted from Data through by the connection's sync schedule (Automatic syncing). A source delivered on upload has none, and neither has a connection that is Pending, Connecting or Disabled.
Delivery reads one of these:
- Daily: a day's cost at a time, read at each sync. AWS, Azure, Google Cloud, Anthropic, OpenAI, Cursor, ClickHouse Cloud, Datadog and GitHub deliver daily, and so does a FOCUS export that STACKIT writes.
- On upload: whenever you upload cost, as to a custom provider. Nothing is due, so such a source is never late and has no missing days.
- Hourly, Month to date and Monthly invoice: a source read by the hour; one that reports the running month so far and reads it again whole at each sync, whose newest month reads "(to date)" after its name; and one delivered a month at a time once the provider has issued its invoice, whose next delivery is due a set number of days after the month ends. OVHcloud, Scaleway and a FOCUS export that OVHcloud writes read Month to date.
Late appears when a source has fallen far enough behind for Costfluent to send its notice that the connection's data is behind (Notification channels), and goes once its data has caught up.
The months under a source's row, newest first and back to the start of your plan's backfill, are those of its connection's Imports card:
- Billing period, Records and Status, as on the Imports card.
- Amount: the month's billed cost, one line per billing currency.
- Provider total: the provider's own total for the month and how Costfluent's compares with it. Agrees means the two match within a small tolerance. "Differs:" is followed by Costfluent's amount less the provider's, and Differs stands alone when the two are not in one currency or the amounts are hidden. "Neither had cost" means neither side found cost; "Not compared yet" and "No provider total for this source" mean there is no comparison.
- Restated: the day Costfluent last collected the month again after it had closed, because the provider revised it. The month's records and amount are then the revised ones.
Costfluent reads the provider's own total for AWS, Azure and Google Cloud, and compares each closed month with it once the provider has had time to revise the month. For AWS the comparison reads Cost Explorer, and AWS bills each request to your account. Every other source reads "No provider total for this source".
Below the months, Missing days lists each stretch no completed collection covered, from From to To, with Accounts affected: how many of the connection's accounts, subscriptions or projects miss every day of it. A source delivered by the month lists Missing months instead. The days counted run from each account's first collected day to Data through; "No missing days" says none is missing.
A missing day is one no completed collection covered. It does not mean the provider had no cost that day.
When a source sent fewer charges for a closed month than Costfluent had imported, Costfluent keeps the imported ones, and the source's open row says so above its months, as the connection's page does.
Amount, and the figures under Provider total, are shown to whoever sees what a connection's last 30 days add up to under Connection status: Owners, integration owners and the partner that manages the organization, for every connection, and any other member for a connection that a workspace they can view reads whole, not just some of its accounts. Others see Hidden in their place and a line under the table that says who sees them; the verdicts, the records and the rest of the page stay. The Imports card follows the same rule.
The Public API reads the same status: GET /v1/providers/collection-status lists every source, and GET /v1/providers/{providerId}/collection-status returns one with its months and missing stretches. See the API reference.
Choose which workspaces see the cost
A connection's cost appears only in the workspaces it is associated with. There are two places to set that:
- From the connection: Workspace access has a checkbox for each workspace. Owners, and integration owners who can edit that workspace, can change it. A workspace that reads only some of the connection's accounts says so under its name, and workspaces you cannot view are counted below the list. Unticking a workspace asks you to confirm first; a workspace that read only some of the connection's accounts loses that choice, and ticking it again reads all of them. A Kubernetes cluster has the same card on its own page; see Kubernetes.
- From a workspace: Settings, then Workspace providers, lists the connections the current workspace uses. Add provider associates another connected one. The Enabled switch decides whether this workspace reads the connection: switched off, the connection's cost leaves this workspace's reports, budgets and alerts, its anomalies leave the workspace's anomaly list, its commitment expiry and credit notices stop reaching the workspace, and the connection leaves the workspace's automatic schedule; see Automatic syncing. The connection's Credits card and what its last 30 days add up to are then hidden from anyone who sees them only through this workspace. The link and the accounts chosen for it stay, so switching it on again restores both. The bin icon on a row removes it after you confirm Remove provider: this workspace stops reading the connection and loses its choice of accounts, while the connection and its cost data stay and other workspaces keep reading them. Only Owners, and integration owners who can edit the workspace, can add it back, so the confirmation also offers Turn off instead, which keeps the link and its accounts.


Switching a workspace's providers on or off and removing them needs the Editor team role on that workspace with Can edit access. Adding a provider and choosing its accounts decide which of the organization's accounts the workspace reads, so they also need the Owner or Integration owner organization role.
A workspace can also read only some accounts of an AWS or Azure connection, so one AWS organization or Azure tenant can be divided between workspaces. Under Workspace providers, select Choose accounts on the connection's row. Under Accounts, choose All accounts for the whole connection, including accounts it discovers later, or Chosen accounts and tick the accounts this workspace reads, then select Save. Each workspace chooses its own accounts of the same connection, and two workspaces may choose the same account. A connection that lists no accounts is always read whole. In Terraform, account_ids on costfluent_workspace_provider sets the same choice; see Terraform.
Sync a connection
Use the sync button on a connection's row; its label is "Sync" and the connection's display name. On the connection's page, Sync in the header does the same. "Sync started" confirms the request. While a connection is Paused or already syncing, its sync button is held; on the row, its tooltip says which. If Costfluent does not start it, for example because the connection is already syncing, "Sync not started" says why. Custom providers have no sync button, because their cost arrives by upload. Automatic syncing covers the schedule and when an explicit sync still runs.
Update credentials
When a key or password changes on the provider side, open the connection and select Update credentials on the Connection card, or beside a failed collection the credentials caused. For an Azure connection, enter the new Service principal password; the tenant and app ID are already filled in. For Anthropic, enter the new Admin API key, for OpenAI the new Admin key, for Cursor the new Admin API key, for ClickHouse Cloud the Key ID and Key secret of the new key, for OVHcloud the Application key, Application secret and Consumer key of the new key, for Scaleway the new Secret key with your Organization ID, for Datadog the new API key and Application key, for GitHub the new Personal access token with the Organization, and for a FOCUS export the Access key ID and Secret access key of the new key. An OVHcloud connection's Platform, a Datadog connection's Datadog site and a FOCUS export's Provider, Region, Bucket and Prefix are already filled in. Then select Save. Costfluent checks the new credentials with the provider before saving them and then runs the connection checks in the same dialog. If the check fails, nothing changes and the current credentials stay in use.
AWS and Google Cloud connections hold no key or password, so their button reads Test connection. Its dialog tests the connection and says that its access is changed in the cloud account, with a link to the provider page's section on changing it.
Rename a connection
- Open the integration's page on the Manage tab, open the menu at the end of the connection's row and select Rename. On the connection's page, Rename on the Connection card does the same.
- Enter the new Display name and save it.
When you add a connection, Display name starts filled with the integration's name, such as Microsoft Azure, or with the lowest free number after it, such as Microsoft Azure 2, when a connection already has that name. A custom provider's starts empty, because its name is also the provider name on its costs. A display name is any text of up to 255 characters, and two connections may share one: the account ID beside each tells them apart. Renaming asks nothing of the provider and leaves the credentials, the checks and the collected cost as they are. The console, the carbon export, and the emails and notices sent from then on use the new name; those already sent keep the old one. The Public API's PUT /v1/providers/{providerId} with a displayName renames a connection too, and a connection that Terraform manages takes its display_name back from the configuration at the next apply.
A Kubernetes cluster's connection is renamed the same way, with Rename in the cluster's row menu or on its Connection card. A cluster's name cannot be empty: to name it by its cluster ID, type the cluster ID; see Kubernetes.
A custom provider's name is also the provider name on its costs, written when they are uploaded. After a rename, costs already uploaded keep the old name and new uploads carry the new one, so Cost Reports show the two under separate provider names.
Remove a connection
- Open the integration's page on the Manage tab.
- Open the menu at the end of the connection's row and select Remove connection. On the connection's page, More actions, then Remove connection does the same, and takes you back to the integration's page once the connection is removed.
- Confirm with Remove in the Remove connection dialog, which names the connection.
Removing a connection does not revoke the access you granted Costfluent at the provider. Revoke it there, as the provider's page describes under Update or disconnect; the dialog links that section.
Removing a connection takes it out of every workspace at once and erases the cost data it imported. This cannot be undone. Reports, budgets and alerts stay, but no longer show that connection's cost.
To stop one workspace seeing a connection without deleting its data, remove it from that workspace under Workspace providers instead.
An organization removes at most 120 connections in any hour, Kubernetes clusters included, in the product and through the Public API together. Past that, a removal is refused with the time to wait and removes nothing; a Terraform destroy refused by it is run again after the wait.
How it behaves
- History on connecting. A new connection's first collection imports your plan's backfill, and at most six months of it. Connecting the same account again after removing it creates a new connection, which starts over the same way. On Business and Custom, whose backfill reaches further, the rest is collected on request: Collect older months on the Imports card, for anyone who may sync the connection, asks the provider for those months, and so does the Public API's sync with
"fullSync": true(Automatic syncing). Each provider returns only what it still holds: AWS Cost Explorer up to 14 months, without resource or tag detail, each request billed to your account; Azure up to 13 months; Google Cloud from the day its billing export started. What it imports counts toward this month's usage, and a connection's older months can be requested once every 24 hours. - When the first import finishes. A new connection reads Importing until every month its first collection asked for has arrived and its data has caught up with its sync schedule. Then it reads Active, and the workspaces it feeds and whoever added it are told what it brought in; see Notification channels.
- Checks on their own. Costfluent runs every connection's checks again once a day, so Connection status changes without anyone selecting Run checks. Automatic syncing says which connections that covers.
- Saved without a check. If the provider cannot be reached while a connection is saved, it is saved anyway, "Saved." says so, and Costfluent checks it again automatically.
- Tests and cost. Each Test connection asks the provider again; for AWS that is a Cost Explorer request billed to your account. A connection is tested at most once a minute with the same credentials and settings: a test sooner says how long to wait, and saving credentials or changed settings allows one straight away. Credential tests while adding a connection and Run checks share one limit per organization; once it is reached, a further test or run is refused for up to an hour.