• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question What is the best practice for cloning a Plesk instance on AWS ec2

peteeeeeee

New Pleskian
My site is hosted in AWS ec2, after a certain amount of time, the site traffic growing up, so I decided to add one more ec2 and site behind a load-balancer to distribute network or application traffic.
I create an image from the original ec2 and create the second ec2 instance, it is working fine.

Just wonder any best practices for this cloning action.
  1. How can I generate a new domain for the second instance
    I was able to access the Plesk admin panel via Plesk generated domain with https(https://xxx-xxx.1-2-3-4.plesk.page:8443/), but the cloned instance, I can only access it via IP address(5.6.7.8:8443)
  2. I found Plesk license keys are the same between two instances, any way I can update it, or should I update it? (not a crucial issue though)
  3. Any action I should take after cloning the image with Plesk?
 
Back
Top