This message was deleted.

Thanks. But it looks like the answer is No to my second question

Yes but it doesnt seems required

If you want to use a self-signed SSL certificate, you can specify AWS_CERT in the Kubernetes secret you provided to Longhorn. See the example in Set up a Local Testing Backupstore. It’s important to note that the certificate needs to be in PEM format, and must be its own CA. Or one must include a certificate chain that contains the CA certificate. To include multiple certificates, one can just concatenate the different certificates (PEM files).

Unless hostname checking is skipped when you provide a cert (haven't tried yet), then it's required for me. Unfortunately.

Can't you hack around a reverse proxy to present that cert?

As said, I'm talking to an S3-server that has a self-signed cert. But not only a self-signed cert.... It's a cert that contains no valid DNS-names or IP-sans. So the cert is basically invalid, from an x509 standpoint. .... Yeah, I could setup a proxy... Maybe.. Question is whether that's faster than getting the right team in my corp to actually present a sane cert on the s3 gateway 😄 will try both, see what comes first... thanks again

Good luck mate 🫡