/// CONNECT A PROVIDER / MINIO
MinIO
MinIO is S3-compatible and usually self-hosted, so you connect it as an access-key Fleet pointed at your own endpoint URL. storafleet uses path-style addressing, which is what most MinIO deployments expect.
Don't have a deployed MinIO yet? Deploy MinIO →
What you need
- Your MinIO endpoint URL — the address clients use to reach the server, for example
https://minio.internal.example.comor a host and port likehttps://10.0.0.5:9000. - An Access Key and Secret Key. Create a dedicated MinIO user (or service account) scoped to the bucket rather than using the root credentials.
- The bucket name and, if your deployment uses one, a region label.
Connect the Fleet
From the Fleet page, click Create Fleet and pick Access Keys. Then:
- Enter a display name, the bucket name, and a region label if you use one.
- Paste the Access Key and Secret Key.
- Set the endpoint to your MinIO URL. storafleet uses path-style addressing, so the bucket goes in the request path.
- Click Connect Fleet.
Private certificates
If your MinIO is behind a self-signed certificate or one issued by a private CA, paste the CA or certificate PEM bundle when connecting the Fleet. storafleet trusts that bundle for this endpoint specifically — it never disables TLS verification globally, so every other connection keeps full certificate validation.
Paste the full PEM chain (the leaf and any intermediates, up to the trusted root). If MinIO is fronted by a reverse proxy, use the proxy's certificate chain, since that is what storafleet connects to.
Object Lock
MinIO supports Object Lock, but it must be enabled when the bucket is created — it cannot be turned on for an existing bucket. If you need retention or legal-hold features, create a new bucket with Object Lock enabled and connect that one.
The endpoint URL must be reachable from storafleet. For an on-prem MinIO, that means it has to be accessible at the address you provide, not only inside your private network.