@Test
        @DisplayName("Should throw configured exception on encode")
        void testConfiguredExceptionOnEncode() {
            testRequest.setThrowOnEncode(true);

            assertThrows(RuntimeException.class, () -> testRequest.encode(testBuffer, 0), "Should throw configured exception");
        }

        @Test
        @DisplayName("Should throw configured exception on size")

- Veeam requires TLS connections to the object storage.  This can be configured per <https://docs.min.io/community/minio-object-store/operations/network-encryption.html>
- The S3 bucket, Access Key and Secret Key have to be created before and outside of Veeam.

# How to configure Prometheus AlertManager

Alerting with prometheus is two step process. First we setup alerts in Prometheus server and then we need to send alerts to the AlertManager.

            list.addAll(boostFunctionList);
        });
    }

    /**
     * Builds the base query from the user's search string using the configured query parser.
     * This method parses the query string, processes it, and applies any additional customizations.
     *
     * @param queryContext the query context containing the query string

`images`. Whenever a JPEG image is created/overwritten, a new document is added or an existing document is updated in the Elasticsearch index configured above. When an existing object is deleted, the corresponding document is deleted from the index. Thus, the rows in the Elasticsearch index, reflect the `.jpg` objects in the `images` bucket.

To configure this bucket notification, we need the ARN printed by MinIO in the previous step. Additional information about ARN is available [here](htt...

    URLStreamHandler getUrlHandler();

    /**
     * Check if default credentials are configured
     *
     * @return whether default credentials are available
     */
    boolean hasDefaultCredentials();

    /**
     * Create a child context with default credentials
     *
     * @return a child context using the configured default credentials
     */
    CIFSContext withDefaultCredentials();

    /**

The MinIO TLS STS API can be configured via MinIO's standard configuration API (i.e. using `mc admin config set/get`). Further, it can be configured via the following environment variables:

```
mc admin config set myminio identity_tls --env
KEY:
identity_tls  enable X.509 TLS certificate SSO support

ARGS:

```
export MINIO_KMS_AUTO_ENCRYPTION=on
```

### Verify auto-encryption

> Note that auto-encryption only affects requests without S3 encryption headers. So, if a S3 client sends
> e.g. SSE-C headers, MinIO will encrypt the object with the key sent by the client and won't reach out to
> the configured KMS.

 * This filter processes requests with specific encoding requirements and converts
 * character encodings according to configured mapping rules.
 *
 * <p>The filter intercepts requests matching configured path patterns and
 * redirects them with proper character encoding applied to parameters.</p>
 */
public class EncodingFilter implements Filter {

minio server /data
```

NOTE: If `etcd` is configured with `Client-to-server authentication with HTTPS client certificates` then you need to use additional envs such as `MINIO_ETCD_CLIENT_CERT` pointing to path to `etcd-client.crt` and `MINIO_ETCD_CLIENT_CERT_KEY` path to `etcd-client.key` .

### 4. Test with MinIO STS API

Once etcd is configured, **any STS configuration** will work including Client Grants, Web Identity or AD/LDAP.