feat: migrate to ROOT_USER/PASSWORD from ACCESS/SECRET_KEY (#11185)

docs/gateway/azure.md

@@ -5,15 +5,15 @@ MinIO Gateway adds Amazon S3 compatibility to Microsoft Azure Blob Storage.
 ### Using Docker
 ```
 docker run -p 9000:9000 --name azure-s3 \
- -e "MINIO_ACCESS_KEY=azurestorageaccountname" \
- -e "MINIO_SECRET_KEY=azurestorageaccountkey" \
+ -e "MINIO_ROOT_USER=azurestorageaccountname" \
+ -e "MINIO_ROOT_PASSWORD=azurestorageaccountkey" \
  minio/minio gateway azure
 ```
 
 ### Using Binary
 ```
-export MINIO_ACCESS_KEY=azureaccountname
-export MINIO_SECRET_KEY=azureaccountkey
+export MINIO_ROOT_USER=azureaccountname
+export MINIO_ROOT_PASSWORD=azureaccountkey
 minio gateway azure
 ```
 ## Test using MinIO Browser
@@ -38,7 +38,7 @@ mc ls myazure
 
 ### Use custom access/secret keys
 
-If you do not want to share the credentials of the Azure blob storage with your users/applications, you can set the original credentials in the shell environment using `AZURE_STORAGE_ACCOUNT` and `AZURE_STORAGE_KEY` variables and assign different access/secret keys to `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY`.
+If you do not want to share the credentials of the Azure blob storage with your users/applications, you can set the original credentials in the shell environment using `AZURE_STORAGE_ACCOUNT` and `AZURE_STORAGE_KEY` variables and assign different access/secret keys to `MINIO_ROOT_USER` and `MINIO_ROOT_PASSWORD`.
 
 ### Known limitations
 Gateway inherits the following Azure limitations:

docs/gateway/gcs.md

@@ -24,8 +24,8 @@ MinIO GCS Gateway allows you to access Google Cloud Storage (GCS) with Amazon S3
 docker run -p 9000:9000 --name gcs-s3 \
  -v /path/to/credentials.json:/credentials.json \
  -e "GOOGLE_APPLICATION_CREDENTIALS=/credentials.json" \
- -e "MINIO_ACCESS_KEY=minioaccountname" \
- -e "MINIO_SECRET_KEY=minioaccountkey" \
+ -e "MINIO_ROOT_USER=minioaccountname" \
+ -e "MINIO_ROOT_PASSWORD=minioaccountkey" \
  minio/minio gateway gcs yourprojectid
 ```
 
@@ -33,8 +33,8 @@ docker run -p 9000:9000 --name gcs-s3 \
 
 ```sh
 export GOOGLE_APPLICATION_CREDENTIALS=/path/to/credentials.json
-export MINIO_ACCESS_KEY=minioaccesskey
-export MINIO_SECRET_KEY=miniosecretkey
+export MINIO_ROOT_USER=minioaccesskey
+export MINIO_ROOT_PASSWORD=miniosecretkey
 minio gateway gcs yourprojectid
 ```
 

docs/gateway/hdfs.md

@@ -8,15 +8,15 @@ MinIO HDFS gateway adds Amazon S3 API support to Hadoop HDFS filesystem. Applica
 ### Using Binary
 Namenode information is obtained by reading `core-site.xml` automatically from your hadoop environment variables *$HADOOP_HOME*
 ```
-export MINIO_ACCESS_KEY=minio
-export MINIO_SECRET_KEY=minio123
+export MINIO_ROOT_USER=minio
+export MINIO_ROOT_PASSWORD=minio123
 minio gateway hdfs
 ```
 
 You can also override the namenode endpoint as shown below.
 ```
-export MINIO_ACCESS_KEY=minio
-export MINIO_SECRET_KEY=minio123
+export MINIO_ROOT_USER=minio
+export MINIO_ROOT_PASSWORD=minio123
 minio gateway hdfs hdfs://namenode:8200
 ```
 
@@ -25,8 +25,8 @@ Using docker is experimental, most Hadoop environments are not dockerized and ma
 ```
 docker run -p 9000:9000 \
  --name hdfs-s3 \
- -e "MINIO_ACCESS_KEY=minio" \
- -e "MINIO_SECRET_KEY=minio123" \
+ -e "MINIO_ROOT_USER=minio" \
+ -e "MINIO_ROOT_PASSWORD=minio123" \
  minio/minio gateway hdfs hdfs://namenode:8200
 ```
 

docs/gateway/nas.md

@@ -10,8 +10,8 @@ Please ensure to replace `/shared/nasvol` with actual mount path.
 
 ```
 docker run -p 9000:9000 --name nas-s3 \
- -e "MINIO_ACCESS_KEY=minio" \
- -e "MINIO_SECRET_KEY=minio123" \
+ -e "MINIO_ROOT_USER=minio" \
+ -e "MINIO_ROOT_PASSWORD=minio123" \
  -v /shared/nasvol:/container/vol \
  minio/minio gateway nas /container/vol
 ```
@@ -19,8 +19,8 @@ docker run -p 9000:9000 --name nas-s3 \
 ### Using Binary
 
 ```
-export MINIO_ACCESS_KEY=minio
-export MINIO_SECRET_KEY=minio123
+export MINIO_ROOT_USER=minio
+export MINIO_ROOT_PASSWORD=minio123
 minio gateway nas /shared/nasvol
 ```
 

docs/gateway/s3.md

@@ -8,25 +8,25 @@ As a prerequisite to run MinIO S3 gateway, you need valid AWS S3 access key and
 ### Using Docker
 ```
 docker run -p 9000:9000 --name minio-s3 \
- -e "MINIO_ACCESS_KEY=aws_s3_access_key" \
- -e "MINIO_SECRET_KEY=aws_s3_secret_key" \
+ -e "MINIO_ROOT_USER=aws_s3_access_key" \
+ -e "MINIO_ROOT_PASSWORD=aws_s3_secret_key" \
  minio/minio gateway s3
 ```
 
 ### Using Binary
 ```
-export MINIO_ACCESS_KEY=aws_s3_access_key
-export MINIO_SECRET_KEY=aws_s3_secret_key
+export MINIO_ROOT_USER=aws_s3_access_key
+export MINIO_ROOT_PASSWORD=aws_s3_secret_key
 minio gateway s3
 ```
 
 ### Using Binary in EC2
 Using IAM rotating credentials for AWS S3
 
-If you are using an S3 enabled IAM role on an EC2 instance for S3 access, MinIO will still require env vars MINIO_ACCESS_KEY and MINIO_SECRET_KEY to be set for its internal use. These may be set to any value which meets the length requirements. Access key length should be at least 3, and secret key length at least 8 characters.
+If you are using an S3 enabled IAM role on an EC2 instance for S3 access, MinIO will still require env vars MINIO_ROOT_USER and MINIO_ROOT_PASSWORD to be set for its internal use. These may be set to any value which meets the length requirements. Access key length should be at least 3, and secret key length at least 8 characters.
 ```
-export MINIO_ACCESS_KEY=custom_access_key
-export MINIO_SECRET_KEY=custom_secret_key
+export MINIO_ROOT_USER=custom_access_key
+export MINIO_ROOT_PASSWORD=custom_secret_key
 minio gateway s3
 ```
 
@@ -89,15 +89,15 @@ minio gateway s3
 ### Using Docker
 ```
 docker run -p 9000:9000 --name minio-s3 \
- -e "MINIO_ACCESS_KEY=access_key" \
- -e "MINIO_SECRET_KEY=secret_key" \
+ -e "MINIO_ROOT_USER=access_key" \
+ -e "MINIO_ROOT_PASSWORD=secret_key" \
  minio/minio gateway s3 https://s3_compatible_service_endpoint:port
 ```
 
 ### Using Binary
 ```
-export MINIO_ACCESS_KEY=access_key
-export MINIO_SECRET_KEY=secret_key
+export MINIO_ROOT_USER=access_key
+export MINIO_ROOT_PASSWORD=secret_key
 minio gateway s3 https://s3_compatible_service_endpoint:port
 ```