4 ms·
From the expense report, it says you have a wildcard SSL (and it seems to be in use in the subdomain for the signup page for example) yet your main root site se
by nacs 11y ago
From the expense report, it says you have a wildcard SSL (and it seems to be in use in the subdomain for the signup page for example) yet your main root site seems to be unavailable via SSL?
Is there any reason for this or just an oversight?
- destroytoday 11y agoThe marketing site is static-hosted on S3 and I think when I first set that up it was either too expensive for SSL or not possible. I'm not 100% sure, but I'll definitely look into it again. The wildcard SSL was a recent addition after coming out of beta, which didn't have the multiple subdomains.
- NeutronBoy 11y agoHot tip for when you get around to setting it up - SSL on S3 is far easier if you use CloudFront as the endpoint. At least it was 6 months ago when I was playing around.
- patmcc 11y agoIt's possible, as long as you're ok with SNI (which is a pretty minor issue these days). You have to setup SSL on CloudFront to get it to work, check out: https://bryce.fisher-fleig.org/blog/setting-up-ssl-on-aws-cloudfront-and-s3/ https://bryce.fisher-fleig.org/blog/setting-up-ssl-on-aws-cl... I used that for my static S3 site, it's working fine.