fixup

docs/Usage.md

@@ -38,7 +38,7 @@ Refer to the quick start guide in the [README](../README.md#quickstart-guide) fo
    - S3 endpoint (and IAM endpoint, if different)
    - Region
    - Access Key ID & Secret Key
-   - `tlsCert`, if using HTTPS
+   - `tlsCert`, if needed. COSI driver uses the the AWS setting `InsecureSkipVerify` for HTTPs endpoints if not provided.
 
 3. **Create a Kubernetes Secret (by the Kubernetes Administrator)**
 
@@ -67,6 +67,7 @@ Refer to the quick start guide in the [README](../README.md#quickstart-guide) fo
    > [!NOTE]
    > Update `<ACCESS_KEY_ID>`, `<SECRET_ACCESS_KEY>`, `<S3_ENDPOINT>`, `<REGION>`, with valid values for your environment. If your endpoint does not require a TLS cert, you can remove it. Similarly, add IAM endpoint with `iamEndpoint` if its different from S3 endpoint otherwise remove it.
    > If using TLS cert, include the certificate content (PEM-encoded) in the stringData section of the Secret. Use a multi-line block scalar (|-) in YAML so that the certificate (with newlines) is preserved correctly.
+   > For HTTPS endpoint if not using TLS certificate, COSI driver will use the `InsecureSkipVerify` flag.
 
 ---