How connections work
What happens after you connect a provider, how fresh the data is, and how to share setup with the account owner.
What happens when you connect
You grant read-only access
Each provider has its own method: a CloudFormation stack, an OAuth sign-in, a SQL snippet, a Helm chart, or an admin key. OpsLyft can see billing and usage data. It can't change, stop, or delete anything.
OpsLyft detects the connection
For most providers, you come back to OpsLyft and it detects the new role or grant automatically.
The first bill arrives
OpsLyft starts analysing as soon as the first billing data lands. Depending on the provider, that's minutes to hours after you connect. Exports that start fresh (such as a new Azure export or AWS CUR) can take up to a day to fill in.
Inventory and metrics follow
Where the provider supports it, OpsLyft polls resource inventory and utilisation metrics, which feed Atlas.
Connection states
| State | Where you see it | Meaning |
|---|---|---|
| live | Clouds picker | Data is current |
| Nh behind | Clouds picker | The latest data is N hours old |
| Syncing | Onboarding, settings | The first sync or a backfill is running |
| not connected | Clouds picker | Select connect to set it up |
| Healthy / Not connected | Tickets → Integrations | Tool connections |
Don't have access?
If you can't grant access yourself, select Copy link under Don't have access? on the connect screen and send it to whoever owns the provider. They complete the setup, and you get a Slack message when they finish.
Data freshness
Providers publish billing data on a delay. See Data freshness for typical delays and how OpsLyft marks incomplete days.