/// GUIDES / SEARCH & REAL-TIME INDEXING
Search & real-time indexing
Global search finds any object by name across every connected Fleet at once. It is backed by a local index, so a query reads from storafleet's own store — there are zero provider API calls at query time.
How search works
Type a name into global search and storafleet matches it against the local index of object keys for all your buckets. The index stays fresh two ways, which work together:
- Browse-time indexing — the default universal fallback. Objects are indexed as you browse.
- Event-driven real-time indexing — the provider pushes create and delete events to a webhook so the index updates instantly.
Browse-time indexing
Browse-time indexing is on for every Fleet, on every provider — it is the universal fallback that always works. As you navigate a bucket's prefixes, the objects you load are added to the local index. The more you browse, the more complete your searchable index becomes, with no extra setup.
Event-driven real-time indexing
When a provider supports it, you can wire up real-time indexing. The provider pushes object create and delete events to a per-Fleet, token-authenticated webhook, and storafleet updates the index the moment the event arrives.
- Each Fleet has its own webhook endpoint, authenticated by a token so only that provider can post to it.
- The index reflects changes instantly — even for changes made outside storafleet, such as an upload from another tool or the provider console.
Real-time wiring by provider
How the events get delivered depends on the provider:
- AWS — events flow through SNS; the subscription is auto-confirmed.
- Cloudflare R2 — events are delivered by a Worker.
- MinIO — events come from direct bucket notifications.
- Other providers — fall back to browse-time indexing.
The webhook secret
When you enable real-time indexing, storafleet issues a one-time secretthat authenticates the webhook. You can rotate it or disableit at any time from the Fleet's settings. Rotating issues a fresh token; disabling turns event delivery off and falls back to browse-time indexing.