/// CONNECT A PROVIDER / CUSTOM S3-COMPATIBLE
Custom S3-compatible
If your storage speaks the S3 API, you can connect it even when it isn't one of the named providers — other clouds, edge providers, and on-prem gateways all work. You just need an endpoint URL and access keys.
What you need
- The endpoint URL for your S3-compatible service.
- An access key and secret for that service.
- The bucket name and, if the service 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 the service uses one.
- Paste the access key and secret.
- Set the endpoint to your service's URL. storafleet uses path-style addressing, so the bucket goes in the request path.
- Click Connect Fleet.
Capability defaults
For an unknown endpoint, storafleet uses conservative capability defaults: it shows the safe, common feature set that nearly every S3-compatible service supports, rather than assuming provider-specific extras are available. This keeps the connection reliable across implementations that vary in what they support.
If a provider you connect this way is one storafleet later recognizes natively, the named provider page will give you the most accurate feature set. Until then, the conservative defaults are the safe baseline.
Make sure the endpoint is reachable from storafleet and that the key has access to the bucket. Path-style addressing means the bucket name does not need to be part of the hostname.