We have an S3 bucket that has dot “.” as part of its name, like: my.bucket. Upload to S3 backup fails because S3 wildcard certificate does not cover the domain that is constructed for this bucket. I can’t also browser this bucket from Virtualmin. The exact message from backup log is:
File does not exist: Can’t connect to my.bucket.with.dot.s3.amazonaws.com:443 (certificate verify failed)
LWP::Protocol::https::Socket: SSL connect attempt failed with unknown errorerror:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed at /usr/share/perl5/LWP/Protocol/http.pm line 51.
at S3/ListBucketResponse.pm line 26
Similar message appears when I try to browse the bucket from Virtualmin. I was looking for a setting where I can disable certificate verification but I could not find anything. There seems to be no simple fix for it:
a) *.s3.amazonaws.com wildcard certificate covers “1st level subdomains” only so buckets with dot in their name are not covered
b) the wildcard certificate itself is trusted so it’s not the matter of untrusted certificate
c) S3 does not allow to upload custom certificate
Any help (other than changing bucket name of course) would be highly appreciated.