Service: MinIO - EyevinnOSC/community GitHub Wiki

MinIO

MinIO (serviceId minio-minio) is an S3-compatible object storage service, used for managing buckets that can be accessed with AWS S3 compatible clients and SDKs. In Eyevinn Open Source Cloud (OSC) it is a long-running service instance with up to 50 GiB of storage per instance. License: AGPL-3.0.

What it can do

  • Store objects in buckets through an S3-compatible API, usable with the AWS CLI, the MinIO client mc and S3 SDKs.
  • Serve objects over HTTPS, with presigned URLs or anonymous read-only access to a bucket.
  • Act as origin for a CDN for public distribution.
  • Serve as storage for other OSC services and workloads such as analytics, machine learning and application data.

Creating an instance

Create the instance with create-service-instance using serviceId: "minio-minio" and a config object. The instance name must be alphanumeric and at most 20 characters. MinIO has no dependencies on other OSC services.

Store the admin password as a service secret first with create-service-secret (serviceId: "minio-minio") and reference it as {{secrets.NAME}}.

{
  "name": "guide",
  "RootUser": "<admin-user-name>",
  "RootPassword": "{{secrets.miniopwd}}"
}

Wait for the instance with wait-for-service-ready, then use describe-service-instance to get the URL. The URL, for example https://<tenant>-guide.minio-minio.auto.prod-se.osaas.io, is the S3 endpoint to use with clients.

Options

Option Required Type Meaning
name Yes string Name of the instance. Alphanumeric, at most 20 characters. It is part of the instance URL.
RootUser No string Admin user name. Used as the access key id (AWS_ACCESS_KEY_ID or S3_ACCESS_KEY_ID) when accessing buckets with an S3 client or SDK.
RootPassword No string, sensitive Admin password. Used as the secret access key (AWS_SECRET_ACCESS_KEY or S3_SECRET_ACCESS_KEY) with an S3 client or SDK. Store it as a secret and pass {{secrets.NAME}}.

Use a strong password and a non-default user name. A {{secrets.NAME}} reference must be the whole field value, and changing a secret later does not restart a running instance.

Using the instance

Create a bucket

Install the MinIO client and create an alias for the instance, using the admin user and password from the instance. <tenant> is the id of your tenant:

% brew install minio/stable/mc
% mc alias set guide https://<tenant>-guide.minio-minio.auto.prod-se.osaas.io <RootUser> <RootPassword>
Added `guide` successfully.
% mc mb guide/tutorial

Access a bucket with an AWS S3 client

% export AWS_ACCESS_KEY_ID=<RootUser>
% export AWS_SECRET_ACCESS_KEY=<RootPassword>
% aws --endpoint-url https://<tenant>-guide.minio-minio.auto.prod-se.osaas.io \
  s3 cp images.jpeg s3://tutorial/
upload: ./images.jpeg to s3://tutorial/images.jpeg
% aws --endpoint-url https://<tenant>-guide.minio-minio.auto.prod-se.osaas.io s3 ls s3://tutorial/

HTTPS access with presigned URLs

% aws --endpoint-url=https://<tenant>-guide.minio-minio.auto.prod-se.osaas.io \
  s3 presign s3://tutorial/images.jpeg

See the AWS CLI documentation on how to set the expiration time of the link.

Public access to a bucket

Enable anonymous read-only access to a bucket with mc:

% mc anonymous set download guide/tutorial

The object is then reachable directly, for example https://<tenant>-guide.minio-minio.auto.prod-se.osaas.io/tutorial/images.jpeg.

Web acceleration with a CDN

For public distribution use a CDN. At your CDN provider set:

  • Origin: your MinIO instance hostname, for example <tenant>-guide.minio-minio.auto.prod-se.osaas.io
  • Protocol: HTTPS
  • Port: 443
  • Origin Host Header: the MinIO instance hostname

The Host header in the request to the origin must be the hostname of the MinIO instance, not the hostname in the viewer request. Consult your CDN provider documentation for how to configure this.

The OSC command line tool can set up a default CDN property in AWS CloudFront for a bucket (the OSC CLI is open source). For the bucket tutorial on the instance guide:

% npx @osaas/cli web cdn-create --origin-path=/tutorial minio-minio guide

Using MinIO with AI agents (MCP)

When an AI agent is connected to OSC via MCP, it can create buckets and list objects in your MinIO instances. By default the agent uses a shared instance named mcpstorage; you can target a specific named instance instead. Examples:

"Create a bucket called 'my-data' in my MinIO instance called 'production-storage'"

"List objects in the 'my-data' bucket in my MinIO instance named 'production-storage'"

Limitations

  • Storage is limited to 50 GiB per instance.
  • Removing a MinIO instance means that its data is lost.

Security best practices

  • Use strong, complex passwords and avoid default or easily guessable user names.
  • Avoid anonymous access (mc anonymous set download) unless necessary, and review content exposure regularly.
  • Always access MinIO over HTTPS; all OSC services provide it by default.
  • Use access policies to restrict what users or clients can do; MinIO supports fine-grained policies similar to AWS IAM.
  • Rotate the access keys periodically.

Resources

⚠️ **GitHub.com Fallback** ⚠️