从自我管理的 Let's Encrypt 到 AWS Certificate Manager

From self managed Let's Encrypt to AWS Certificate Manager

我一直在为域管理 Let's Encrypt 的 SSL 证书。

现在我要迁移到 Amazon API 网关。我将使用 AWS Certificate Manager 为根域和一系列子域生成 HTTPS 证书。

如果我进行转移,与我的域关联的当前 HTTPS 证书会发生什么情况。如果浏览器突然开始看到某个域的新 HTTPS 证书,之前他们一直在为该域获取不同的 HTTPS 证书,这会是个问题吗?

此外,一旦我进行了转换,我该如何处理我当前的(手动管理的)Let's Encrypt 证书?有办法永久作废吗?

您可以同时拥有同一个域的多个有效证书。从一个证书颁发者转移到另一个证书颁发者应该不会造成问题。 这也意味着如果您创建新证书,旧证书仍然可以使用,除非它已经过期。

You can have multiple valid certificates for the same domain at the same time. Moving from one certificate issuer to another should not cause a problem.

Toby Osbourn

SSL certificates don’t last forever, most of them need to be renewed on a yearly cycle and occasionally you will want to change the type of the SSL certificate mid-cycle.

由于您要更换证书,建议您备份现有的证书。

备份旧证书后,只需用新证书覆盖 .crt.key 文件即可。然后,重新加载您的 Web 服务器,以便它知道查看这些新证书,然后您就可以开始了。

如果您有兴趣了解有关如何使用 Amazon Certificate Manager (ACM) 生成 SSL 证书的更多信息,我建议 Barguzar, A. (July 2018). Building Serverless Python Web Services with Zappa。在那里可以阅读一份很好的分步指南。请参阅下面的摘录:

ACM is a service that manages and creates SSL/TSL certificates for AWS-based services and applications. An ACM certificate works with multiple domain names and subdomains. You can also use ACM to create a wildcard SSL.

ACM is strictly linked with AWS Certificate Manager Private Certificate Authority (ACM PCA). ACM PCA is responsible for validating the domain authority and issuing the certificate.