Migrated my blog to https (after a few years of putting it off); getting HTTPS hosting for the images set up was the biggest sticking point for me, but now I've got to figure out a way to do it for the podcast MP3s, which are sitting on S3.
-
-
It's easier with
@caddyserver. I promise. -
Will take a look.
- 2 more replies
New conversation -
-
-
If you're already serving from S3 you can use CloudFront in front of that with HTTPS and avoid having to run your own nginx server.
-
This ended up being what I went with -- was able to us their Certificate Manager to get a cert for my podcast subdomain and then just pointed the CNAME from S3 to Cloudfront and then flipped some poorly defined switches as per posts on the Internet.
- 1 more reply
New conversation -
-
-
The quickest way is to use S3 https urls, no?
-
Yeah but I care about implementation details not leaking into the UX; same reason to have URLs over IP addresses counsels having URLs that refer to me not AWS.
- 1 more reply
New conversation -
-
-
Use https with the generic http://s3.amazonaws.com/bucketname URL, since nobody much looks at those URLs anyway?
-
(May need a different domain depending on S3 bucket's region, but public-read items available via https already.)
- 1 more reply
New conversation -
-
-
Put a cloudfront instance in front of S3. You can cname the CF instance and add your custom SSL cert. works great & very cost effective.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I'm not an expert, but maybe just put a Cloudfront distribution in front of the podcast MP3s?
-
These are the relevant docs: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-https.html … Let me know if I'm off-base here!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.