# Preface

Recently, I have been researching how to transfer more and more pictures of my articles to the storage location. I used to put them on Tencent's object storage, but after exceeding the 10G free quota, the cost became more and more exaggerated, and I couldn't afford it.

After a simple search, I found a very NICE self-built object storage service: MinIO

It uses the standard S3 protocol, so it can be compatible with all S3 infrastructure, and the original S3 users can also seamlessly migrate to MinIO.

Next, I will use docker to actually deploy it and make a record to share.

# Deploy using docker

If your system does not have docker installed, use the following command to install it:

apt install docker.io

After docker is installed, you can paste the following code to run directly, because docker is so simple.

docker run -d --name=minio --restart=always \
     -v 【Actual file storage location】:/data \
     -p 9000:9000 \
     -p 9001:9001 \
     -e MINIO_ROOT_USER=【User Name】\
     -e MINIO_ROOT_PASSWORD=【Password】\
     -e MINIO_SERVER_URL=【API Address】 \
     -e MINIO_BROWSER_REDIRECT_URL=【Management URL】 \
     minio/minio:latest server /data --console-address ":9001"

Replace the above Chinese with your actual parameters before running. MINIOSERVERURL is the API domain name. This API domain name will be called when logging in to create a file share through the web management domain name. If you don’t understand it very well, you can use the following default configuration:

docker run -d --name=minio --restart=always \
     -v /data:/data\
     -p 9000:9000 \
     -p 9001:9001 \
     -e MINIO_ROOT_USER=admin \
     -e MINIO_ROOT_PASSWORD=passwd\
     -e MINIO_SERVER_URL=https://share.tstrs.me\
     -e MINIO_BROWSER_REDIRECT_URL=https://drive.tstrs.me \
     minio/minio:latest server /data --console-address ":9001"

After running, you can open the server http://server_ip:9001 to access the background, the default account admin, the password passwd, create Buckets after logging in, and finally upload the file to use.

# Configure permissions

The default Buckets permission is private, so we can’t use it as a map bed. You need to modify the access policy to custom, and enter the following fields, remember to replace [Buckets name] with your actual Buckets name.

{
     "Version": "2012-10-17",
     "Statement": [
    {
   "Effect": "Allow",
   "Principal": {
  "AWS": [
"*"
  ]
   },
   "Action": [
  "s3:GetBucketLocation"
   ],
   "Resource": [
  "arn:aws:s3:::【Buckets name】"
   ]
    },
    {
   "Effect": "Allow",
   "Principal": {
  "AWS": [
"*"
  ]
   },
   "Action": [
  "s3:GetObject"
   ],
   "Resource": [
  "arn:aws:s3:::【Buckets name】/*"
   ]
    }
     ]
}