For a refresher, I decided to host my own WordPress blog on the AWS cloud. This gives me an opportunity to get “hands-on” with various technologies and tools. I was interested in running containers at cloud scale to see if this simplifies stuff. Please check out Cloudy with a Chance of Containers for an architecture diagram and the decisions that drove the design.
While this should have been relatively straight forward, AWS usually has little gotchas where you think you need to make a change “here,” but you really need to change something “waaaaaay” over there. I’ve documented the various gotcha’s and solutions so hopefully you don’t have to feel the same pain. Continue reading “AWS Gotcha’s – WordPress in Elastic Container Service”
I write a lot to help organize my thoughts. But most of my notes are either in a journal – there’s still something special about using a pen and paper, or in Word docs. This creates a couple of problems – it’s hard to search, and I’m the only one to benefit from this effort. Blogging is my way of sharing some of my ideas/thoughts that might help others, and to also make it searchable for my own needs.
Since this blog isn’t intended to be a revenue stream, I am not going to worry about site-optimization, pushing traffic, and all the other internet/ecommerce type stuff. My goal is to keep things simple and the costs manageable. The quick/easy would be to spin up a virtual machine, load it with a LAMP stack, install WordPress, and be done. That’s what the super-basic WP hosts offer. But then I was thinking what if something I write somehow really hits a cord with peeps? This solution would crumble with traffic, plus it would be fragile. Time to distribute it.