I have set a CNAME entry to redirect over Amazon S3 bucket, however there is something that doesnt works as supposed (by me of course) with CNAME I expect to redirect a fictional subdomain, say for example
s3.example.com to the Amazon S3 bucket with the same name.
Now the problem is that
example.com doesn't have a SSL while Amazon bucket does. For what I assumed, with a CNAME rule it should redirect the traffic before to ever reach my webserver and check for the presence of a certificate, notice that for this purpose the DNS is set to my domain provider and not my hosting provider.
Why is it ever checking for SSL when there is a CNAME rule and it is working? If for example I remove the
s from the url it opens the relative file in the bucket without any certificate warning.
edit: the error returned is different, I'll try to translate and adapt it:
s3.mydomain.com is using a not valid certificate. the certificate is only valid for the following names: *.s3.eu-central-1.amazonaws.com, *.s3-eu-central-1.amazonaws.com, s3-eu-central-1.amazonaws.com, s3.eu- central-1.amazonaws.com, s3.dualstack.eu-central-1.amazonaws.com, *.s3.dualstack.eu-central-1.amazonaws.com, *.s3.amazonaws.com
it then seems that he is reading the CNAME rule and looking up the correct domain (amazon s3) then it confront this against my domain and see it is a different name, it then stops before redirecting. For this reason if I remove the
s it will give no error. Now I'd try to install let's encrypt and see if having a certificate would help, but my guess it will still make this check ad give again a similar if not the same result.