• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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