Recent Ansible Adventures

 

Oops

So I recently picked up my Rundeck project again. My “production” instance has been running mostly* A-OK for many months now - except for 1 blip, it has got off easy. I’ve been using it as an unusual home for my own “documentation” of sorts. My plan for a third Rundeck blog post has been on the back-burner for a while, now beneath a virtual pile of other drafts. Now seemed good a time as any to resume my blog plans, starting where I left off!

My original plan was adding to the playbook so it configured the Rundeck Ansible Plugin as well. Ansible configuring Ansible. Instead of diving into the original plan I thought I’d re-familiarize myself with one layer of Ansible first.

As it happened, I had the inspiration I needed to start working on a money-saving playbook…

»

hugo --> AWS --> https://osgav.run

 

Why migrate to AWS?
Hugo –> S3
S3 –> CloudFront (+ ACM)
Route53
HTTP 403
HTTP 403 (moar)
www.osgav.run
References

Why migrate to AWS?

As well as catching up on drafted blog posts last weekend, I migrated this blog from GitHub Pages, KloudSec, Domain Registrar’s DNS & Let’s Encrypt to Amazon Web Services: S3, CloudFront, Route53 & Certificate Manager. I also introduced Travis CI and continued using GitHub for version control (but no longer hosting). This migration to AWS was in light of one of my apprehensions about KloudSec unfortunately materializing - it was a fairly small and new company and has recently ceased to exist. As such my Let’s Encrypt certificate had expired and was no longer auto-renewed by KloudSec so my blog was showing a HTTPS error when you visited it - boo. Time to pay for a risky design choice…

»