Connect an S3-compatible bucket

Connect a bucket on any service that implements the Amazon S3 API, such as MinIO, Backblaze B2, Wasabi, or Hetzner Object Storage. For how connections work across providers, see storage connections.

Prerequisites

From your provider, you need:

Value	Where it comes from
Endpoint	The provider’s S3 API URL. It must use `https` and a public host
Region	The region your provider’s documentation gives for S3 requests
Bucket name	An existing bucket, or a name for a new one
Access key ID and secret access key	A key that can read and write objects in the bucket

The key does not need permission to delete objects. Listing objects is needed only to browse the bucket from the dashboard.

1. Connect the bucket

In Storage, select Connect Storage, then S3-compatible.
Enter the Endpoint, Region, and Bucket.
Set Path-style URLs to match your provider. See Path-style URLs.
Enter the Access Key ID and Secret Access Key.
(Optional) Under More options, change the ID or set a public URL.
Select Connect.

Rendobar runs its access checks and saves the connection only if they pass. If the bucket does not exist, the dialog offers Create the bucket and connect.

2. Use the bucket in a job

Put an object in inputs to read it, and the connection in destinations to write the output:

import { createClient, outputUrl } from "@rendobar/sdk";

const client = createClient({
  apiKey: process.env.RENDOBAR_API_KEY,
});

const job = await client.jobs.run({
  type: "ffmpeg",
  inputs: { source: "storage://demo-bucket/raw/clip.mp4" },
  params: {
    command: "ffmpeg -i source -vf scale=1280:-2 out.mp4",
  },
  destinations: ["storage://demo-bucket/exports"],
});

console.log(outputUrl(job));
console.log(job.deliveries);

curl https://api.rendobar.com/jobs \
  -H "Authorization: Bearer $RENDOBAR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "ffmpeg",
    "inputs": { "source": "storage://demo-bucket/raw/clip.mp4" },
    "params": {
      "command": "ffmpeg -i source -vf scale=1280:-2 out.mp4"
    },
    "destinations": ["storage://demo-bucket/exports"]
  }'

With the default output path, this writes exports/clip.mp4. Delivery finishes after the job, so job.deliveries can still show pending when run returns. To change how outputs are named, see delivery settings. If a delivery fails, see delivery errors.

Path-style URLs

Path-style URLs decides where the bucket name goes in each request. Use the style your provider documents.

Setting	Request URL
On	`https://<endpoint>/<bucket>/<key>`
Off	`https://<bucket>.<endpoint-host>/<key>`

If the access checks fail with a signature or bucket error and the keys are correct, try the other setting.

Behavior that depends on the provider

Name conflicts. When you connect, Rendobar checks whether the endpoint refuses to overwrite an existing object. If it does not, Name conflicts is fixed to Replace, and an output with the same path replaces the existing object. To keep every output, add {job_id} to the output path. Deletes. A key without delete permission works. The empty test object from the access checks then stays in the bucket at .rendobar/probe-<uuid>, and you can delete it. Public URLs. Set your provider’s public or CDN domain as the connection’s public URL, so deliveries return links on that domain.

How do I revoke access?

Delete or deactivate the access key in your provider’s console. The connection stops working immediately. Deleting the connection in Rendobar removes the stored key, but does not invalidate it.

Next steps

Storage connections

Connection ids, delivery settings, credentials, and error codes.

Jobs

Where inputs and destinations appear in the job payload.

SDK

Submit the job above in TypeScript.

Webhooks

Receive an event when a job completes.

Getting Started

Concepts

Storage

Jobs

Automation

Developer tools

Support

Connect an S3-compatible bucket

Prerequisites

1. Connect the bucket

2. Use the bucket in a job

Path-style URLs

Behavior that depends on the provider

How do I revoke access?

Next steps

Storage connections

Jobs

SDK

Webhooks

​Prerequisites

​1. Connect the bucket

​2. Use the bucket in a job

​Path-style URLs

​Behavior that depends on the provider

​How do I revoke access?

​Next steps

Storage connections

Jobs

SDK

Webhooks

Prerequisites

1. Connect the bucket

2. Use the bucket in a job

Path-style URLs

Behavior that depends on the provider

How do I revoke access?

Next steps