Getting Started

Silo is an independent, community-maintained fork of the open source MinIO server, published by PGSTY (Pigsty). It provides S3-compatible object storage with a web console. Silo is not affiliated with or endorsed by MinIO, Inc. The project describes itself as a maintained line of the MinIO server, with security fixes and the full web console. The version running on Eyevinn Open Source Cloud is RELEASE.2026-09-16T00-00-00Z, licensed under AGPL-3.0. If you want the original upstream build, see the MinIO service.

Prerequisites

Step 1: Store the root password as a secret

The root password is sensitive. Navigate to the Silo service and go to the "Service Secrets" tab. Click "New Secret" and create:

  • silorootpassword with a long random string as its value

Step 2: Create the Silo instance

Go to the "My silo" tab and click "Create silo". Fill in:

Option Description Example
Name Instance name (lowercase letters and digits) mystorage
RootUser Root/admin user name. Used as the S3 access key <access-key>
RootPassword Root password. Used as the S3 secret key {{secrets.silorootpassword}}

The instance gets a 50 GB persistent volume.

Step 3: Open the instance

When the instance shows as running, its URL is:

https://<tenant>-<name>.pgsty-silo.auto.prod-se.osaas.io

This URL is both the S3 endpoint and the base for the web console, which is at <URL>/ui/. The health endpoint <URL>/minio/health/live returns 200 when the server is up.

Note: right after the instance first reports ready, S3 requests can return 401 for a short while (about a minute was observed). Wait and retry.

Usage Example

Configure any S3-compatible client with these settings:

Setting Value
Endpoint URL https://<tenant>-<name>.pgsty-silo.auto.prod-se.osaas.io
Access key the RootUser value (<access-key>)
Secret key the RootPassword value (<secret-key>)
Region us-east-1
Addressing style path-style

Then, with your client, create a bucket (for example my-bucket), upload a file into it, and download it again to confirm the content matches. Requests without valid credentials, or with a wrong password, are rejected with HTTP 403.

Configuration

Option Required Description
Name Yes Instance name, lowercase letters and digits
RootUser Yes Root/admin user name, used as the S3 access key
RootPassword Yes Root password, used as the S3 secret key. Store as a service secret and reference it as {{secrets.<secret-name>}}

The root credentials are set only when the instance is created.

Limitations

  • Single node, single drive: Silo runs on one drive, so there is no redundancy. Data lives only on the 50 GB persistent volume. Keep an independent copy of important data. Data written before an instance restart was still readable after it.
  • Use path-style addressing. Virtual-hosted style (bucket as subdomain) is not available with this hostname pattern.
  • Console login with the root credentials in a browser was not tested (the console page loads at /ui/).
  • Only signed HTTP requests (SigV4) were tested. AWS CLI, mc/mcli, and SDK clients were not run.
  • Not tested: large uploads, multipart uploads, versioning, lifecycle rules, anonymous/public bucket policies, and IAM users and policies beyond the root user.
  • IP-based bucket policy conditions (aws:SourceIp) were not tested. Do not rely on them.
  • Changing RootUser or RootPassword after creation was not tested.
  • arm64 was not tested.

Resources