Today we’re going to be covering one of the most fundamental skill sets when it comes to cloud computing, Infrastructure as Code (IaC). Regardless of which public cloud provider you’re using I would strongly recommend that you have a good understanding of what IaC is and how to use it. In today’s article we’ll be discussing the various IaC tool sets and what some pros and cons are. Additionally, we’ll explain why we chose to go with our IaC of choice for blog.masterthe.cloud.
I’m sure you’ve heard the terms thrown around enough, but what does CI/CD really mean? What roles are each responsible for? Maybe we can help clear some of that up in today’s blog post. Today we’re going to be discussing Continuous Integration (CI) and Continuous Delivery (CD) at high levels. We’ll discuss their native counterparts in AWS, and why we decided to use them for our production workflow. Additionally, we’ll discuss our wishlist and what we plan on doing in the future in regards to our established pipeline.
In part two of our Journey Through the Cloud we’re going to talk a little bit more about our overall desired endstate of our architecture. This will focus more on our end user expereince and best pracitces in regards to security, and not so much on the CI/CD process of our Jekyll site. If you’re a fan of CloudFront and or Origin Access Identity this will be the blog for you!
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.