I suppose the quickest way is to put Nginx in between the Internet and S3 and have it "upgrade" everything to HTTPS... (I care about the mixed content warning more than I care about someone editing the MP3s in flight, for all the obvious reasons.)
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Migration complete including the podcast; please let me know if you see hinkiness.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Oh! That's nice. (Checked and it appears you're right: 9 cents / GB for first 10 TB from S3 versus 8 cents at same tier from Cloudfront.)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This turned out to be the pain-minimizing step. We'll see what happens to the AWS bill after my next episode ;)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I use a custom domain for S3 for aesthetic reasons.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Cloud front with ACM certs is pretty easy, or just use the https://s3.amazonaws.com/bucket-name urls
-
This Tweet is unavailable.
New conversation -
-
-
Congrats! This must be "https weekend" because I completed migration of a site today as well. The part I didn't realize I'd have to do until afterwards was all the third-party stuff (e.g., adding the https version of the site to Google Search Console).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
This Tweet is unavailable.
-
-
I literally just did this a couple of days ago. Same prob. Set up cloudfront (easy) with and imported my SSL cert + told it to use SNI
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.