I’ve been seeing a number of issues coming up lately that break workflows because of invalid or self signed SSL certificates.
Fortunately, there is a simple (and free) solution to this issue in the form of Let’s Encrypt. From the Let’s Encrypt website:
Let’s Encrypt is a free, automated, and open certificate authority (CA), run for the public’s benefit. It is a service provided by the Internet Security Research Group (ISRG).
We give people the digital certificates they need in order to enable HTTPS (SSL/TLS) for websites, for free, in the most user-friendly way we can. We do this because we want to create a more secure and privacy-respecting Web.
The key principles behind Let’s Encrypt are:
- Free: Anyone who owns a domain name can use Let’s Encrypt to obtain a trusted certificate at zero cost.
- Automatic: Software running on a web server can interact with Let’s Encrypt to painlessly obtain a certificate, securely configure it for use, and automatically take care of renewal.
- Secure: Let’s Encrypt will serve as a platform for advancing TLS security best practices, both on the CA side and by helping site operators properly secure their servers.
- Transparent: All certificates issued or revoked will be publicly recorded and available for anyone to inspect.
- Open: The automatic issuance and renewal protocol will be published as an open standard that others can adopt.
- Cooperative: Much like the underlying Internet protocols themselves, Let’s Encrypt is a joint effort to benefit the community, beyond the control of any one organization.
So, I thought it would be useful to put together a one-stop shop for how to install Let’s Encrypt on different environments and cloud hosting. I’m asking everyone who knows where a good tutorial on installing Let’s Encrypt to either IM me or reply to this post with the following:
- Environment/Cloud Provider (e.g. Ubuntu, AWS, etc)
- URL to the tutorial
I will compile them and publish them here.