If you have updated your self-hosted MinIO server in the past few weeks and logged in to the web console, you were probably surprised: all that is left in the interface is browsing and creating buckets and uploading and downloading files. Managing users, policies, access keys, configuration and monitoring has disappeared. This isn’t a bug: MinIO deliberately removed these features from the AGPL-licensed community edition and moved them into its paid AIStor product.
Below we summarise exactly what happened, how you can keep managing the server from the command line, and what to consider if you have built on MinIO.
What changed in the MinIO web console?
The change arrived in the RELEASE.2025-05-24T17-08-30Z release (24 May). The built-in console was replaced by a new, “simplified” version through two updates merged on 9 and 21 May; the developers themselves marked the first one as a breaking change. According to the release notes:
- the embedded console is deprecated and has moved to the separate
object-browserproject; - logging in to the console with external identity providers (LDAP, OIDC) has been removed – this has also become part of AIStor;
- the STS APIs still work if someone wants to build their own interface;
- MinIO recommends that paying customers move to AIStor.
The server’s S3-compatible API and the admin API have not changed. In a GitHub issue where a user reported the “missing” administration section, MinIO’s co-founder confirmed that the interface was removed on purpose, but the admin APIs the interface used (madmin-go) and the mc command-line client remain, and no changes to them are planned for now.
How the community reacted
The reception was very negative. On GitHub and Reddit, many people wrote about it with disappointment, as a step backwards; several pointed out that critical comments had been deleted from the issues, and one commenter wrote that a multi-petabyte purchase had been halted because of it. The removal of OIDC login also hit those who had given developers access to the console through single sign-on (SSO). Shortly after the release, a community fork of the old console (OpenMaxIO) also appeared, but its long-term maintenance is still uncertain.
The move has a history: MinIO switched from Apache 2.0 to AGPLv3 in 2021, and in autumn 2024 it launched a commercial product called AIStor. We saw a similar change of direction with Red Hat’s source code access and after Broadcom’s acquisition of VMware: what is free depends on the vendor’s decision.
Administration with mc
The good news is that everything you used to click through in the console can be done with the mc client, and that can be scripted and version-controlled too. First, add the server as an alias:
mc alias set myminio https://s3.example.com ADMIN_KEY ADMIN_SECRET
mc admin info myminio
A user, a policy and an access key for an application:
mc admin user add myminio app-backup 'StrongPassword123'
mc admin policy create myminio backup-rw backup-rw.json
mc admin policy attach myminio backup-rw --user app-backup
mc admin accesskey create myminio app-backup
Buckets and lifecycle:
mc mb myminio/backups
mc version enable myminio/backups
mc quota set myminio/backups --size 500GiB
mc ilm rule add --expire-days 30 myminio/logs
For troubleshooting and monitoring:
mc admin trace myminio # live API calls
mc admin config get myminio identity_openid
mc admin prometheus generate myminio # Prometheus scrape configuration
It is worth keeping the policies in Git as JSON files, and putting the creation of users and buckets into a script or an Ansible task. That way the setup is reproducible and doesn’t depend on clicks in a web interface.
Should we stay on an older version?
If your team relies on the web interface, as a temporary measure you can pin the server to the last release with the full console, RELEASE.2025-04-22T22-12-26Z:
services:
minio:
image: quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z
command: server /data --console-address ":9001"
This only buys time, though: the old version doesn’t get security fixes, and an S3 endpoint is typically a service that is also exposed to the internet. We don’t recommend the latest tag in production anyway – this case shows why. Always refer to a specific release, and read the release notes before updating.
Alternatives for self-hosted S3 storage
If this move makes you rethink your use of MinIO, these open-source options are available:
| Solution | Licence | What is it good for? |
|---|---|---|
| Garage | AGPLv3 | Small, geographically distributed clusters on modest hardware; the 1.x series is stable |
| SeaweedFS | Apache 2.0 | Many small files, S3, file and FUSE access in one system |
| Ceph RGW | LGPL | Large storage with many nodes; a natural choice if you already run Ceph in a Proxmox VE cluster |
| Cloud object storage | – | AWS S3, Google Cloud Storage, OVHcloud Object Storage, if you don’t need your own hardware |
None of them is a drop-in replacement for MinIO in every S3 feature: support for versioning, object lock, replication and event notifications differs, so before switching, check what your applications use. We wrote about the cloud options in more detail in our article on Google Cloud Platform for small businesses.
What do we recommend?
- Don’t update blindly. Pin the version, and decide whether the team needs a web interface.
- Move all administration to
mc, and put the settings into code. This is good practice regardless of MinIO. - If you used OIDC or LDAP login in the console, plan its replacement (access keys, your own STS-based solution).
- Assess your exposure. If MinIO is only the backup target of one application, switching is simple; if many services depend on it, try the alternatives in a test environment before you decide.
We help with building and migrating S3-compatible storage and with choosing cloud alternatives; you can read about this on the Cloud and DevOps page.