This is the 3rd and final post in the Running WordPress on AWS Lightsail series. In this post, we’ll set up Cloudflare DNS, Web Application Firewall (WAF) and Content Delivery Network (CDN).
The first step of course, is to get a Cloudflare account. Once you sign in, go to the +Add Site menu selection in the upper right-hand side of the screen.
Next, you’ll add the website the “Add Websites” and let Cloudflare scan it.
It will scan the site and it will display the scanning process.
When completed, it shows “Scan Complete” status and then you click “Continue Setup”.
It shows the DNS configuration settings. Verify everything looks correct. You can make changes on this page.
At the bottom of the DNS settings list, click Continue. Select the Cloudflare Plan.
Hit Continue to the DNS Name Servers screen. These are the servers you updated your DNS settings to in AWS Route 53.
It shows the status of Cloudflare. Until the Name Server are updated and replicated out to the other DNS servers, it will show a status of “Not Active”. Once it updated, the status turns green and you can configure the firewall and caching.
This post is the second in the Running WordPress on AWS Lightsail series.
I already had an AWS account for lab testing and demos with my work at Zerto. So if you don’t have one, you’ll need one. I logged in and went to Lightsail.
The rest was really easy. Push the “Create Instance” button, choose the type of instance you want and it spins up in a couple minutes. I picked WordPress.
The AWS Lightsail WordPress instance gets up and running very quickly.
AWS also provides DNS hosting as well. Just click “Create DNS Zone and associate it to IP address shown on the WordPress instance. I didn’t use this because I’m using Cloudflare firewall and CDN.
Instead, I went to AWS’s Route 53 to change to the Cloudflare Name Servers in it. To do that, click on the AWS menu selection on the upper right next to the Billing menu choice.
The AWS button takes you to the AWS console.
Scroll down to the Networking & Content Delivery section.
Click on Route 53. It takes you to the AWS DNS Management console.
Click on the Hosted zones.
Here is where you change the Name Servers to the Cloudflare Name Servers.
In the next post in this series, we’ll set up Cloudflare.
Zerto has many customers already protecting virtual machines from vSphere and Hyper-V to AWS and Azure.
With the recent release, Zerto added several new features and fixes that make it worthwhile to upgrade the AWS or Azure Zerto Cloud Appliance (ZCA). See the release notes here.
The upgrade is really straightforward. Log into your ZCA, download the upgrade from MyZerto and then do the install. To demonstrate how easy it is, I created this video.