• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 114216, created on Jun 26, 2012, last review on May 16, 2016

  • Applies to:
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 10.4 for Linux/Unix

KB article for Plesk 12 version.

KB article for Windows version of Plesk.

Release Notes

To simplify Plesk 11 provisioning on Cloud for infrastructure providers (including service providers offering dedicated servers, VPS, or IaaS), Odin introduces the Plesk AMI image for the Amazon EC2 service.

Steps to Deploy

  1. Log in to the AWS Marketplace and go to the Plesk Panel with PowerPack product if you would like to deploy Plesk 11 with the included Power Pack license. Alternatively, go to Plesk Panel - Bring Your Own License (CentOS) if you already have a Plesk 11 license.

  2. Click the "Continue" button.

  3. Choose the 1-Click Launch tab and select "Region" to deploy an instance and EC2 Instance Type depending on your needs (Note: the price is different for different regions). Select the default option or create a new Security Group based on seller settings. Pay special attention to the ports that are required for Plesk:

    KB391 Which ports need to be opened for all Plesk Panel services to work with a firewall?

    Select the Key Pair to be used for connecting to the instance. (The existing Key Pair is required for connection to the Plesk instance.)

  4. Click Launch with the 1-Click button.

  5. When the instance is deployed, click the Visit Your Software link. The page with your subscription will be opened:

  6. Select Manage in the AWS console.

  7. (Optional) Attach your Elastic IP to the instance, and wait while the IP and its Public DNS are configured.

  8. Connect to the instance via SSH. Update system packages with the following:

    # yum update
  9. Run this command:

    # /usr/local/psa/bin/amazon_setup_ip <external IP>
  10. Log in to Plesk with the URL https://<external IP>:8443, using the login admin and the correct password, which you can retrieve with the help of this command:

    # /usr/local/psa/bin/admin --show-password

    Note: The panel can become inaccessible for a few minutes after instance deployment while updates are installed.

  11. Configure your server IP. It is recommended that you set up a shared IP.

  12. Specify a hostname. It is recommended that you use a domain name that you control or one controlled by the Amazon instance's Public DNS that will be constant in the case of an Elastic IP.

  13. Change your password.

  14. If you selected the Bring Your Own License product, then activate the license of the Plesk instance as described in the Plesk Panel 11 Installation and Upgrade Guide.

Changing IP address

After every stop/start (if no Elastic IP is used), or after assigning a new Elastic IP to a configured Plesk instance, you should do the following:

  1. Connect to the instance via SSH.

  2. Run this command:

    # /usr/local/psa/bin/amazon_setup_ip <new external IP>
  3. Reconfigure all external DNS servers used by the hosted domains to match the machine's new external IP.

  4. Check that all "A" records from the server-wide DNS template point to the new external IP, and synchronize the changes to all zones as described in the Administrator's Guide: Performing Mass Operations over DNS Zones.

    The article Nginx isn't started after IP change can be useful for Amazon/Plesk instances.

Plesk transfer to Amazon EC2 instance

To transfer your Plesk server to or from the Amazon instance deployed from the Plesk AMI, please follow the instructions in the KB article #117069 - How to migrate domains which use custom DNS template.

Known Issues and Limitations

  • It is not possible to install Plesk for Amazon EC2 with the general Plesk installer. Only the AMI image is supported.
  • The Tomcat component is not shipped with the AMI.
  • ColdFusion will not work in Plesk 11 on Amazon.
  • phpMyAdmin will not work with remote databases.
  • To change the time in Plesk Panel, you need to run the following command:

    # echo 1 > /proc/sys/xen/independent_wallclock
  • Some spam filters (including the default Plesk greylisting) consider mail auto-generated by Amazon hostnames as spam. Therefore, you may need to change the hostname.

  • If an external IP address is added on the interface/Plesk/domain and the nginx service is enabled, after upgrading to Plesk 11.5 websites may point to "Default Plesk Panel Page". If this occurs, switch domains to a Private IP addresses from the GUI: Plesk Control panel->subscriptions->change hosting settings.

Search Words


yum update


0a53c5a9ca65a74d37ef5c5eaeb55d7f 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 aea4cd7bfd353ad7a1341a257ad4724a 01bc4c8cf5b7f01f815a7ada004154a2 e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040

Email subscription for changes to this article
Save as PDF