In this document we will walk you through the configuration files of MinIO Client.
MinIO Client configurations are stored in file name .mc. It is a hidden file which resides on user's home directory.
This how the structure of the directory looks like:
tree ~/.mc
/home/supernova/.mc
├── config.json
├── session
└── share
2 directories, 5 files
session directory keeps metadata information of all incomplete upload or mirror. You can run mc session list to list the same.
config.json is the configuration file for MinIO Client, it gets generated after you install and start MinIO. All the credentials, endpoint information we add via mc alias are stored/modified here.
cat config.json
{
"version": "10",
"aliases": {
"XL": {
"url": "http://127.0.0.1:9000",
"accessKey": "YI7S1CKXB76RGOGT6R8W",
"secretKey": "FJ9PWUVNXGPfiI72WMRFepN3LsFgW3MjsxSALroV",
"api": "S3v4",
"path": "auto"
},
"fs": {
"url": "http://127.0.0.1:9000",
"accessKey": "YI7S1CKXB76RGOGT6R8W",
"secretKey": "FJ9PWUVNXGPfiI72WMRFepN3LsFgW3MjsxSALroV",
"api": "S3v4",
"path": "auto"
},
"gcs": {
"url": "https://storage.googleapis.com",
"accessKey": "YOUR-ACCESS-KEY-HERE",
"secretKey": "YOUR-SECRET-KEY-HERE",
"api": "S3v2",
"path": "auto"
},
"play": {
"url": "https://play.min.io",
"accessKey": "Q3AM3UQ867SPQQA43P2F",
"secretKey": "zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG",
"api": "S3v4",
"path": "auto"
},
"s3": {
"url": "https://s3.amazonaws.com",
"accessKey": "YOUR-ACCESS-KEY-HERE",
"secretKey": "YOUR-SECRET-KEY-HERE",
"api": "S3v4",
"path": "auto"
},
"ibm": {
"url": "https://s3.YOUR-REGION.cloud-object-storage.appdomain.cloud",
"accessKey": "YOUR-HMAC-ACCESS-KEY-ID",
"secretKey": "YOUR-HMAC-SECRET-ACCESS-KEY",
"api": "S3v4",
"path": "auto"
}
}
}
version tells the version of the file.
aliases stores authentication credentials which will be used by MinIO Client.
This file keeps previous config file version details.
share directory keeps metadata information of all upload and download URL for objects which is used by MinIO client mc share command.