Hey! Listen! This post is part of a series on deploying Hugo. Check them all out!
|2022-02-08||Deploying Hugo with Netlify||Deploying on Netlify|
|2021-10-13||Deploying Hugo with CloudFront and S3||Deploying on CloudFront and S3|
|2021-09-21||Deploying Hugo with AWS Amplify||Deploying on Amplify|
In my last post, I was testing the deployment of Hugo with AWS Amplify. My only complaint was that Amplify doesn’t support IPv6. Because of this, I wanted to explore other deployment options under the AWS umbrella.
CloudFront and S3
I won’t cover the technical details of the setup here, you can Google for that.
For the admin user (i.e., me), I used Terraform to create the AWS infrastructure (DNS, certificates, S3 bucket, CloudFront distribution, etc…) and GitHub/GitHub Actions to host, build, and deploy the code to S3.
For visitors, CloudFront handled HTTPS and redirects from the
www site. The HTML files hosted in S3 were not directly accessible (i.e., I used a CloudFront origin access identity to restrict access).
Below was the minimum viable product I setup for my testing. There were other things missing from here that would be in a production setup, like buckets for logging, Lambda functions, etc…
In practice, this setup was difficult to get going. In Terraform, I had to create the following items:
- DNS entries (using Route53)
- S3 bucket (for static files generated by Hugo)
- S3 bucket policy (to allow CloudFront access)
- Certificates (and automatic validation)
- CloudFront distribution
- IAM user (for GitHub Actions)
- IAM user policy (to allow access only to S3)
Then, I had to setup GitHub Actions and my Hugo deployment settings, which took a few tries to get right.
What I liked
- Fine-grained control - CloudFront has some pretty powerful options, like geo restrictions, web application firewalls, price classes, and more. I was very impressed with the amount of control it offered.
- IPv6 - As I said in my last post, I wanted IPv6 support, and CloudFront checked that box for me.
- S3 - S3 is addictive and way too convenient. It’s like having an unlimited hard drive in the cloud. I’ll probably keep using it to store other assets for my site, even if the site isn’t hosted on S3 itself.
What I didn’t like
- Complicated setup - The Terraform code required for setup was complicated. Especially frustrating was the nugget of information I missed about CloudFront certificates only working if they were created in the
us-east-1region (I was using a different region).
- URL redirects - I have a few custom URL redirects setup, and CloudFront doesn’t support those natively without an edge function (while Amplify does). Right now, if I’m going to switch, it needs to be easier than Nginx.
Ultimately, I choose the tear down my CloudFront and S3 demo site in favor of my plain-old Nginx server. If you’re keeping track, the score is:
If you host a Hugo site, tell me how! I’m open to any options!