Object Storage MinIO

Adds MinIO, and any other S3-compatible endpoint, to the Object Storage extension.

What you can do

• Connect to a MinIO or S3-compatible server by host and port, over HTTP or HTTPS.
• Browse your buckets and objects from the Object Storage panel.
• Download an object into your workspace.
• Upload a workspace file back to a bucket.
• Work with on-prem deployments that have no wildcard DNS, since path-style addressing is on by default.

Getting started

Open Object Storage from the activity bar, click + and choose MinIO / S3-compatible. Give the connection a name and fill in the form:

• Endpoint is host:port, for example minio.corp.local:9000. A full https:// URL also works.
• Access key and Secret key are your credentials.
• Leave Use HTTPS off for a plain-HTTP on-prem deployment.
• Keep Path-style addressing on unless your server has wildcard DNS.
• Region is optional. MinIO ignores it, but the S3 protocol needs one, so it defaults to us-east-1.
• Default bucket is optional and names the bucket to open first.

When you edit an existing connection the secret field stays blank, and leaving it empty keeps the stored key.

Requirements

• The Object Storage extension, which draws the panel. This one has no panel of its own.
• The Secrets extension, which holds the access and secret keys.
• The desktop app. Connections are not available in the browser.
• Node.js 18 or later. If node is not on your PATH, or the default port clashes with something on your machine, change them in the extension's settings.

Good to know

• Your keys are handed to Secrets and land in whichever store you use there, never in a workspace file. If the store will not give a key back, the connection tells you to re-enter it.
• An interrupted download never leaves a half-written file behind.
• When an AI assistant or a flow deletes an object, the delete goes through the approval rules.