• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question let's encrypt for AWS route53 DNS domain

Seba

Basic Pleskian
Hi all,

I have 2 hosted zone for 2 domains that are setup with AWS route 53 and each zone setup the domain to point to 2 server, each server contain a clone of these domains, till here everything is OK.

How can I use let's encrypt to secure those domains? can I simply use let's encrypt in both servers and secure each domain independently? and then 60 days after the certificate issue Plesk will renew the certificate?
 
Back
Top