How to bypass the HTTPS restriction when using CNAME for S3?

Question

Amazon Web Services

There is an S3 bucket accessed by a web application that is available to everyone on the Internet via GET, POST (direct upload).
Some computers are denied access to S3 due to network restrictions (by admin).
To get around this limitation, I thought a good solution would be to create a CNAME record s3.example.com -> somebucket.s3.aws.amazon.com as described in https://docs.aws.amazon.com/AmazonS3/latest/dev /Vi...
There's a catch though: this scheme doesn't work because the SSL certificate doesn't match:

SSLError: hostname 's3.example.com' doesn't match either of '*.s3.amazonaws.com', 's3.amazonaws.com'

Am I missing something? What can you offer?

Answer 1

No way.
The certificate was then invented to confirm that the connection was made with www.zhopa.ru and not with www.zadnica.ru. The meaning is the same ;), but the domain names are different and if the certificate is issued on zhopa.ru, then write any alias - there will be an error