Cloud providers
The object stores BlixtFS can serve, and what each supports.
| Provider | Scheme | Change notifications | Notes |
|---|---|---|---|
| Amazon S3 | s3:// |
S3 events via SNS and SQS | |
| Google Cloud Storage | gs:// |
Pub/Sub | Needs a one-time IAM grant for Pub/Sub |
| Azure Blob Storage | azure:// |
Event Grid via Service Bus | |
| Oracle OCI Object Storage | oci:// |
OCI Events via Streaming | |
| MinIO | minio:// |
Bucket notification webhook | Self-hosted; set the endpoint URL |
| Cloudflare R2 | r2:// |
Cloudflare Queues | Notifications need an API token; see below |
| CoreWeave AI Object Storage | cw:// |
None | See below |
Every provider stores files the same way, one ordinary object per file, so you can move a bucket’s data between providers with the providers’ own tools and serve it again.
Other storage systems or cloud providers can be added on request. Please contact us.
Provider notes
Amazon S3
Configuration-file entries for S3 buckets need the bucket’s actual region. On
the command line, set it with --aws_default_region.
Google Cloud Storage
BlixtFS creates a Pub/Sub topic named blixtfs for notifications. Cloud
Storage’s own service agent needs permission to publish to it. The
setup guide has the two
commands.
Cloudflare R2
- R2 routes a bucket’s events to one Cloudflare Queue. You create the queue and its HTTP pull consumer. BlixtFS finds it and creates the notification rule if one is missing.
- Draining the queue needs a Cloudflare API token, separate from the R2 access keys. Without one, R2 buckets are served normally and outside changes are found by consistency checks.
- Each queue message is delivered to only one consumer. Run one BlixtFS deployment per bucket, or use the event log to share a bucket’s changes between deployments.
- BlixtFS can’t create or delete R2 buckets.
See the setup guide for
the wrangler commands.
CoreWeave AI Object Storage
- CoreWeave has no change notifications. Changes made outside BlixtFS appear after the next consistency check.
- Only static access keys are supported.
- Create buckets in the CoreWeave console. BlixtFS can’t create them.
- The in-cluster LOTA cache endpoint can be turned on with
--coreweave_use_lota, but it is off by default and not yet verified.
MinIO
MinIO pushes notifications to BlixtFS through a webhook, so the MinIO server must be able to reach BlixtFS.