The following instructions are for ОС Ubuntu Linux 20.04.
In this example, the virtual host name is “elma365vhost”, the user is “elma365user”, and the password is “SecretPassword”.
When configuring MinIO, set these data according to the security policies of your organization.
- Download the binary file of the MinIO server from the official website:
sudo wget https://dl.min.io/server/minio/release/linux-amd64/minio
- Make the file executable:
sudo chmod +x minio
- Move the file to /usr/local/bin, as the startup script will be searching for it in this directory:
sudo mv minio /usr/local/bin
- Create a new user:
sudo useradd -r minio-user -s /sbin/nologin
- Make “minio-user” the owner of the file:
sudo chown minio-user:minio-user /usr/local/bin/minio
- Create a directory where MinIO will store files:
sudo mkdir /usr/local/share/minio
- Make “minio-user” the owner of this directory:
sudo chown minio-user:minio-user /usr/local/share/minio
- Create a directory to store MinIO configuration files:
sudo mkdir /etc/minio
- Make “minio-user” the owner of the directory:
sudo chown minio-user:minio-user /etc/minio
- Using a text editor, create an environment file that can be used to change the default settings:
sudo nano /etc/default/minio
- Add the following variables to the file:
MINIO_REGION = "us-east-1"
MINIO_OPTS="-C /etc/minio --console-address :9001 --address :9000"
- MINIO_ROOT_USER sets the key you will use to access the user interface of the MinIO browser.
- MINIO_ROOT_PASSWORD sets the private key you will use to enter your credentials in the MinIO interface.
- MINIO_VOLUMES determines the directory in which files will be stored.
- MINIO_OPTS determines where and how the server will serve data (in this example, the MinIO server can be accessed from any external address).
- Save and close the file.
Create a systemd service for MinIO
- Download the official file of the MinIO service:
sudo curl -O https://raw.githubusercontent.com/minio/minio-service/master/linux-systemd/minio.service
- Check the contents of the minio.service file before using it (view such parameters as AssertFileIsExecutable and EnvironmentFile). Open it in a text editor:
sudo nano minio.service
- After viewing, move minio.service to the configuration directory systemd:
sudo mv minio.service /etc/systemd/system
- Reload systemd units:
sudo systemctl daemon-reload
- Start the MinIO service and make is start automatically at boot:
sudo systemctl enable --now minio
Install the MinIO Client Tool and create a bucket
- Download the binary file MinIO Client Tool from the official website:
sudo wget https://dl.min.io/client/mc/release/linux-amd64/mc
- Make the file executable:
sudo chmod +x mc
- Configure the connection to MinIO:
./mc alias set minio http://minio-server.your_domain:9000 elma365user SecretPassword
- Create a bucket:
./mc mb minio/s3elma365 --region=us-east-1
Connection to MinIO
Parameters for MinIO connection:
- address: <minio-server-address>:9000
- bucket: s3elma365
- region: us-east-1
- access key ID: elma365user
- secret access key: SecretPassword
- upload method: PUT
- enable SSL? No
To improve security, you can isolate the S3 server in the organization’s local network.
In this case, users will access it through a proxy server. You can enable a proxy server during installation or reconfiguration (if an external S3 was connected during installation) of ELMA365. To do that, when asked “Enable proxying connection to external S3 through ELMA365?”, answer “Yes”.
Important: to work with proxy without issues, make sure that the name of the container (bucket) in the S3 storage is “s3elma365”.
Found a typo? Highlight the text, press ctrl + enter and notify us