This is misleading. Cloudfront doesn't charge anything for putting your domains on an SSL cert that uses SNI. They only change you if you need a cert without SNI, which requires them to allocate a dedicated IP address to you.
I'm hosting my personal blog on S3 and cloudfront, with SSL, for less than a dollar a month.
Performance and capabilities are fine for me, too. I get 0.15 seconds to first byte from Chicago, vs 0.24 for the author's site.
https://www.webpagetest.org/result/180214_K2_28c2826a6422b01...
https://www.webpagetest.org/result/180214_QT_a91f7af3bf78e7b...
I plan on expanding on the featureset, so no S3 for me. :)
I forgot to add that this applies only to R&D and hobby projects, for production setups I'm a bit more careful. :)
(I'm the author.)
Maybe. I agree it's not as clearcut as always pick the less traveled road, but the difference between the two may include a competitive advantage that you'd be unwise to overlook. I mean, you're on HN; Paul Graham and Common Lisp back in the 90s is an excellent example.
https://www.digicert.com/ssl-support/apache-secure-multiple-...
If you need to handle bursty traffic, you're likely going to get best value in shared tenancy services until you can fully utilize your servers. Otherwise, you will probably end up paying for idle infrastructure.
I noticed this line at the bottom of the page: "When it comes to picking a solution, I often choose the less traveled road". I don't agree with that at all, and it sounds a bit like NIH syndrome. It's always better to choose the most-traveled roads, especially in DevOps. If there's a problem, then you can join those communities and contribute to the projects.
[1] https://aws.amazon.com/cloudfront/custom-ssl-domains/