Cloud storage setup

1. Sign in to the AWS S3 Console.
2. Click Create bucket.
3. Choose a region and give the bucket a name.
4. Leave the default settings and click Create bucket.

1. Open the GCS Console.
2. Click Create bucket.
3. Choose a location and pick a storage class (Standard is fine for most use cases).
4. Click Create.

1. Open the Azure Portal.
2. Create a Storage Account if you don't have one.
3. Inside the storage account, go to Containers and click + Container.
4. Give it a name and click Create.

1. Sign in to the Oracle Cloud Console.
2. Navigate to Object Storage & Archive Storage.
3. Click Create Bucket, choose a compartment and name.
4. Click Create Bucket.

1. Install MinIO on your server or use an existing deployment.
2. Open the MinIO Console or use the CLI:

3. mc mb myminio/my-bucket

1. Sign in to the Cloudflare dashboard.
2. Go to R2 Object Storage and click Create bucket.
3. Give it a name and choose a location (or a jurisdiction, if your data must stay in the EU).
4. Copy your Account ID from the R2 overview page. Blixt uses it to build the S3 endpoint.

Change notifications

R2 delivers bucket events to a Cloudflare Queue rather than through the S3 API, so Blixt cannot subscribe to them the way it does on S3, GCS or Azure. Everything written through Blixt is visible immediately; changes made to the bucket outside Blixt — from the Cloudflare dashboard, wrangler or another S3 client — appear after the next filesystem scan instead of straight away. Nothing to configure: this is the default, and no other R2 behaviour is affected.

1. In the IAM Console, create a user (or role) with s3:* permissions on your bucket.
2. Go to Security credentials and click Create access key.
3. Copy the Access key ID and Secret access key.
4. Enter these in Blixt during setup.

Running inside GCE or GKE? Blixt supports Application Default Credentials (ADC) out of the box. GCE instances and GKE pods automatically authenticate to GCS via the metadata server, using the service account attached to the VM or workload. No credential files to manage — just make sure the service account has the Storage Object Admin role on your bucket.

Using gcloud on your machine? If you've run gcloud auth application-default login, Blixt will pick up your default credentials automatically. This is convenient for development and testing.

Other environments? You'll need to create and manage a service account key:

1. In the Service Accounts page, create a new service account.
2. Grant it the Storage Object Admin role on your bucket.
3. Click Keys → Add Key → JSON to download a key file.
4. Point Blixt at this JSON key file during setup.

Pub/Sub permissions

GCS requires Pub/Sub permissions to be configured for the project. Blixt creates a Pub/Sub channel to receive updates from GCS, but by default GCS doesn't have permission to publish to Pub/Sub. The following commands authorise GCS to send Pub/Sub messages to Blixt. See the GCS documentation for background.

1. Find the GCS service account for your project. Replace PROJECT with your GCP project name. Use the output as SERVICE-ACCOUNT in the next command.

gcloud storage service-agent --project=PROJECT

2. Grant the roles/pubsub.publisher role to the GCS service account:

gcloud pubsub topics add-iam-policy-binding projects/PROJECT/topics/bfs \
  --member="serviceAccount:SERVICE-ACCOUNT" \
  --role="roles/pubsub.publisher"

1. In the Azure Portal, open your Storage Account.
2. Go to Security + networking → Access keys.
3. Copy the Storage account name and one of the Keys.
4. Enter these in Blixt during setup.

1. In the Oracle Cloud Console, go to your User Settings.
2. Under Customer Secret Keys, click Generate Secret Key.
3. Copy the access key and secret key (S3-compatible).
4. Note your tenancy namespace and region. Enter all of these in Blixt.

1. Use your MinIO access key and secret key. These work the same as S3 credentials.
2. Set the endpoint URL to your MinIO server address (e.g. https://minio.example.com).
3. Enter these in Blixt during setup.

1. In the Cloudflare dashboard, go to R2 Object Storage → API → Manage API tokens.
2. Create an Account API token with Object Read & Write permission for your bucket.
3. Copy the Access Key ID and Secret Access Key. These are S3-compatible credentials.
4. Enter these, along with your account ID, in Blixt during setup.