KB article for Windows version of Plesk.
Release NotesTo simplify Parallels Plesk Panel 11 provisioning on Cloud for infrastructure providers (including service providers offering dedicated, VPS or IaaS), Parallels introduces Plesk AMI image for Amazon EC2 service.
Steps to Deploy1. Login to the AWS Marketplace and go to the Parallels Plesk Panel with PowerPack product if you would like to deploy an Parallels Plesk Panel 11 with included Power Pack license or go to the product Parallels Plesk Panel - "Bring Your Own License" (CentOS) if you already have Parallels Plesk Panel 11 license.
2. Press Continue button.
3. Choose 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 default or create new Security Group based on seller settings. Pay special attention to the ports that are required for Parallels Plesk Panel: KB391 Which ports need to be opened for all Parallels Plesk Panel services to work with a firewall?
Select Key Pair to be used for connection to the instance. (existing Key Pair is required for connection to the Plesk instance).
4. Press Launch with 1-Click button.
5. When instance is deployed – Click Visit Your Software link – the page with your subscription will be opened:
6. Select “Manage in AWS Console”
7. (Optional) Attach your Elastic IP to the instance, and wait while the IP and its Public DNS will be configured.
8. Connect to the instance via SSH. Update system packages with
# yum update
9. Run this command:
# /usr/local/psa/bin/amazon_setup_ip <external IP>
10. Login to Parallels Plesk Panel with this URL: https://<external IP>:8443 using the login "admin" and the correct password, which you can get with help of command:
# /usr/local/psa/bin/admin --show-password
Note: The Panel can be inaccessible few minutes after instance deployment because of updates installation.
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 of controlled by the Amazon instance's Public DNS that will be constant in case of an Elastic IP.
13. Change your password.
14. If you chose the “Bring Your Own License” product then activate the license of the Parallels Plesk Panel instance as described in the Parallels Plesk Panel 11 Installation and Upgrade Guide.
Changing IP addressAfter every stop/start (if no Elastic IP used), or after assigning a new Elastic IP to configured Parallels Plesk Panel 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 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/Parallels Plesk Panel instances.
Know Issues and Limitations
- The Tomcat component is not shipped with the AMI.
- ColdFusion will not work in Parallels Plesk Panel 11 on Amazon.
- phpMyAdmin will not work with remote databases.
To change the time in Parallels Plesk Panel, you need to run the following command:
# echo 1 > /proc/sys/xen/independent_wallclock
- Some spam filters (including default Parallels Plesk Panel greylisting) consider mail auto-generated by Amazon hostnames as spam. Therefore, you may need to change the hostname.