• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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