Install and Deploy MinIO

MinIO is a software-defined high performance distributed object storage server. You can run MinIO on consumer or enterprise-grade hardware and a variety of operating systems and architectures.

MinIO supports three deployment topologies:

Single-Node Single-Drive (SNSD or “Standalone”)

A single MinIO server with a single storage volume or folder. SNSD deployment provides failover protections. Drive-level reliability and failover depends on the underlying storage volume.

SNSD deployments are best suited for evaluation and initial development of applications using MinIO for object storage.

SNSD deployments implement a zero-parity erasure coding backend and include support for the following erasure-coding dependent features:

Single-Node Multi-Drive (SNMD or “Standalone Multi-Drive”)

A single MinIO server with four or more storage volumes. SNMD deployments provide drive-level reliability and failover only.

Multi-Node Multi-Drive (MNMD or “Distributed”)

Multiple MinIO servers with at least four drives across all servers. The distributed MNMD topology supports production-grade object storage with drive and node-level availability and resiliency.

For tutorials on deploying or expanding a distributed MinIO deployment, see:

The following table compares the key functional differences between MinIO deployments:

Single-Node Single-Drive

Single-Node Multi-Drive

Multi-Node Multi-Drive

Site-to-Site Replication

Client-Side via mc mirror

Server-Side Replication

Server-Side Replication



Object Versioning

Object Versioning



Write-Once Read-Many Locking

Write-Once Read-Many Locking

High Availability / Redundancy

Drive Level Only (RAID and similar)

Drive Level only with Erasure Coding

Drive and Server-Level with Erasure Coding



Server Pool Expansion

Server Pool Expansion.

Site Replication

Site replication expands the features of bucket replication to include IAM, security tokens, service accounts, and bucket features the same across all sites.

Site replication links multiple MinIO deployments together and keeps the buckets, objects, and Identify and Access Management (IAM) settings in sync across all connected sites.

Each MinIO deployment (“peer site”) synchronizes the following changes across the other peer sites:

  • Creation, modification, and deletion of buckets and objects, including

  • Creation and deletion of IAM users, groups, policies, and policy mappings to users or groups (for LDAP users or groups)

  • Creation of Security Token Service (STS) credentials for session tokens verifiable from the local root credentials

  • Creation and deletion of service accounts (except those owned by the root user)

Site replication enables bucket versioning for all new and existing buckets on all replicated sites.

What Does Not Replicate?

Not everything replicates across sites.

MinIO deployments in a site replication configuration do not replicate the creation or modification of the following items:

Platform Support

MinIO provides builds of the MinIO server (minio) and the MinIO CLI (mc) for the following platforms.

  • Red Hat Enterprise Linux 8.5+ (including all binary-compatible RHEL alternatives)

  • Ubuntu 18.04+

MinIO provides builds for the following architectures:

  • AMD64

  • ARM64

  • PowerPC 64 LE

  • S390X

For unlisted platforms or architectures, please reach out to MinIO at for additional support and guidance. You can build MinIO from source and cross-compile for your platform and architecture combo. MinIO generally does not recommend source-based installations in production environments.