Amazon Web Services, nginx, Docker, Hugo and a Raspberry PiMar 17, 2016 · 3 minute read
Hosting a static webiste on a Raspberry Pi (RPi from now on) is quite straight forward. Serving that same website from a Dockerized Nginx HTTP server -on that same RPi- is a bit more interesting. Sure.
But what if the RPi decides to take the day off?
This post is mainly for students who attended one of my Architecting on AWS or System Operations on AWS sessions. It contains instructions, links to templates, tools and scripts to get started with Amazon Route 53 DNS failover between a primary site hosted on a RPi and a secondary site hosted on Amazon S3 & Amazon CloudFront. It is however not an exhaustive list of all the steps required for such a setup: use it at your own risk.
The page you’re reading right now (the whole
fourteenislands.io domain for that matter) is written in Markdown and converted to a static site (HTML) with Hugo. Please go (no pun intended) have a look and come back here when you’ve written that novel of yours. I’ll wait.
Done? Good. You now want to serve the site you’ve generated directly from your RPi. We’ll do that with Nginx running in a Docker container. I’ve prepared some for you.
From a terminal on your RPi open your favorite text editor and save the following as docker-compose.yml
Start the Nginx container with the following command
$ docker-compose run -d --service-ports nginx
Amazon Route 53
In this section I assume you already have created an S3 bucket to store a copy of your static website and set up a CloudFront distribution to distribute that content (see Using CloudFront with Amazon S3 for instructions). I also assume you have the AWS CLI installed and configured.
Create DNS records and an health check with CloudFormation
First we want to create a primary record, an health check for that record and a secondary record to failover to when the primary record is not available.
Create a CloudFormation stack from that template directly in the AWS console or save the template locally, hit the terminal and run the following script(replace the
ParameterValue values with your own):
Update health check and primary DNS record
Once the health check, primary and secondary records have been created using the above CloudFormation template, the health check
IPAddress and the primary record
ResourceRecords should be automatically (hourly job on the RPi for example) updated with the following script.
Have fun and if you have any questions, please leave a comment.
fourteenislands.io is not currently served from a Raspberry Pi but from an Amazon S3 bucket.