Major Updates to Our WordPress Pattern
We recently released version 2.0.0 of our WordPress pattern – there are some big updates here.
The largest change is a move away from the Bedrock subproject to more of a pure WordPress installation. In previous versions, we assumed the use of the Bedrock WordPress subproject, which makes it easier to manage WordPress via a CICD workflow.
However, when working with customers, we discovered that the real value of WordPress is to be able to use the UI to make updates. So we decided to update our pattern to use the stock WordPress install. We setup AWS EFS to manage the WordPress files and user-generated content. So with this latest version you can use WordPress to install plugins, update itself, and other administrative tasks. This changes will persist between instance re-provisions, due to the EFS filesystem in place.
On the first deployment of the pattern, we start with a fresh WordPress installation, and allow the user to customize the install either via SFTP (with Systems Manager Session Manager) or using the WordPress UI directly.
We think this is now the easiest way to get a production-ready WordPress install in an AWS account – please give it a try!