# Process video in any S3-compatible bucket

Give Rendobar an endpoint, a region and a key pair, and any job reads from and writes to MinIO, Wasabi, Backblaze B2 or Hetzner over the S3 API. The endpoint must be public https.

Storage connection · Endpoint, region and key pair · Job input and destination · MinIO, Wasabi, Backblaze B2, Hetzner

Page: https://rendobar.com/integrations/s3-compatible/ · Connect a bucket: https://app.rendobar.com/storage?connect=1&provider=s3-compatible · Read the docs: https://rendobar.com/docs/storage/s3-compatible

- Type: Storage connection
- Built by: Rendobar
- Auth: Access key ID and secret access key
- Used as: Job input and output destination
- Works with: MinIO, Wasabi, Backblaze B2, Hetzner Object Storage, any S3 API on a public https host
- Pricing: Free
- Category: Storage

## Overview

Jobs read objects as `storage://` paths and deliver outputs back over the S3 API. The dashboard asks for the endpoint, region, bucket and a key pair, then tests them on one object before saving. The [S3-compatible docs](https://rendobar.com/docs/storage/s3-compatible) cover path-style URLs and connecting from the SDK.

## Reference

### S3-compatible setup

- Fields: Endpoint (https, public host), Region, Bucket, Path-style URLs, Access Key ID, Secret Access Key
- SDK: client.storage.create({ provider: "s3-compatible", id, bucket, endpoint, region, pathStyle, credentials: { type: "keys", accessKeyId, secretAccessKey } })
- Path-style on: https://<endpoint>/<bucket>/<key>. Off: https://<bucket>.<endpoint-host>/<key>
- Key permissions: read and write objects. Delete optional, list only for browsing from the dashboard
- If the endpoint doesn't refuse overwrites, Name conflicts is fixed to Replace
- Public URL: your provider's public or CDN domain
- If the bucket doesn't exist, the dialog offers Create the bucket and connect
- Revoke: delete or deactivate the key in your provider's console

### Addressing

- Inputs: storage://<connection-id>/<path>, anywhere a job accepts a file URL
- Outputs: destinations: ["storage://<connection-id>[/<folder or path template>]"]
- Connection ids match [a-z0-9-]{2,40}
- In a path, write % ? # as %25 %3F %23

### Output path

- Default template (By date): rendobar/{date}/{source_name}.{ext}. Also Flat: rendobar/{source_name}.{ext}, or a custom template
- Tokens: {job_id} {ext} {source_name} {date}
- storage://<id> uses the template, storage://<id>/<folder> uses the folder plus the template's file name, a path with a token or a file name is used as written
- Name conflicts: Keep both (default, adds the job id's last 6 characters) or Replace

### Connecting

- Dashboard: Storage > Connect Storage, or client.storage.create(params)
- Rendobar writes, reads, lists and deletes a test object before saving the connection
- Stored keys are encrypted with AES-256-GCM and no endpoint returns them
- Rotate: Replace Keys, or client.storage.update(id, { credentials }). The connection id stays the same

### Delivery results

- deliveries[] on GET /jobs/{id}: storageId, status (pending, delivered, failed), path, url, reason, renamed
- Webhooks: job.delivery_succeeded, job.delivery_failed, job.deliveries_settled
- Retry: POST /jobs/{id}/deliveries/retry or client.jobs.retryDeliveries(id)

## Questions

### Which S3-compatible providers work with Rendobar?

Any service that implements the S3 API on an https endpoint with a public host, such as MinIO, Wasabi, Backblaze B2 and Hetzner Object Storage. A server reachable only on a private network can't be connected.

### When should I turn on path-style URLs?

When your provider addresses buckets as endpoint/bucket/key instead of bucket.endpoint/key. If the access checks fail with a signature or bucket error and the keys are correct, try the other setting.

### What permissions does the S3-compatible key need?

Read and write on objects in the bucket. Delete isn't needed, and without it the empty test object stays at .rendobar/probe-<uuid> for you to remove. List only matters for browsing the bucket from the dashboard.

### Why is Name conflicts fixed to Replace on my bucket?

When you connect, Rendobar checks whether the endpoint refuses to overwrite an existing object. If it doesn't, Keep both can't work, so the setting is fixed to Replace. Add `{job_id}` to the output path to keep every output.

## Resources

- [Docs](https://rendobar.com/docs/storage/s3-compatible): The fields, path-style URLs and behavior that depends on the provider.
- [Output paths](https://rendobar.com/docs/storage): How templates, folders and Keep both decide where each output lands.
- [TypeScript SDK](https://rendobar.com/docs/sdk): client.storage.create and the other storage methods used above.
- [S3 URL styles](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html): The two S3 addressing styles the Path-style URLs setting picks between.

## More

- [Run FFmpeg commands through the API](https://rendobar.com/ffmpeg/)