2020-03-24 22:51:06 +01:00
# MinIO Multi-Tenant Deployment Guide [![Slack](https://slack.min.io/slack?type=svg)](https://slack.min.io) [![Docker Pulls](https://img.shields.io/docker/pulls/minio/minio.svg?maxAge=604800)](https://hub.docker.com/r/minio/minio/)
2017-05-09 04:22:34 +02:00
2018-11-28 03:03:07 +01:00
This topic provides commands to set up different configurations of hosts, nodes, and drives. The examples provided here can be used as a starting point for other configurations.
2017-05-09 04:22:34 +02:00
2018-11-28 03:03:07 +01:00
1. [Standalone Deployment ](#standalone-deployment )
2. [Distributed Deployment ](#distributed-deployment )
3. [Cloud Scale Deployment ](#cloud-scale-deployment )
## <a name="standalone-deployment"></a>1. Standalone Deployment
2019-04-09 20:39:42 +02:00
To host multiple tenants on a single machine, run one MinIO Server per tenant with a dedicated HTTPS port, configuration, and data directory.
2018-11-28 03:03:07 +01:00
### 1.1 Host Multiple Tenants on a Single Drive
Use the following commands to host 3 tenants on a single drive:
2017-05-09 04:22:34 +02:00
```sh
2019-01-02 19:05:16 +01:00
minio server --address :9001 /data/tenant1
minio server --address :9002 /data/tenant2
minio server --address :9003 /data/tenant3
2017-05-09 04:22:34 +02:00
```
2017-06-29 20:41:21 +02:00
![Example-1 ](https://github.com/minio/minio/blob/master/docs/screenshots/Example-1.jpg?raw=true )
2017-05-09 04:22:34 +02:00
2018-11-28 03:03:07 +01:00
### 1.2 Host Multiple Tenants on Multiple Drives (Erasure Code)
Use the following commands to host 3 tenants on multiple drives:
2017-05-09 04:22:34 +02:00
```sh
2019-01-02 19:05:16 +01:00
minio server --address :9001 /disk1/data/tenant1 /disk2/data/tenant1 /disk3/data/tenant1 /disk4/data/tenant1
minio server --address :9002 /disk1/data/tenant2 /disk2/data/tenant2 /disk3/data/tenant2 /disk4/data/tenant2
minio server --address :9003 /disk1/data/tenant3 /disk2/data/tenant3 /disk3/data/tenant3 /disk4/data/tenant3
2017-05-09 04:22:34 +02:00
```
2018-11-28 03:03:07 +01:00
2017-06-29 20:41:21 +02:00
![Example-2 ](https://github.com/minio/minio/blob/master/docs/screenshots/Example-2.jpg?raw=true )
2017-05-09 04:22:34 +02:00
2018-11-28 03:03:07 +01:00
## <a name="distributed-deployment"></a>2. Distributed Deployment
2017-05-09 04:22:34 +02:00
2019-04-09 20:39:42 +02:00
To host multiple tenants in a distributed environment, run several distributed MinIO Server instances concurrently.
2017-05-09 04:22:34 +02:00
2018-11-28 03:03:07 +01:00
### 2.1 Host Multiple Tenants on Multiple Drives (Erasure Code)
Use the following commands to host 3 tenants on a 4-node distributed configuration:
2017-05-09 04:22:34 +02:00
```sh
export MINIO_ACCESS_KEY=< TENANT1_ACCESS_KEY >
export MINIO_SECRET_KEY=< TENANT1_SECRET_KEY >
2019-01-02 19:05:16 +01:00
minio server --address :9001 http://192.168.10.11/data/tenant1 http://192.168.10.12/data/tenant1 http://192.168.10.13/data/tenant1 http://192.168.10.14/data/tenant1
2017-05-09 04:22:34 +02:00
export MINIO_ACCESS_KEY=< TENANT2_ACCESS_KEY >
export MINIO_SECRET_KEY=< TENANT2_SECRET_KEY >
2019-01-02 19:05:16 +01:00
minio server --address :9002 http://192.168.10.11/data/tenant2 http://192.168.10.12/data/tenant2 http://192.168.10.13/data/tenant2 http://192.168.10.14/data/tenant2
2017-05-09 04:22:34 +02:00
export MINIO_ACCESS_KEY=< TENANT3_ACCESS_KEY >
export MINIO_SECRET_KEY=< TENANT3_SECRET_KEY >
2019-01-02 19:05:16 +01:00
minio server --address :9003 http://192.168.10.11/data/tenant3 http://192.168.10.12/data/tenant3 http://192.168.10.13/data/tenant3 http://192.168.10.14/data/tenant3
2017-05-09 04:22:34 +02:00
```
2018-11-28 03:03:07 +01:00
**Note:** Execute the commands on all 4 nodes.
2018-09-11 02:14:40 +02:00
2018-11-28 03:03:07 +01:00
![Example-3 ](https://github.com/minio/minio/blob/master/docs/screenshots/Example-3.jpg?raw=true )
2018-09-11 02:14:40 +02:00
2018-11-28 03:03:07 +01:00
**Note**: On distributed systems, credentials must be defined and exported using the `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` environment variables. If a domain is required, it must be specified by defining and exporting the `MINIO_DOMAIN` environment variable.
2017-05-09 04:22:34 +02:00
2018-11-28 03:03:07 +01:00
## <a name="cloud-scale-deployment"></a>Cloud Scale Deployment
2017-05-09 04:22:34 +02:00
2019-04-09 20:39:42 +02:00
A container orchestration platform (e.g. Kubernetes, DC/OS, or Docker Swarm) is recommended for large-scale, multi-tenant MinIO deployments. See the [MinIO Deployment Quickstart Guide ](https://docs.min.io/docs/minio-deployment-quickstart-guide ) to get started with MinIO on orchestration platforms.