> ## Documentation Index
> Fetch the complete documentation index at: https://rendobar.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Keep the API key in an env var (RENDOBAR_API_KEY), never in chat or committed code.
> Job types change, so fetch the live catalog from GET https://api.rendobar.com/jobs/types rather than relying on memory.
> The full integration prompt for coding agents is at https://rendobar.com/prompts/integrate.md.
# Connect an S3-compatible bucket
> Connect a bucket on any S3-compatible service, such as MinIO, Backblaze B2 or Wasabi, so Rendobar jobs can read files from it and write outputs back.
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](/docs/storage).
## 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
1. In [**Storage**](https://app.rendobar.com/storage), select **Connect Storage**, then **S3-compatible**.
2. Enter the **Endpoint**, **Region**, and **Bucket**.
3. Set **Path-style URLs** to match your provider. See [Path-style URLs](#path-style-urls).
4. Enter the **Access Key ID** and **Secret Access Key**.
5. (Optional) Under **More options**, change the **ID** or set a public URL.
6. Select **Connect**.
Rendobar runs its [access checks](/docs/storage#connect-a-bucket) 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:
```typescript SDK theme={null}
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);
```
```bash cURL theme={null}
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](/docs/storage#delivery-settings). If a delivery fails, see [delivery errors](/docs/storage#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:////` |
| Off | `https://./` |
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](/docs/storage#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-`, and you can delete it.
**Public URLs.** Set your provider's public or CDN domain as the connection's [public URL](/docs/storage#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
Connection ids, delivery settings, credentials, and error codes.
Where `inputs` and `destinations` appear in the job payload.
Submit the job above in TypeScript.
Receive an event when a job completes.