Features and fixes for 0.2.0

[petewilcock]

Great response to the initial release of the module and some interesting feedback to think about. In no particular order, features list for 0.2.0 and beyond.

Major

• Provide a curated Docker image for Wordpress, to be hosted on Quay.io, which will remove the base image upload and CodeBuild steps, which seems to be the greatest friction for new or inexperienced users. CodeBuild option will remain behind a flag for those that prefer to 'own' their own image.
• Add a mechanism for SSL within the Wordpress container. Would probably need some kind of launch-generation/installation via a LetsEncrypt flow. Must be mindful of throttling restrictions.
• Offer non-Aurora mySQL container option for WP database - to be launched as a separate ECS container and persisted to EFS. This would be much cheaper for update cycles.
• Offer optional ECS Exec configuration for debugging issues or additional control from within container environment.
• Simplified mechanism of launching/shutting down the management container. I'm thinking pre-configured Cognito user pool to authenticate a static front-end with one-click launch/shutdown of ECS task.

Minor

• .gitattributes to ensure checkouts respect LF line endings and help avoid issues for Windows users.
• Perform additional pre-configuration by activating S3 add-on module and setting default ACL policy to private
• Integrate docker-entrypoint updates from upstream Wordpress container.
• Try to get the container to perform some proactive DNS refresh to avoid Guzzle crawl errors.
• In addition to modifying PHP memory limit, also modify WP_MEMORY_LIMIT in some way to increase from defaults of 40Mb.
• Add support for EFS backups (easily achievable in 3.47.0 of AWS Terraform provider)
• Allow user to configure EFS disk configuration and transition lifecycles (maintaining cost-efficient defaults)
• Consider default caching behaviour of CloudFront for improvements, and allow user-set overrides for caching values.
• Consider possibility of adding another Lambda@Edge or CloudFront function to dynamically rewrite the mime-type for WebP images that are currently not supported by S3. This would allow use of WebP for static publishing.
• Configurable Logging configuration for CloudFront & S3
• Customise retention policy for CloudWatch log groups.
• A solution to create/manage default log groups in all Edge Cache Regions - only us-east-1 is covered at the moment.
• Add optional S3 versioning (but strongly note expense of doing so).
• Investigate whether any S3 transitions would be worthwhile to further reduce cost.
• Configure pause timeout for RDS Aurora.
• Configurable alert (email via SES? Slack? Both!) when the management container has been running for n hours (to help to not forget to turn it off).
• Fix detail on EventBridge alerts Lambda.