.. start-common-deploy-create-environment-file-single-drive Create an environment variable file at ``/etc/default/minio``. For Windows hosts, specify a Windows-style path similar to ``C:\minio\config``. The MinIO Server container can use this file as the source of all :ref:`environment variables `. The following example provides a starting environment file: .. code-block:: shell :class: copyable # MINIO_ROOT_USER and MINIO_ROOT_PASSWORD sets the root account for the MinIO server. # This user has unrestricted permissions to perform S3 and administrative API operations on any resource in the deployment. # Omit to use the default values 'minioadmin:minioadmin'. # MinIO recommends setting non-default values as a best practice, regardless of environment MINIO_ROOT_USER=myminioadmin MINIO_ROOT_PASSWORD=minio-secret-key-change-me # MINIO_VOLUMES sets the storage volume or path to use for the MinIO server. MINIO_VOLUMES="/mnt/data" # MINIO_OPTS sets any additional commandline options to pass to the MinIO server. # For example, `--console-address :9001` sets the MinIO Console listen port MINIO_OPTS="--console-address :9001" Include any other environment variables as required for your deployment. .. end-common-deploy-create-environment-file-single-drive .. start-common-deploy-create-unique-root-credentials .. versionadded:: Server RELEASE.2024-03-03T17-50-39Z MinIO automatically generates unique root credentials if all of the following conditions are true: - :kes-docs:`KES ` Release 2024-03-01T18-06-46Z or later running - **Have not** defined: - ``MINIO_ROOT_USER`` variable - ``MINIO_ROOT_PASSWORD`` variable - **Have**: - set up KES with a :kes-docs:`supported KMS target <#supported-kms-targets>` - disabled root access with the :ref:`MinIO environment variable ` When those conditions are met at startup, MinIO uses the KMS to generate unique root credentials for the deployment using a `hash-based message authentication code (HMAC) `__. If MinIO generates such credentials, the key used to generate the credentials **must** remain the same *and* continue to exist. All data on the deployment is encrypted with this key! To rotate the generated root credentials, generate a new key in the KMS, then update the value of the :envvar:`MINIO_KMS_KES_KEY_NAME` with the new key. .. end-common-deploy-create-unique-root-credentials .. start-common-deploy-create-environment-file-multi-drive Create an environment variable file at ``/etc/default/minio``. For Windows hosts, specify a Windows-style path similar to ``C:\minio\config``. The MinIO Server container can use this file as the source of all :ref:`environment variables `. The following example provides a starting environment file: .. code-block:: shell :class: copyable # MINIO_ROOT_USER and MINIO_ROOT_PASSWORD sets the root account for the MinIO server. # This user has unrestricted permissions to perform S3 and administrative API operations on any resource in the deployment. # Omit to use the default values 'minioadmin:minioadmin'. # MinIO recommends setting non-default values as a best practice, regardless of environment. MINIO_ROOT_USER=myminioadmin MINIO_ROOT_PASSWORD=minio-secret-key-change-me # MINIO_VOLUMES sets the storage volumes or paths to use for the MinIO server. # The specified path uses MinIO expansion notation to denote a sequential series of drives between 1 and 4, inclusive. # All drives or paths included in the expanded drive list must exist *and* be empty or freshly formatted for MinIO to start successfully. MINIO_VOLUMES="/data-{1...4}" # MINIO_OPTS sets any additional commandline options to pass to the MinIO server. # For example, `--console-address :9001` sets the MinIO Console listen port MINIO_OPTS="--console-address :9001" Include any other environment variables as required for your local deployment. .. end-common-deploy-create-environment-file-multi-drive .. start-common-deploy-connect-to-minio-deployment .. tab-set:: .. tab-item:: MinIO Console You can access the MinIO Console by entering any of the hostnames or IP addresses from the MinIO server ``Console`` block in your preferred browser, such as http://localhost:9001. Log in with the :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD` configured in the environment file specified to the container. .. image:: /images/minio-console/console-bucket-none.png :width: 600px :alt: MinIO Console displaying Buckets view in a fresh installation :align: center You can use the MinIO Console for general administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration. Each MinIO server includes its own embedded MinIO Console. If your local host firewall permits external access to the Console port, other hosts on the same network can access the Console using the IP or hostname for your local host. .. tab-item:: MinIO CLI (mc) You can access the MinIO deployment over a Terminal or Shell using the :ref:`MinIO Client ` (:mc:`mc`). See :ref:`MinIO Client Installation Quickstart ` for instructions on installing :mc:`mc`. Create a new :mc:`alias ` corresponding to the MinIO deployment. Specify any of the hostnames or IP addresses from the MinIO Server ``API`` block, such as http://localhost:9000. .. code-block:: shell :class: copyable mc alias set http://localhost:9000 myminioadmin minio-secret-key-change-me Replace ``myminioadmin`` and ``minio-secret-key-change-me`` with the :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD` values in the environment file specified to the container. You can then interact with the container using any :mc:`mc` command. If your local host firewall permits external access to the MinIO S3 API port, other hosts on the same network can access the MinIO deployment using the IP or hostname for your local host. .. end-common-deploy-connect-to-minio-deployment