We have prebuilt a server image on the AWS marketplace that you can use to quickly create a WordPress server & site with WPCloudDeploy already pre-installed.
You will need some basic SSH skills to be able to log into the server and follow the prompts so you can connect your domain and setup WPCD.
After navigating to the AWS Marketplace page with the above button, please click the CONTINUE TO SUBSCRIBE button to get started.
When using this option, you have a few choices during the process:
When creating the instance, you should ensure that you enable the options for SSH, HTTP and HTTPS in the NETWORK SETTINGS section as shown in the image below:
Once the instance has been created you will need to login to it via SSH to continue the setup process.
When you login for the first time you will be asked to choose your domain and to provide your email address. Your email address is required to setup your SSL certificate and to make sure that your WPCD site knows where to send any alerts.
If the domain you provide is pointed to the IP address of the new droplet we’ll request an SSL certificate. We strongly recommend that you point your domain IP address to the new droplet PRIOR to entering the domain name here so that the SSL certificate can be issued.
When you get to the end of the process you will see additional instructions on how to access the site.
Generally your site can be accessed at https://yourdomain.com/wp-admin.
If you log out and log back into the server using SSH, you will be prompted to setup the site again. This is because the setup script is part of the root user after-login script.
If you proceed to run through the setup again, you will irreversibly damage the original site. Instead you should CTRL-BREAK / CTRL-C out of the script.
To prevent the script from accidentally running again you can remove the script from the root user start up sequence as follows:
Edit the root user start up script:
nano ~/.bashrc
Scroll down to the bottom of the file. There you will see a line that looks like this:
bash /root/800_do_first_login.sh
Just delete the line (and the related comment above it). Then save the file:
ctrl-o <enter>
And exit the nano editor:
ctrl-x
Test that the script no longer runs on login by logging out and then logging back in with ssh.
If you’ve purchased a license from us, it is possible that you have a more recent version of the plugin than what is on the droplet. So the first thing you should do is upload a copy of the version of the plugin you got from us – you can do this from the regular WordPress PLUGINS screen.
Additionally, if your license include premium providers such as Linode and Vultr, you should upload those and activate them as well. This will allow you to use the quick-start Wizard (described later) with these premium providers.
Once you’re logged into WPCD for the first time, you have a number of ways to proceed with setup.
When you log into WPCLOUDDEPLOY for the first time you will see a green banner at the top of the screen. This will allow you to invoke an easy on-boarding process as long as you are deploying your new servers into the DigitalOcean cloud.
If you are NOT deploying servers into the DigitalOcean cloud and you have one of our premium providers (eg: AWS EC2, AWS LightSail, Linode, Vultr etc.), you MUST skip this on-boarding process and use the advanced instructions shown later in this document.
To continue with this easy setup, click the button in the green banner to get started and you’ll see the first page of the on-boarding wizard.
Because we have automatically created an encryption key for you with this AWS EC2 instance you can just click the green CONTINUE button to move to the next step:
You can get your API Key from your Cloud Provider’s dashboard – use the API Menu option to generate a key. Make sure the key has WRITE permissions!
Enter the api key and click the green CONTINUE button to move to the next step where you will generate your SSH key-pair:
We use SSH keys instead of passwords to access your servers. This step will allow us to generate a unique pair for you, submit the public portion to DigitalOcean and securely store the private portion in WPCD.
Just click the green CONTINUE button to proceed.
At the next step click the green CONTINUE button to complete the process and go to the servers list.
To create your first server:
Important: Please choose a server size with at least 1 GB RAM. DigitalOcean offers droplets with as little as 512MB but those will not work for WPCD WordPress servers.
After a server is provisioned you will be returned to the servers list where you will see the new server available for use. You will also see a message in the health column about CALLBACKS being unavailable – you can ignore that message because they will eventually be installed in the background.
It’s now time to install your first WordPress site.
To create your first site after creating your first server:
As mentioned earlier in this document, you will need to use this option if you want to deploy WordPress servers at any provider other than DigitalOcean OR you want to use your own SSH key-pairs. This includes AWS EC2.
There are the seven groups of actions you will perform:
To deploy servers into the AWS cloud you need a premium license for WPCloudDeploy – you can purchase one from our store.
After you’ve made your purchase, please download the EC2 provider file and install it as you would any WordPress plugin into your new WPCloudDeploy site. (Full installation and usage instructions can be found here: https://wpclouddeploy.com/documentation/cloud-providers/ec2-provider/)
The Core WPCloudDeploy plugin is already installed on your EC2 instance and ready to be connected to your EC2 account. However, you still need to install the WPCD AWS EC2 premium provider.
Installing any premium provider plugin, including the one for AWS EC2, is just like any other WordPress plugin:
You will need to create an IAM user (or use an existing IAM user) with the proper permissions to create EC2 instances. You will obtain your EC2 ACCESS KEY and EC2 SECRET KEY from this user.
You must create or upload an SSH key pair to the region where you will be building your servers. You cannot use the ‘default’ ssh keys that AWS provides – you must create a new pair or upload your own pair. AWS keypairs are specific to a region. If you need to use the same keypair in all regions then you must upload it to all regions. (How To Create SSH Keys.)
Full installation and usage instructions for AWS EC2 can be found here: https://wpclouddeploy.com/documentation/cloud-providers/ec2-provider/
Please verify that the default security group for your account has ports 22, 80 and 443 (SSH, HTTP and HTTPS) open. All WordPress servers are provisioned in your default security group.
Now you’re ready to quickly run through the steps to get your first server and site up and running.
To create your first server:
Important: Please choose a server size with at least 1 GB RAM. Your provider might offer instances with as little as 512MB but those will not work for WPCD WordPress servers.
After a server is provisioned you will be returned to the servers list where you will see the new server available for use. You will also see a message in the health column about CALLBACKS being unavailable – you can ignore that message because they will eventually be installed in the background.
To create your first site after creating your first server:
As mentioned earlier in this document, you will need to use this option if you want to deploy WordPress servers at any provider other than DigitalOcean, Linode, Vultr, Hetzner and UpCloud OR you want to use your own SSH key-pairs.
The Core WPCloudDeploy plugin is already installed and ready to be connected to a DigitalOcean account.
However, if you’re going to be connecting to any other cloud provider (eg: Linode, AWS etc.), then you must purchase a license from our store and download the premium provider plugins from your account.
Installing any premium provider plugin is performed just like any other WordPress plugin:
If you are not going to be use DigitalOcean to deploy your WordPress servers then you must obtain API keys for whichever service you will be using.
Each cloud provider has a different method for creating API keys. We have some caveats on keys and other restrictions for certain providers in our Cloud Provider documentation. Please make sure you read the information for the one(s) you are using before proceeding to the next step.
Also, please make sure you create a read-write keys/tokens – some providers allow you to specify these types of fine-grained permissions.
We use SSH keys and only SSH keys to connect to your cloud servers. This means that you must have at least one key-pair created and uploaded to your cloud server providers. OR, for certain providers, we can generate and install them for you.
We can automatically generate and upload SSH keys for the following cloud server providers:
Certain other providers have different SSH key requirements. Please make sure you read our Cloud Provider documentation for your provider(s).
AWS, GOOGLE CLOUD and UPCLOUD in particular have very specific SSH key requirements.
If you need to generate an SSH key-pair, you can use this guide to learn how to generate one.
If you going to be using your own SSH keys (either because we don’t offer the option to automatically generate them or because you want to use your own), then it is very important that you create and upload them to your cloud server provider before moving on to the next step!
Connecting to your cloud server provider can be very simple or very complex. Simpler providers include DigitalOcean, Linode & Vultr. Complex providers include AWS EC2 & Lightsail, Google Cloud & Azure.
We recommend that you read any of our Cloud Provider documentation notes for your provider(s).
For this section, we’ll assume you’re using DigitalOcean as your cloud server provider – if you’re using a different provider and have installed and activated the plugin for them, just substitute your provider for DigitalOcean in the instructions below. We’ll insert notes for the more complex providers as well.
Now you’re ready to quickly run through the steps to get your first server and site up and running.
To create your first server:
Important: Please choose a server size with at least 1 GB RAM. Your provider might offer instances with as little as 512MB but those will not work for WPCD WordPress servers.
After a server is provisioned you will be returned to the servers list where you will see the new server available for use. You will also see a message in the health column about CALLBACKS being unavailable – you can ignore that message because they will eventually be installed in the background.
To create your first site after creating your first server: