In my day job recently I’ve been rewriting AWS deployment infrastructure-as-code taking Serverless-Framework and raw Cloudformation transforming it into Terraform. While I’ve used Terraform to deploy infrastructure for many years, this particular task was rather interesting as I had to replicate what Serverless-Framework did with regard to building the bundles and deploying them.

For obvious reasons I’m not going to use exact examples of code bundles here, but the Hello sample code from a freshly created Lambda function.

Since I setup the new version of this blog using Hugo, hosted on Cloudfront, I put together a Grafana instance to monitor traffic hitting the CDN. I noticed quite a number of errors and realised these would be dead links out in the wild. I wondered if I might figure a way of replicating the path structure I had with WordPress over here on Hugo.

Initially I looked at the behaviours on the CloudFront distribution and figured quite quickly that it needed to be a Lambda@Edge. So I started writing something that would perform the redirects for me. This seemed a lot of work for what would be relatively straight forward in something like NGinx, but hey ho.. I then realised that there would be Lambda invocation costs associated with doing this, and not being one willing to spend more than I have to with AWS I tried to look elsewhere.