Moving my blog to AWS


Well, it has been wild. I streamlined the CI for this blog in 2023, which was an enormous step forward in reducing the technical burden, but more needed to be done.

Now, I’ve combined the knowledge I’ve gained through work and my own dedicated infrastructure to host this in S3 and use the remaining pieces in AWS.

To be honest, I was tired of managing DNS through a provider that deliberately scalped the price of domains and abused customers. I was also tired of trying to manage an Apex domain through GitHub Pages. I had no control over these inconveniences, and they were bothersome.

The benefit of moving to an all-AWS stack is that I can take advantage of my knowledge and keep it all together on a platform built for stability. It’s not the cheapest option, but it’s not expensive compared to other options.

At least now, using a CDN that I control, I can configure it quickly, and I do not ever need to worry about the overall site stability. I have had to move the domain, and there is still work to be done to update CI and development workflows.

But, this should increase content cadence.

Lastly, I have been sitting on two longer travel articles for some time, which I hope to get through a proper review with a content specialist. So, stay tuned for those!