Feed
Your setup could be easier: since you use both Route53 and Cloudfront, then ACM (AWS Certificate Manager) could generate TLS certificates for you, and will handle certificate rotation for you: now 90 days renewal to manage yourself or automate yourself.
I love Let'sEncrypt (EFF is the only non-healthcare organization I give donations to each year), but when there's a way to get a simpler setup (both easier to set up and easier to maintain because of automatic renewal), there's no reason to not use it ;-)
Nice one. I used to host static sites in Google Cloud. Now hosting everything in Netlify. It much easier, no need for these complicated setups, auto deploy from your git repo (CD), free ssl, edge server cache, branch previews, previews for merge request and a lot more.
Hi Paul Berg 👋
Great article. Thanks for re-publishing it. :) Some images were broken as Hashnode doesn't support HTML tags. I have fixed them. Please verify.
Cloudshock Dev
Code, memes, and tech memories; not necessarily in that order
Paul,
Great write up of the technical steps! I did something similar and used Hugo to generate pages based on mark up and deployed to S3 via a Github / Travis CI build process.
For me, figuring out (and tweaking) the Hugo template system was the most challenging aspect. As a cloud platform I find AWS fairly straight forward, and the integration with 3rd parties like Travis are remarkably easy. Also you can't beat the free AWS Certificate Manager certs, especially now that Chrome wants everything to be HTTPS.