The EC2 provider is just a regular WordPress plugin – upload and activate it from the WordPress PLUGINS screen.
Connecting to EC2 and automatically creating servers requires a lot more moving parts to be synchronized than simpler providers such as DigitalOcean and Linode. In particular:
It is very important that all five of the above items be checked and double-checked before proceeding. Otherwise provisioning a server on EC2 WILL FAIL.
The AWS EC2 provider then needs connection and security information before it can be used. You can provide this information under WPCLOUD DEPLOY->SETTINGS->CLOUD PROVIDERS-AWS EC2. There are several steps to this process:
After the provider is installed and configured you’ll see it as an option when deploying a new server:
Servers are placed into EC2’s ‘default’ security group. There are times where this group BLOCKS incoming traffic – this will cause server deployments to fail since we’ll be unable to connect to it automatically. You should EDIT the default security group to ensure that traffic is allowed from your WordPress server where WPCD is installed. In particular, the SOURCE for incoming traffic is set to “custom” by default – you need to change this to “Anywhere” or specify the IP address of your WordPress server where WPCD is installed.
Alternatively, you can set it up so that only SSH, HTTP and HTTPS traffic is allowed in from all sources.
The basic EC2 provider can only be used in one region. In order to use it in multiple regions, you need to install the VIRTUAL PROVIDER add-on. Once that has been installed, you can create a virtual provider for each region – learn more in the Virtual Provider documentation.
If you do not see a region you expect in the region list, please check to make sure that you have opted into that region in your AWS console. AWS now has a nice global view summary that includes a column showing your opt-in status for a region: https://console.aws.amazon.com/ec2globalview/home#
EC2 instances default their root device to only 8GB. For most single WP sites this does not pose an issue. But if you will install multiple sites on the device you will need to increase its size. This exercise requires some comfort level with the command line as well as familiarity with the AWS EC2 console!
Step 2 generally involves the use of the growpart and resize2fs commands which:
Running a backup on an instance that is too small for the amount of data being backed up will cause the MariaDB server to stop. You will have to manually restart it. This seems to be a flaw in the EC2 instance.
So, if you intend to use our backup process on these instances please make sure you run a few backup tests before placing your site into production to make sure there are no issues.
If you do want to continue to use these instances without our backup process in place you can always use a plugin backup process such as Updraft Plus which does not tax the instance as much but takes far longer to complete.
Server Sync cannot be used on AWS servers – neither as source nor destination.
The function to copy a site to a new server will not work with AWS EC & Lightsail servers as targets.
When deleting a site, the option to also delete all local backups will not work on AWS servers.
Want to know which EC2 instance to use? Take a look at this document on Github that outlines all the various instance types and their differences.