In this blog series we’ll walk through why and how we chose our technology stack for our rebranding initiative here at masterthe.cloud. We’ll cover some intermediate Terraform, Static Site Generators (SSG), and some core AWS services. Additionally, there will be a video on our youtube channel towards the end combining all of the blog posts. This first part will cover Static Site Generators, what they are, and why chose the one we did.
Recently I decided to redo (yet again) both masterthe.cloud and blog.masterthe.cloud. This led to some akward data loss; however, I did manage to scour the internet and salvage some of the old blogs I had written. Those have been added but I’m much more excited for the future. Below I will talk about what the plans for the blog are and what some of the goals are.
I was recently tasked with investigating how to assign persistent static IP’s (four) to a RHEL EC2 instance. As a longtime Unix/Linux Engineer in a previous life, I (much like many of you right now) assumed this would be simple. I regret to inform you we were sadly mistaken. After a bit of research, I stumbled into quite a few separate ways to accomplish this goal. Here I have outlined what I believe to be the easiest methodology.
AWS released a learning path documenting the creation of a Unicorn ride service known as Wild Rydes. While the learning path (found here) is great at helping users understand the high level concepts of serverless architecture and the nitty gritty details of provisiong API gateways, DynamoDB tables, etc. it wasn’t very ‘real world’ friendly. This document aims to take the learning path a step up utilizing a few bash scripts, and the Serverless Framework to emulate a real world workflow. As a note I would strongly recommend completing the learning path as intended, then come back and revisit this page. That will give you a greater appreciation for how powerful and easy the Serverless Framework truly is.