When I first thought about starting a “blogging” website I was thinking of posting on another social media platform. But then I wanted to be able to post what I wanted and format it the way I seen fit. I decided to build a WordPress site and I felt what better place than the company I work for, AWS. It took me a week to test and figure out if AWS Elastic Beanstalk was what I wanted.

I like AWS Elastic Beanstalk, in fact two years ago I was able to dive deep on it by deploying out my previous company’s website and utilizing a DevOps approach. I had it integrated with AWS Code Pipeline pushing updates and redeploying the environment. It worked well for the most part but ran into logistical issues with the development team and how they were “used” to doing things.

Then I came across the following Git Repo (see below for a link) and it’s life changing. Just look at this awesome architecture! It’s exactly what I was looking for when developing my website.

Before I get really nerdy on you. I spent two weeks deploying this stack using http (not “S), selecting my own WordPress theme, modifying the layout, menu’s only to have issues getting HTTPS to work.

I’m going to give you a BIG hint to start. If you have a domain and you want to use AWS ACM but haven’t set it up yet. Do it first!! It will save you a lot of hassle. I tried http and ended up destroying after a week, only to redeploy with it using HTTPS and the required ACM ARN.

Since I don’t expect a lot of HITs just yet, I’m only using a single instance but what I like about it, is EFS. I did a demo on it when it first came out and I think it’s perfect for this type of use case.

https://github.com/aws-samples/aws-refarch-wordpress

As always, make sure you give credit to the contributors of this awesome repo.

This blog/website represents my own viewpoints and not of my employer, Amazon Web Services.