Guides

Resource inventory & sync

Work with Cloud Control's synced inventory: keyset-paginated reads, filters, freshness, delta sync, soft-deleted resources and the includeDeleted flag — and why the UI never calls clouds.

Inventory is the searchable record of what you run across connected accounts. It is produced entirely by the background sync engine; a page load reads it from the database and never fans out to a cloud provider.

The Inventory screen with real synced resources and a last-synced marker

Reading inventory

`GET /api/cloud/resources` returns your synced resources with keyset (cursor) pagination. Each row carries provider, resource type, native id, name, region/zone, status, normalized attributes, provider-specific detail, tags, and first-/last-seen timestamps. Filter by provider, type, region and a free-text q.

bash

curl -s "https://cloud-control.snoweasl.com/api/cloud/resources?provider=AWS&type=ec2-instance&limit=50" \
  -H "Authorization: Bearer cc_pat_YOUR_TOKEN_HERE"

Delta sync and first-/last-seen

Sync is incremental: a pass uses delta cursors to fetch what changed, then normalizes each resource into a common shape while preserving provider-specific detail. A resource's firstSeenAt and lastSeenAt tell you when Cloud Control first discovered it and when it last confirmed it.

Soft-deleted resources

When a resource disappears upstream it is soft-deleted with the reason removed_upstream; disconnecting an account marks its rows account_disconnected. Both are hidden by default and surfaced with includeDeleted=1, which also returns deletedAt and deletedReason so you can tell an upstream deletion from a disconnect.

Why the UI never calls provider APIs

Routing every read through the database keeps the console fast and predictable, puts provider rate limits under the engine's token-bucket control, and means a single slow or throttling cloud can never hang your inventory screen.

Scale

For most organizations the console envelope carries the shaped inventory directly. The keyset endpoint is the seam that takes over when an organization crosses the payload budget. Ten-thousand-resource virtualization and a dedicated queue/worker sync tier are on the roadmap.