Ok, let’s do this thing! In this post I’m going to be adding a WordPress Auto Scaling Group spread across two availability zones, and an Application Load balancer to accept connections on port 80 and direct traffic to the Auto Scaling Group. Both will be added to the CloudFormation template I started in my last blog post.
Month: January 2020
Provision a MariaDB RDS Database Instance with CloudFormation in AWS
I’m now 5 posts into this series (and 5 months in), and I’m finally ready to start talking about provisioning my workload, i.e. WordPress. I’ve laid out a rough outline for this, and it’s clearly too much for a single blog post, so I’m going to split it into 3 posts, which I’ll try to publish in the next 3 weeks or so (rather than 3 months, as I’ve been pacing myself until now). After all, I’ve spent twice as much time (in terms of months, not man hours) writing this series as I spent building and launching my blog on AWS. So the next three posts will be:
- Provision a MariaDB RDS Database Instance with CloudFormation in AWS (this post)
- And Finally, a WordPress Cluster using CloudFormation in AWS
- How’s About we add a Scaling Policy, eh?
This post and the last one will be relatively brief, but the middle post will be substantial enough to justify splitting it up. So let’s get started.