/// CONNECT A PROVIDER / EXABA (BETA)

Exaba (beta)

Exaba is a self-hosted, S3-compatible store, currently in pre-release beta. Point storafleet at your Exaba S3 endpoint with a key an admin issues for you.

What you need

• An Access Key ID and Secret Access Key from your admin.
• Your Exaba S3 endpoint URL — the operator sets this via S3_URL (default http://<host>:9000).
• The region — Exaba ignores it, so use us-east-1 (use whatever region the operator set, if any).

Get your credentials

1. Ask your admin to create a user in the Exaba admin GUI (port :9006).
2. The admin gives you the resulting Access Key ID and Secret Access Key.

Endpoint & region

Your endpoint is your Exaba S3 endpoint, which the operator sets via S3_URL (default http://<host>:9000). The region is ignored by Exaba, so use us-east-1 — or whatever region the operator configured.

Connect the Fleet

1. From the Fleet page, click Create Fleet and pick Access Keys.
2. Paste the Access Key ID and Secret Access Key from your admin.
3. Set your endpoint to your Exaba S3 endpoint (e.g. http://<host>:9000) and set the region to us-east-1.
4. Connect using path-style addressing. If your endpoint uses a private-CA or self-signed HTTPS certificate, provide a CA bundle so storafleet can verify the connection.

Supported features

Exaba supports versioning, lifecycle, bucket/IAM policies, and Object Lock (Veeam-validated). CORS, object tags, and storage-class transitions are not documented.