Building a blog using AWS infrastructure

Journey: 📊 Community Builder 📊

Subject matter: Building on AWS

When I decided to create an AWS Community Builder blog, the only thing I knew I wanted to achieve at first was to host it on AWS.

While I have completed a project to build a CI/CD pipeline using individual AWS services before, for this blog I wanted to use a managed service.

💡 The site itself had to be easy to maintain once it was set up. 💡

So that I could decide on what type of blog I needed to create, I next decided on the content.

My outlined requirements were to:

• Share my thoughts on emerging technology.
• Link to interesting news from AWS releases.
• Quote to provoke inspiration.
• Promote videos I have enjoyed from fellow content creators.

From here I could then begin researching what services I could use and decided on a CI/CD pipeline using:

• GitHub
• AWS Amplify
• Route 53 to serve DNS

I hit various issues as I created the site which needed troubleshooting. At one point Amplify outright refused to stage and build my content following a refresh. Somehow the Go template files had been downloaded into the GitHub repository and could not be re-written up to Amplify again.

I ended up deleting the repository and republished it from the source again to fix it. However, I suspect I could have just committed the change locally and pushed those changes to reflect the change in GitHub to overcome the problem. I may write a separate post on this in case it helps others in the future!

This is how the architecture looks: