Node Lambda ACME (Let's Encrypt-compatible)
Use AWS Lambda to manage SSL certificates for ACME providers.
How does it work?
This project utilizes AWS Lambda to periodically (once per day) check a set of certificates for expiration, and then if they're about to expire or invalid/missing, it will request a new certificate from the ACME infrastructure.
Certificates are stored in S3, which can easily be configured to send an SNS notification based upon a PUT event into the configured bucket.
Please see the roadmap for a sorted list of upcoming features by priority.
This project requires a little configuration to be used in AWS.
Modify the configuration file with the values needed for your environment:
||Change to production url - https://acme-v01.api.letsencrypt.org if ready for real certificate.|
||Email of user requesting certificate.|
||An S3 bucket to place account keys/config data into. You will need to create this bucket and assign the IAM role to read/write.|
||An S3 bucket to place domain certificate data into. You will need to create this bucket and assign the IAM role to read/write.|
||A folder within the above buckets to place the files under, in case there are other contents of these buckets.|
||Object containing certificate information mapping certificate names to domains.|
ACME v2 Support
acme-directory-url to one of the v2 urls:
and you will be able to request wildcarded certificates.
Follow these steps to get started:
Git-clone this repository.
$ git clone email@example.com:ocelotconsulting/node-acme-lambda.git
Modify configuration (as above).
Create S3 buckets, IAM role, then test locally:
$ npm run local-cert
Package lambda zip:
$ npm run dist
Create lambda by uploading zip, set the handler to "app.handler", and establish your desired trigger (i.e. periodic).
Optional: You can write your certificates to a PEM file by executing:
$ npm run pems
certificate-info field of configuration file
- Certificate names are keys of JSON object, denoting sets of sub/domains to use as SAN names in certificate.
- Value of certificate name keys is array of sub/domains, which can contain either:
- a string (default, looks for route53 hosted zone with 2 levels this is all that is currently supported for v2/wildcard certificates currently)
- or an object, with both
zoneLevelsdefined, allowing hosted zones at levels greater than 2 (i.e.
host.at.longer.domain.comcould specify 4 zone levels, which would require proper NS records in parent Route53 hosted zone or other DNS).