To simplify Plesk provisioning in the Cloud for infrastructure providers (including service providers offering dedicated servers, VPS, or IaaS), Plesk provides AMIs (Amazon Machine Images) for deploying on the Amazon EC2 web service (for details, refer to https://aws.amazon.com/ec2/?nc1=h_ls). Each AMI allows deploying a particular instance of Plesk 12.5 optimized for specific needs.
Plesk 12.5 AMIs are shipped in five editions and are available for both Linux and Windows. The provided AMIs are listed below.
Image name |
License and OS version |
Plesk 12.5 for Linux Web Hosting with WordPress Toolkit (CentOS 7) |
Plesk Web Host Edition on CentOS 7 |
Plesk 12.5 for Linux Web Hosting with WordPress Toolkit (Ubuntu 14) |
Plesk Web Host Edition on Ubuntu 14.04 |
Plesk 12.5 for Linux Web Hosting with WordPress Toolkit and Security Bundle (CentOS 7) |
Plesk Web Host Edition on CentOS 7 + Kaspersky Antivirus + Security Core Complete |
Plesk 12.5 for Linux Web Hosting with WordPress Toolkit and Security Bundle (Ubuntu 14) |
Plesk Web Host Edition on Ubuntu 14.04 + Kaspersky Antivirus + Security Core Complete |
Plesk 12.5 for WordPress Hosting (CentOS 7) |
Plesk Web Admin Edition on CentOS 7 + WordPress Toolkit |
Plesk 12.5 for WordPress Hosting (Ubuntu 14) |
Plesk Web Admin Edition on Ubuntu 14.04 + WordPress Toolkit |
Plesk 12.5 for Developers with App Security (CentOS 7) |
Plesk Web App Edition on CentOS 7 + Security Core Complete. |
Plesk 12.5 for Developers with App Security (Ubuntu 14) |
Plesk Web App Edition on Ubuntu 14.04 + Security Core Complete |
Plesk 12.5 'Bring Your Own License' (CentOS 7) |
Plesk 12.5 on CentOS 7 with no license |
Plesk 12.5 'Bring Your Own License' (Ubuntu 14) |
Plesk 12.5 on Ubuntu 14.04 with no license |
Plesk for DNN Hosting |
Plesk Web Admin Edition on Windows + Control Suite |
Plesk 12.5 'Bring Your Own License' (Windows) |
Plesk 12.5 on Windows with no license |
Note: The 'Bring Your Own License' (BYOL) instance of Plesk 12.5 allows you to purchase your own license directly from the Plesk Online Store or from a Plesk reseller. Plesk 12.5 licenses are available for two platform types: for dedicated servers and for VPSes. You can use either with your Plesk installed on an Amazon EC2 VPS.
More information about Plesk 12 editions can be found in the following Knowledge Base article: Plesk 12 available editions and differences between them.
To deploy Plesk 12.5 from an AMI, perform the following steps:
Note: By default, instances are deployed with a small root storage (10 GB on Linux and 30 GB on Windows). To deploy instances with larger storage, use Manual Launch with EC2 console. To learn how to change the disk storage size after deployment, check the Amazon AWS documentation: Expanding the Storage Space of a Volume.
On Linux
Log in via SSH as the EC2-user using the private key of the Key Pair you deployed the instance with.
For CentOS, use the following command:
$ ssh -i <path to private key> ec2-user@<elastic or public IP>
For Ubuntu, use the following command:
$ ssh -i <path to private key> ubuntu@<elastic or public IP>
And then run the following command:
$ sudo plesk bin admin --show-password
On Windows
Log in via the remote desktop as the Administrator user with the password taken from the AWS console with the Get Windows Password action. Then, run this command in the command line or or powershell:
c:\> plesk bin admin --show-password
https://<public IP>:8443
using the login "admin" and the password you just retrieved.Note: Never add your public IP to your Plesk instance - only private IP addresses must be registered in Plesk. You can assign a public IP later, on the Tools & Settings > IP Addresses page (it is done automatically on Windows instances). For details, refer to the Administrator's Guide.
In Plesk 12.5 "Bring Your Own License", "Web Host", and "Web Pro" editions, there is an option to mark the private IP as either dedicated or shared. The private IP should be shared if you want to host different customers in Plesk (this can be changed later in Tools & Settings > IP Addresses).
Note: Some spam filters (including the default Plesk Greylisting tool) treat mail auto-generated by Amazon hostnames as spam.
plesk bin server_pref -u -subdomain-dns-zone own
plesk bin ipmanage -u `curl http://169.254.169.254/latest/meta-data/local-ipv4` -public-ip `curl http://169.254.169.254/latest/meta-data/public-ipv4`
After every stop/start, your instance changes the public and private IP addresses pair. As a result, you need to perform some additional steps. These steps must also be performed after assigning a new Elastic IP to a configured Plesk instance, but this requires an additional instance restart. For Plesk to operate correctly, all services must be configured to use the private IP, and all A-type DNS records pointing to the local services should point to the public IP.
$ sudo /usr/local/psa/bin/amazon_install_dns_template `curl http://169.254.169.254/latest/meta-data/public-ipv4`
You can find additional details on the DNS Template synchronization procedure in the Administrator's Guide: DNS Template.
plesk bin ipmanage -u `curl http://169.254.169.254/latest/meta-data/local-ipv4` -public-ip `curl http://169.254.169.254/latest/meta-data/public-ipv4`
In AMIs with Plesk 12.5, automatic reconfiguration of the public IP addresses is enabled by default. It means that you do not need to make any changes after the IP address change except the instance restart. Just make sure that the Plesk public IP has been changed to the new AWS Public (Elastic) IP in Tools & Settings > IP Addresses.
A number of actions are performed automatically when an instance is deployed, stopped, started, or restarted. You can disable these actions if necessary.
After an instance deployment, the following actions are performed automatically:
/usr/local/psa/bin/amazon_setup_ip `curl http://169.254.169.254/latest/meta-data/public-ipv4`
/usr/local/psa/bin/amazon_install_dns_template `curl http://169.254.169.254/latest/meta-data/public-ipv4`
After an instance stop/start/restart, the following actions are performed automatically:
/usr/local/psa/bin/amazon_setup_ip `curlhttp://169.254.169.254/latest/meta-data/public-ipv4`
To disable there reconfigurations, rename the /etc/rc.local
file to /etc/rc.local.bak
.
After an instance deployment, the following actions are performed automatically:
"%plesk_bin%\amazon\amazon_repair_ip.cmd"
After an instance stop/start/restart, the following actions are performed automatically:
"%plesk_bin%\amazon\amazon_setup_ip.cmd
To disable these reconfigurations, disable the scheduled task Prepare public IP.
If you have already deployed a Plesk instance based on an AMI of a previous version and want to upgrade to Plesk 12.5:
On Linux
/usr/local/psa/bin/.
/etc/rc.local
content with the following: #!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
touch /var/lock/subsys/local
main()
{
date
local amazon_public_ip=`curl http://169.254.169.254/latest/meta-data/public-ipv4`
if [ -n "$amazon_public_ip" ]; then
bash /usr/local/psa/bin/amazon_setup_ip $amazon_public_ip
fi
}
main >> /var/log/plesk/amazon_setup.log 2>&1
On Windows
C:\Program Files (x86)\Parallels\Plesk\admin\bin\amazon
.Go to Tools &Settings > IP Addresses and set the current Amazon Public IP as public IP for the local IP listed in the interface. Alternatively, run the following command: %plesk_bin%\ipmanage.exe -u "[local IP listed on interface]" -public_ip "[Amazon Public IP]"
(Here [local IP listed on interface]
and [Amazon Public IP]
should be changed to the corresponding IP addresses.)
This will enable automatic public IP reconfiguration (for more details, see the How it works section). To disable this reconfiguration, disable the imported scheduled task Prepare public IP. If your Plesk is not configured or its IP address has been changed, refer to the Changing IP address section above.
To transfer your Plesk server to or from an Amazon instance deployed from a Plesk AMI, follow the instructions provided in the Knowledge Base article How to migrate domains which use custom DNS templates.
/var/log/plesk/amazon_setup.log
file (on Linux) or the %plesk_bin%\amazon\amazon_prepare_instance.log
file (on Windows) for errors like the following:[2015-09-17 06:31:31] ERR [panel] Failed to update key. Attempt: 1
[2015-09-17 06:32:32] ERR [panel] Failed to update key. Attempt: 2
[2015-09-17 06:33:34] ERR [panel] Failed to update key. Attempt: 3
[2015-09-17 06:34:35] ERR [panel] Failed to update key. Attempt: 4
[2015-09-17 06:35:37] ERR [panel] Failed to update key. Attempt: 5
exit status 1
or the error like:
ERROR: bad arguments (Customizations.php:30)
Solution: check your network environment and accessibility of ka.plesk.com and installer.plesk.com, and redeploy the instance.
# bash /etc/rc.local
%plesk_bin%\amazon\amazon_setup_ip.cmd"
Plesk 12.5 AMIs are intended to be used on instances with direct access to the Internet, and can be launched in EC2 Classic network or in VPC if the instance with Plesk is the internet gateway for the VPC network (public IP can be returned with the following request: curl http://169.254.169.254/latest/meta-data/public-ipv4). Otherwise, Plesk AMI automatic customizations must be disabled and performed manually for the public IP of network's internet gateway (see the
How it works section). In addition, a port redirection for used services must be configured on the network's Internet Gateway to make Plesk services accessible from the Internet (the complete list of ports used by Plesk can be found in the Knowledge Base article Which ports need to be opened for all Plesk services to work with a firewall?).# plesk bin ipmanage --update `plesk db "select ip_address from IP_Addresses" | grep -E -o "([0-9]{1,3}[\.]){3}[0-9]{1,3}"` -public_ip `curl http://169.254.169.254/latest/meta-data/public-ipv4`