PBM-1631 Documented the minio storage type

docs/details/endpoint-map.md

@@ -0,0 +1,61 @@
+# Multiple endpoints to the same storage
+
+!!! admonition "Version added: [2.8.0](../release-notes/2.8.0.md)" 
+
+In environments where `pbm-agents` run on servers that are distributed across several data centers, accessing the same remote backup storage can become challenging. This can be due to complex network configurations or strict policies that prevent direct connections to the outside world. As a result, `pbm-agents` can't use the same URL to reach the storage, which is necessary for Percona Backup for MongoDB to work properly.
+
+To address these challenges, you can configure custom endpoint URLs for specific nodes in the PBM configuration. This allows all `pbm-agents` to access the same storage while respecting the network settings of their data centers.
+
+The supported storage types are: 
+
+* AWS S3 
+* MinIO and S3-compatible storage services 
+* Microsoft Azure Blob storage 
+
+Here's the example of the configuration file with the endpoint map:
+
+=== ":fontawesome-brands-amazon: AWS S3"
+
+    ```yaml
+    storage:
+        type: s3
+        s3:
+          endpointUrl: http://S3:9000
+          endpointUrlMap:
+            "node01:27017": "did.socf.s3.com"
+            "node03:27017": "https://example.aws.s3.com"
+          ...
+    ```
+
+=== ":simple-minio: MinIO and S3-compatible storage"
+
+    ```yaml
+    storage:
+        type: minio
+        minio:
+          endpoint: localhost:9100
+          endpointMap:
+            "node01:27017": "did.socf.s3.com"
+            "node03:27017": "https://example.min.io"
+          ...
+    ```
+
+=== ":material-microsoft-azure: Microsoft Azure Blob storage"
+
+    ```yaml
+    storage:
+        type: azure
+        azure:
+          endpointUrl: https://myaccount.blob.core.windows.net
+          endpointUrlMap:
+            "node01:27017": "did.socf.blob.core.windows.net"
+            "node03:27017": "https://example.azure.blob.core.windows.net"
+          ...
+    ```
+
+
+You can define the specific nodes for the `endpointUrlMap` parameter for AWS S3 and Azure or for the `endpointMap` for MinIO and S3-compatible storage. Not listed nodes use the endpoint defined for the `endpointUrl` / `endpoint` parameter. 
+
+For the solution to work, you should also have the mapping mechanism in place. This mechanism should be able to map the custom endpoints to the main endpoint URL of the storage, routing the requests from `pbm-agents` to the storage and back seamlessly.
+
+With this ability to control the endpoints for `pbm-agents` to reach the same storage, you reduce the administrative overhead on PBM configuration and ensure its proper functioning. 

docs/details/minio.md

