Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This is a response I got from their Premium Services</p> <blockquote> <p>Hello,</p> <p>This is actually a issue with the way SSL validates names containing a period, '.', > character. We've documented this behavior here:</p> <p><a href="http://docs.amazonwebservices.com/AmazonS3/latest/dev/BucketRestrictions.html" rel="noreferrer">http://docs.amazonwebservices.com/AmazonS3/latest/dev/BucketRestrictions.html</a></p> <p>The only straight-forward fix for this is to use a bucket name that does not contain that character. You might instead use a bucket named 'furniture-retailcatalog-us'. This would allow you use HTTPS with</p> <p><a href="https://furniture-retailcatalog-us.s3.amazonaws.com/" rel="noreferrer">https://furniture-retailcatalog-us.s3.amazonaws.com/</a></p> <p>You could, of course, put a CNAME DNS record to make that more friendly. For example,</p> <p>images-furniture.retailcatalog.us IN CNAME furniture-retailcatalog-us.s3.amazonaws.com.</p> <p>Hope that helps. Let us know if you have any other questions.</p> <p>Amazon Web Services</p> </blockquote> <p>Unfortunately your "friendly" CNAME will cause host name mismatch when validating the certificate, therefore you cannot really use it for a secure connection. A big missing feature of S3 is accepting custom certificates for your domains.</p> <hr> <p><strong>UPDATE 10/2/2012</strong> </p> <p>From @mpoisot:</p> <p>The link Amazon provided no longer says anything about https. I poked around in the S3 docs and finally found a small note about it on the Virtual Hosting page: <a href="http://docs.amazonwebservices.com/AmazonS3/latest/dev/VirtualHosting.html" rel="noreferrer">http://docs.amazonwebservices.com/AmazonS3/latest/dev/VirtualHosting.html</a></p> <hr> <p><strong>UPDATE 6/17/2013</strong></p> <p>From @Joseph Lust: </p> <p>Just got it! Check it out and sign up for an invite: <a href="http://aws.amazon.com/cloudfront/custom-ssl-domains" rel="noreferrer">http://aws.amazon.com/cloudfront/custom-ssl-domains</a> </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload