![](https://static.gosquared.com/images/liquidicity/20_03_04_Wordpress_Hosting_on_AWS/20_03_04_AWSCloud_01@2x.png)
If you’re a regular around these parts, you may have noticed that this blog recently got a complete overhaul. But we didn’t just refresh the design with a new theme – we also completely revamped how it’s hosted to set us in good stead for anything we might want to do with it in the future.
For years this blog has been running on a third-party managed WordPress solution, with a messy arrangement of reverse-proxy servers and caching layers to keep it running smoothly and without falling over every time we had a mild traffic spike. With this new version, we’re now running everything inside our own infrastructure on AWS, which gives us much more comprehensive control over how everything is managed and scaled.
If you’re just interested in how you can do this for yourself, jump straight to the CloudFormation template at the end of this post. If you’re interested in some of the potential gotchas and caveats involved, read on.
Should I even be running WordPress myself?
![](https://static.gosquared.com/images/liquidicity/20_03_04_Wordpress_Hosting_on_AWS/20_03_04_Question_01@2x.png)