Data sync cadence
Sync timeline
| Event | Typical duration |
|---|---|
| Initial connection validation | Minutes |
| First billing data available | 2–4 hours |
| Ongoing billing sync | Hourly |
| Resource discovery | Continuous / periodic scans |
| Recommendation generation | 24–48 hours after sufficient history |
| GCP BigQuery first export | Up to 24 hours |
Provider-specific notes
AWS
CUR files typically arrive in S3 within several hours of the billing period. Costimizer polls the configured bucket on an hourly schedule.
Azure
Cost Management data refreshes daily; Costimizer syncs on an hourly cadence once available.
GCP
BigQuery billing export updates once per day. Allow 24 hours after enabling export before expecting complete data.
Kubernetes
The cost collector reports metrics in near-real-time; node infrastructure costs follow the parent cloud sync schedule.
What to expect after connecting
| Time after connection | What you should see |
|---|---|
| 0–30 min | Data source status: Connected |
| 2–4 hours | Cost Explorer shows initial spend data |
| 24–48 hours | Recommendations begin appearing |
| 1 week+ | Forecasts and anomaly detection improve |