flywithu/community-catalog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
community-catalog/templates/letsencrypt/2
History
Jan B 871a28d5cd Update Let's Encrypt template to v0.3.0 (#165) 
Changelog:
- Added support for storing certificate and private key in host path,
named volume or Convoy volume
- Updated ACME library fixing issues for Dyn and Route53
2016-06-01 10:38:57 -07:00
..
docker-compose.yml
Update Let's Encrypt template to v0.3.0 (#165)
2016-06-01 10:38:57 -07:00
rancher-compose.yml
Update Let's Encrypt template to v0.3.0 (#165)
2016-06-01 10:38:57 -07:00
README.md
Update Let's Encrypt template to v0.3.0 (#165)
2016-06-01 10:38:57 -07:00

README.md

Let's Encrypt Certificate Manager

About

The Let's Encrypt Certificate Manager obtains a free (SAN) SSL Certificate from the Let's Encrypt CA and adds it to Rancher's certificate store. Once the certificate is created it is scheduled for auto-renewal 14-days before expiration. The renewed certificate is propagated to all applicable load balancer services.

Usage

  1. Accept the terms of service.
  2. Select the API version to use. The Sandbox API should be used for testing purposes.
  3. Fill in your email address.
  4. Enter the name used for storing the certificate in Rancher and volumes. Any existing certificate by that name will be updated.
  5. Enter one or more domain names. The first domain will be used as the Common Name property of the certificate.
  6. Optionally, specifiy the host path or volume name in which to store certificate and private key (Usage).
  7. Fill in the required credentials for the provider. AWS Route 53 requires IAM permissions as specified here.

If you want the certificate to be automatically renewed, leave the service running. Otherwise you may remove the service once the certificate has appeared in Rancher's certificate store.

Suggestions & issue reports

Please submit suggestions or any issues you find to the rancher-letsencrypt GitHub repo.