Software Checklist

Use the following checklist when planning the software configuration for a production, distributed MinIO deployment.

MinIO Pre-requisites

	Servers running a Linux operating system with a 5.x+ kernel, such as Red Hat Enterprise Linux (RHEL) 9 or Ubuntu LTS 20.04+
	A method to synchronize time servers across nodes, such as with `ntp`, `timedatectl` or `timesyncd`. The method to use varies by operating system. Check with your operating system’s documentation for how to synchronize time with a time server.
	System administrator access to the remote servers
	A management tool for distributed systems, such as Ansible, Terraform, or Kubernetes for orchestrated environments. Kubernetes infrastructures should use the MinIO Operator for best results.
	Load balancer to handle routing of requests (for example, NGINX)
	Prometheus / Grafana setup for monitoring and metrics
	(optional) `mc` installed on the local host system

Install the MinIO server binary across all nodes, ensuring that each node uses the same version of that binary.

	(optional) Create an `mc alias` for each server with `mc alias set` from your local machine for command line access to work with the MinIO deployment from a local machine
	Configure Bucket replication to duplicate contents of a bucket to another bucket location
	Configure Site replication to synchronize contents of multiple dispersed data center locations
	Configure Object retention rules with lifecycle management to manage when objects should expire
	Configure Object storage level rules with tiering to move objects between hot, warm, and cold storage and maximize storage cost efficiencies

Enabling this requires MinIO support.