Search for:

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

How to deploy Parallels Plesk Panel 11 on Amazon EC2 service (Windows)

Article ID: 114947, created on Oct 12, 2012, last review on Aug 12, 2014

  • Parallels Plesk 11.0 for Windows
  • Parallels Plesk 11.5 for Windows


How to deploy Parallels Plesk Panel 11 on Amazon EC2 service (Windows)

KB article for Linux version of Plesk.


Release Notes

To simplify Parallels Plesk Panel (PP) 11 provisioning on cloud infrastructure providers (including service providers offering dedicated servers, VPS, or IaaS), Parallels introduces the PP 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:

Steps to Deploy

  1. Log in 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" (Windows) 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 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 Parallels Plesk Panel: KB391 Which ports need to be opened for all Parallels Plesk Panel 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).

  4. Read the User End License Agreement and AWS Customer Agreement and click Assept Terms and 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. 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.

  8. (Optional) Apply Elastic IP:

    a. Attach your Elastic IP to the instance and wait while it configures.

    b. RDP to the instance.

    c. Run %plesk_bin%\amazon\amazon_setup_ip.cmd

    (If you do not use Elastic IP, this step is not needed.)

  9. Use the DNS (or IP from the DNS) from the instance information frame to RDP to the new instance.

    The %plesk_bin%\amazon\amazon_prepare_instance.cmd script, which is executed upon startup of the first instance, prepares your instance with the next steps:

    a. Execute the Parallels Plesk Panel cloning procedure.

    b. Install Parallels Plesk Panel Micro-Updates.

    c. Set up the new IP (run %plesk_bin%\amazon\amazon_setup_ip.cmd).

    d. Update the key (PowerPack version only).

    You can check the log of this script execution:


  10. Now you can access your Plesk Panel instance from your AWS Marketplace subscriptions list by pressing the Access Software link

    or with https://<instance public DNS or IP>:8443. Use Administrator’s credentials to login into the Panel for first time.

IP Changing

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:

  1. RDP to the instance.
  2. Download amazon_repair_ip.cmd from this KB and place it in %plesk_bin%\amazon\. Check this command file. Please pay attention to the PASSIVE_PORT_RANGE value. It must be the same as for FTP-passive-port-range in your security group.
  3. Run %plesk_bin%\amazon\amazon_repair_ip.cmd <old external IP>.
  4. Reconfigure all external DNS servers used by the hosted domains to match the machine's new external IP.
  5. 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.


40b42e819ce59dca8c0661c3644f1ce4 56797cefb1efc9130f7c48a7d1db0f0c c81e59b61af9dca603ba03b14aabe968 42844a8183c58f5bd71c7d59929707e6 f4c89357a6ff7298f273cb70f9d95452 51438e1dfe1e98e6ad3bf2ff9709bbbb

Was this article helpful?
Tell us how we may improve it.
Yes No
Server Virtualization
- Parallels Cloud Server
- Parallels Containers for Windows 6.0
- Parallels Virtuozzo Containers
- Parallels Automation
- Parallels Automation for Cloud Infrastructure
- Parallels Business Automation Standard
- Parallels Virtual Automation
- Parallels Plesk Panel Suite
- Web Presence Builder
- Parallels Plesk Automation
- Parallels Small Business Panel
- Value-added Services for Hosters
- Parallels Partner Storefront
Services & Resources
- Cloud Acceleration Services
- Professional Services
- Support Services
- Training & Certification