StorafleetStorafleet
Log inStart for free

/// CREATE A BUCKET / MINIO

Deploy MinIO

Want S3-compatible object storage that you fully control — running on-prem, at the edge, or inside an air-gapped network? MinIO is self-hosted: you stand up your own server, on your own hardware, speaking the S3 API. Deploy it, then connect it to storafleet as a Fleet right alongside your AWS, GCS, and DigitalOcean buckets.

Deploy MinIO

Screenshot: your running MinIO console (or the deploy output) so a first-timer knows what a healthy console looks like.

For a quick evaluation, run a single node from a container. This is for local development and testing only — it provides no high availability or erasure coding. The S3 API listens on port 9000 and the web Console on port 9001:

  • docker run -p 9000:9000 -p 9001:9001 -v ~/minio/data:/data -e MINIO_ROOT_USER=admin -e MINIO_ROOT_PASSWORD="a-long-random-secret" quay.io/minio/minio server /data --console-address ":9001"
  • Open the Console at http://localhost:9001 and sign in with the root user and password you set above. If you omit them, MinIO defaults to minioadmin / minioadmin — never leave those defaults in place.

For a real deployment — multiple nodes, multiple drives, erasure coding, and high availability — follow MinIO's official guide: Deploy and Manage MinIO (the single-node container reference is here).

Create an access key

Screenshot: the provider's key / secret confirmation screen — copy both values now (the secret is often shown only once).

Don't hand storafleet your root credentials. Create a dedicated access key (an access key ID + secret) so you can scope and rotate it independently. Two ways:

  • Console — in the MinIO Console, go to Access Keys → Create access key. Copy the Access Key and Secret Key shown — the secret is only displayed once.
  • mc (the MinIO Client) — point an alias at your server with mc alias set myminio http://localhost:9000 ADMIN_USER ADMIN_PASSWORD, then create a key with mc admin accesskey create myminio (omit the values to have MinIO auto-generate them). See mc admin accesskey.

Create a bucket

Screenshot: the create-bucket dialog — the name here becomes the Fleet's bucket.

Create the bucket storafleet will manage as a Fleet:

  • Console — go to Buckets → Create Bucket, give it a name, and (recommended) enable versioning.
  • mc — run mc mb myminio/my-bucket (add --with-versioning to enable versioning). See mc mb.

Endpoint & TLS

MinIO serves the S3 API on port 9000 by default, so your endpoint looks like https://minio.your-domain.com:9000 (or whatever host/port you expose). This is the endpoint you'll paste into the Create Fleet wizard. Enable TLS so traffic is encrypted in transit — drop your public.crt and private.key into MinIO's certs directory as described in Enable TLS for MinIO.

Using a self-signed certificate or one issued by a private/internal CA? You don't have to disable TLS. When you connect the Fleet, paste your CA's PEM certificate into storafleet so it trusts your endpoint — TLS stays on, and verification still happens against your own CA.

Connect it to storafleet

Screenshot: Storafleet's Create Fleet wizard with this provider selected and the endpoint + keys filled in — the step that unsticks a first-timer.

With your server up, a bucket created, and an access key in hand, head to Connect MinIO — choose Access Keys in the Create Fleet wizard, enter your key pair and the custom endpoint, and paste your CA PEM if you're on a private cert. Your MinIO bucket then lives in the same workspace as your cloud Fleets.

Need to move objects between MinIO and a cloud bucket — or the other way around? See the Migration guide.

PreviousWasabi
NextDigitalOcean Spaces