StorafleetStorafleet

/// CONNECT A PROVIDER / RABATA

Rabata

Rabata is S3-compatible and authenticates with an Access Key ID and Secret Access Key. It uses path-style addressing and per-region endpoints.

Don't have a bucket yet? Create one first →

What you need

  • An Access Key ID and Secret Access Key from the Rabata dashboard.
  • The bucket name and the region (one of us-east-1, eu-west-1, eu-west-2).

Create API keys

  1. In the Rabata dashboard, go to Access Keys.
  2. Click Create and copy the Access Key ID and Secret Access Key.

Endpoint & region

https://s3.<REGION>.rabata.io — for example https://s3.us-east-1.rabata.io. Regions are us-east-1, eu-west-1, and eu-west-2. Set the region to match; Rabata uses path-style addressing.

Connect the Fleet

  1. From the Fleet page, click Create Fleet and pick Access Keys; enter a name, the bucket name, and the region.
  2. Paste the Access Key ID and Secret Access Key.
  3. Set the endpoint to https://s3.<REGION>.rabata.io and connect.

Supported features

Rabata supports Object Lock (Compliance mode) and the versioning it implies. Other bucket-configuration APIs are undocumented and treated conservatively — lifecycle, CORS, bucket policy, object tags, and storage classes are not offered.

Rabata does not support S3 server-side copy, so storafleet migrations to and from Rabata stream through the migration engine rather than copying in place (the same as Storj). Correctness is unaffected; large copies are just slower.