@@ -0,0 +1,133 @@
+# MinIO and S3-compatible storage
+
+Percona Backup for MongoDB (PBM) works with both AWS S3 and other S3-compatible storage services. We test S3-compatible storages with PBM using [MinIO :octicons-link-external-16:](https://min.io/)
+
+This document provides an overview of MinIO as the closest S3-compatible storage. To use the native AWS S3 service, see [AWS S3 storage](s3-storage.md).
+
+[Configuration example :material-arrow-down:](#configuration-example){.md-button}
+
+## Bucket creation
+
+1. Install a [MinIO client :octicons-link-external-16:](https://min.io/docs/minio/linux/reference/minio-mc.html#install-mc). After the installation, the `mc` is available for you.
+
+2. Configure the `mc` command line tool with a MinIO Server
+
+    ```{.bash data-prompt="$"}
+    $ mc alias set myminio http://127.0.0.1:9000 MINIO_ACCESS_KEY MINIO_SECRET_KEY
+    ```
+
+3. Create a bucket
+
+    ```{.bash data-prompt="$"}
+    $ mc mb myminio/my-minio-bucket
+    ```
+
+4. Verify the bucket creation
+
+   ```{.bash data-prompt="$"}
+   $ mc ls myminio
+   ```
+
+After the bucket is created, apply the proper [permissions for PBM to use the bucket](storage-configuration.md#permissions-setup).
+
+## Configuration example
+
+!!! important
+
+    Percona Backup for MongoDB (PBM) needs its own dedicated S3 bucket exclusively for backup-related files. Ensure that this [bucket is created](#storage-bucket-creation) and managed solely by PBM.
+
+This is the example for the basic configuration of MinIO and other S3-compatible storages in Percona Backup for MongoDB. You can find [the configuration file template :octicons-link-external-16:](https://github.com/percona/percona-backup-mongodb/blob/v{{release}}/packaging/conf/pbm-conf-reference.yml) and uncomment the required fields.
+
+```yaml
+storage:
+  type: minio
+  minio:
+    endpoint: localhost:9100
+    region: us-east-1
+    bucket: pbm-example
+    prefix: data/pbm/test
+    credentials:
+      access-key-id: <your-access-key-id-here>
+      secret-access-key: <your-secret-key-here>
+```
+
+For the description of configuration options, see [Configuration file options](../reference/configuration-options.md).
+
+## Fine-tune storage configuration
+
+The following sections describe how you can fine-tune your storage configuration: 
+
+* [debug logging](#debug-logging) 
+* [upload retries](#upload-retries) 
+* [data upload to storage with self-signed TLS certificates](#data-upload-to-storage-with-self-signed-tls-certificates)  
+* [multiple endpoints to the same S3 storage](endpoint-map.md) 
+
+### Debug logging
+
+You can enable debug logging for different types of S3 requests in Percona Backup for MongoDB. Percona Backup for MongoDB prints S3 log messages in the `pbm logs` output so that you can debug and diagnose S3 request issues or failures.
+
+To enable debug logging, set the `storage.minio.debugTrace` option in Percona Backup for MongoDB configuration. This instructs PBM to also print HTTP trace from the S3 storage in the logs.
+
+## Upload retries 
+
+You can set up the number of attempts for Percona Backup for MongoDB to upload data to S3 storage as well as the min and max time to wait for the next retry. Set the `storage.minio.retryer.numMaxRetries` option in Percona Backup for MongoDB configuration.
+
+```yaml
+retryer:
+  numMaxRetries: 3
+```
+
+This upload retry increases the chances of data upload completion in cases of unstable connection.
+
+## Data upload to storage with self-signed TLS certificates
+
+Percona Backup for MongoDB supports data upload to S3-compatible storage service over HTTPS with a self-signed or a private CA certificate. This feature is especially important when you use services like MinIO, Ceph, or internal S3 gateways that don't use certificates signed by public Certificate Authorities (CAs).
+
+Providing a whole chain of certificates is recommended to ensure the connection is legit. The `SSL_CERT_FILE` environment variable specifies the path to a custom certificate chain file in PEM-format that PBM uses to validate TLS/SSL connection. 
+
+### Usage example
+
+Let's assume that your custom CA certificate is at `/etc/ssl/minio-ca.crt` path and your S3 endpoint is `https://minio.internal.local:9000`. To use self-issued TLS certificates, do the following:
+
+1. Ensure the cert file is in PEM format. Use the following command to check it:
+
+    ```bash
+    cat /etc/ssl/minio-ca.crt
+    ```
+
+    ??? example "Sample output"
+
+
+        ```{text .no-copy}
+        -----BEGIN CERTIFICATE-----
+        MIIC+TCCAeGgAwIBAgIJANH3WljB...
+        -----END CERTIFICATE-----
+        ```
+
+2. Set the `SSL_CERT_FILE` environment variable to that file's path on each host where `pbm-agent` and PBM CLI are running:
+
+    ```{.bash data-prompt="$"}
+    $ export SSL_CERT_FILE=/etc/ssl/minio-ca.crt
+    ```
+
+    If this variable isn't set, PBM uses the system root certificates.
+
+3. Restart `pbm-agent`:
+
+    ```{.bash data-prompt="$"}
+    $ sudo systemctl start pbm-agent
+    ```
+
+4. Verify that your custom certificate is recognized. Check PBM logs for successful S3 access. 
+
+
+Alternatively, you can disable the TLS verification of the S3 storage in Percona Backup for MongoDB configuration:
+
+```{.bash data-prompt="$"}
+$ pbm config --set storage.minio.insecureSkipTLSVerify=True
+```
+
+!!! warning 
+
+    Use this option with caution as it might leave a hole for man-in-the-middle attacks.
+