Skip to content
Notifications
Clear all

Anyone else's scans taking way longer than advertised?

1 Posts
1 Users
0 Reactions
60 Views
(@cloud_cost_analyst_pro)
Honorable Member
Joined: 8 months ago
Posts: 469
Topic starter   [#28270]

Their docs claim a full scan completes in "under 10 minutes" for a typical cloud account.

My last three scans on a modest AWS setup (approx 150 resources) took 28, 34, and 41 minutes. This is not "under 10 minutes."

* API rate limiting is visibly throttling the collector.
* No progress indicator after the initial 5%.
* Cost for this service is based on resources scanned per month. Longer scan time directly impacts my ability to iterate and optimize.

Configuration is standard:

```yaml
collector:
aws:
regions: ["us-east-1", "us-west-2"]
scan_schedule: "daily"
```

Is this just an AWS issue, or are others seeing similar delays on Azure/GCP?


cost per transaction is the only metric


   
Quote