New: Become a sponsor via GitHub Sponsors!

WordPress: fault tolerant and scalable (MySQL)

Use this CloudFormation template to create a fault tolerant and scalable WordPress environment on AWS running on MySQL.

Features

Services

This template combines the following services: * CloudFront: CDN for dynamic and static content * ELB: load balancer forwarding requests to EC2 instances and terminating SSL * EC2: virtual machines running the web servers * EFS: storage for WordPress files (WordPress core, plugins, themes, user uploads, ...) * RDS: MySQL database

Architecture

Amazon S3 URL: https://s3-eu-west-1.amazonaws.com/widdix-aws-cf-templates-releases-eu-west-1/stable/wordpress/wordpress-ha.yaml

Installation Guide

Important: A custom domain name (e.g. www.yourdomain.com) is needed before installing Wordpress based on this template.

  1. This template depends on one of our vpc-*azs.yaml templates. Launch Stack
  2. Create an ACM certificate for your custom domain name within the region you want to launch your stack in. Copy the ARN of the certificate. This is for the ELB.
  3. Create another ACM certificate for your custom domain name in region us-east-1. Copy the ARN of the certificate. This is for CloudFront (note: CloudFront only supports ACM certificates in us-east-1)
  4. This template depends on one of our zone-*.yaml templates. Launch Stack
  5. Launch Stack
  6. Click Next to proceed with the next step of the wizard.
  7. Specify a name and all parameters for the stack.
  8. Click Next to proceed with the next step of the wizard.
  9. Click Next to skip the Options step of the wizard.
  10. Check the I acknowledge that this template might cause AWS CloudFormation to create IAM resources. checkbox.
  11. Click Create to start the creation of the stack.
  12. Wait until the stack reaches the state CREATE_COMPLETE
  13. Copy the value of CloudFrontDomainName from the Outputs tab of your stack.
  14. Create or update a CNAME/Alias record for your custom domain name pointing to the CloudFrontDomainName from the previous step.

Dependencies

Limitations

WordPress: fault tolerant and scalable (Aurora)

Use this CloudFormation template to create a fault tolerant and scalable WordPress environment on AWS running on Aurora.

3 or more AZs required

Features

Services

This template combines the following services: * CloudFront: CDN for dynamic and static content * ELB: load balancer forwarding requests to EC2 instances and terminating SSL * EC2: virtual machines running the web servers * EFS: storage for WordPress files (WordPress core, plugins, themes, user uploads, ...) * RDS: Aurora database

Architecture

Amazon S3 URL: https://s3-eu-west-1.amazonaws.com/widdix-aws-cf-templates-releases-eu-west-1/stable/wordpress/wordpress-ha-aurora.yaml

Installation Guide

Important: A custom domain name (e.g. www.yourdomain.com) is needed before installing Wordpress based on this template.

  1. This template depends on one of our vpc-*azs.yaml templates. Launch Stack
  2. Create an ACM certificate for your custom domain name within the region you want to launch your stack in. Copy the ARN of the certificate. This is for the ELB.
  3. Create another ACM certificate for your custom domain name in region us-east-1. Copy the ARN of the certificate. This is for CloudFront (note: CloudFront only supports ACM certificates in us-east-1)
  4. This template depends on one of our zone-*.yaml templates. Launch Stack
  5. Launch Stack
  6. Click Next to proceed with the next step of the wizard.
  7. Specify a name and all parameters for the stack.
  8. Click Next to proceed with the next step of the wizard.
  9. Click Next to skip the Options step of the wizard.
  10. Check the I acknowledge that this template might cause AWS CloudFormation to create IAM resources. checkbox.
  11. Click Create to start the creation of the stack.
  12. Wait until the stack reaches the state CREATE_COMPLETE
  13. Copy the value of CloudFrontDomainName from the Outputs tab of your stack.
  14. Create or update a CNAME/Alias record for your custom domain name pointing to the CloudFrontDomainName from the previous step.

Dependencies

Limitations