node-acme-lambda icon indicating copy to clipboard operation
node-acme-lambda copied to clipboard

Use AWS Lambda to manage SSL certificates for ACME providers like Let's Encrypt.

Results 15 node-acme-lambda issues
Sort by recently updated
recently updated
newest added

Avoids these sporadic errors, which are caused by attempting to issue certs before records have propagated to all Route53 servers: ``` { "type": "urn:ietf:params:acme:error:orderNotReady", "detail": "Order's status (\"invalid\") is not...

We've had this running for a couple years now without issue, but it seems we are now getting 403 Forbidden on the finalize step when the certificates go to renew....

I am using this lambda function to generate letsencrypt certificate and then put them in s3 bucket so later when I bake images it would pick the certificate from s3....

Whilst experimenting with this project; I've hit a brick wall where v2 support will be totally broken for most actions when talking to ACME server (especially via Let's Encrypt's Boulder)....

First, thanks @larryboymi for this project, it made the job *much* easier! I got this project working using Windows/VSCode. I upgraded all dependencies to the latest package versions as of...

At least in my certs (V2) cert.notBefore & cert.notAfter are always undefined.

Hi, I'm doing some small reading, and noticed that the client doesn't actually send a user-agent with (except for "superagent-version" which doesn't help LE or others) and did some quick...

Thanks for this project, I see there are tests, but they're not automated so here we go. Passing on the first run :tada:. Edit: oh, nevermind, I see you're using...

From what I see currently you have to run `npm run pems` to get ready to use certificates, it would be nice to have that as a result of Lambda.

Add support for explicitly specifying the AWS Zone ID in the hash containing a domain name.