KB article for Plesk 12 version.
KB article for Linux version of Plesk.
How to deploy Plesk 11 on Amazon EC2 service (Windows)
To simplify Plesk 11 provisioning on cloud infrastructure providers (including service providers offering dedicated servers, VPS, or IaaS), Odin introduces the Plesk AMI image for Amazon EC2 service.
NOTE: All Amazon EC2 instances are assigned two IP addresses at launch: a private IP address (RFC 1918) and a public IP address. These two addresses are directly mapped to each other through Network Address Translation (NAT):
It can cause that some services will not work properly. As an alternative, you can use Windows Azure service for the same purpose: http://kb.odin.com/114648
Steps to Deploy
Log in to the AWS Marketplace and go to the Plesk with PowerPack product if you would like to deploy Plesk 11 with included Power Pack license or go to the product Plesk - "Bring Your Own License" (Windows) if you already have Plesk 11 license.
Press Continue button.
Choose 1-Click Launch tab and select Region to deploy an instance and EC2 Instance Type depending from 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 Plesk : KB391 Which ports need to be opened for all Plesk services to work with a firewall?
And select Key Pair to be used for connection to the instance. (existing Key Pair is required for connection to the Plesk instance).
Read the User End License Agreement and AWS Customer Agreement and click Assept Terms and Launch with 1-Click button.
When instance is deployed – Click Visit Your Software link – the page with your subscription will be opened:
Select “Manage in AWS Console”
Select your new instance and get the Administrator Password. Open the Instance Action menu and choose "Get Windows Password." Use your key pair key to decrypt the password. You do not have to change the Administrator password because it is automatically regenerated for each instance.
(Optional) Apply Elastic IP:
a. Attach your Elastic IP to the instance and wait while it configures.
b. RDP to the instance.
(If you do not use Elastic IP, this step is not needed.)
Use the DNS (or IP from the DNS) from the instance information frame to RDP to the new instance.
%plesk_bin%\amazon\amazon_prepare_instance.cmdscript, which is executed upon startup of the first instance, prepares your instance with the next steps:
a. Execute the Plesk cloning procedure.
b. Install Plesk Micro-Updates.
c. Set up the new IP (run
d. Update the key (PowerPack version only).
You can check the log of this script execution:
Now you can access your Plesk instance from your AWS Marketplace subscriptions list by pressing the Access Software link
https://<instance public DNS or IP>:8443. Use Administrator’s credentials to login into the panel for the first time.
If the private/public IP pair of your instance is changed due to stopping/starting, or another Elastic IP is attached, please use these steps:
- RDP to the instance.
amazon_repair_ip.cmdfrom this KB and place it in
%plesk_bin%\amazon\. Check this command file. Please pay attention to the
PASSIVE_PORT_RANGEvalue. It must be the same as for FTP-passive-port-range in your security group.
%plesk_bin%\amazon\amazon_repair_ip.cmd <old external IP>.
- Reconfigure all external DNS servers used by the hosted domains to match the machine's new external IP.
- Check that all "A" and “PTR” records from the server-wide DNS template point to the new external IP, and check synchronization of changes to all of the domain's DNS zones.