You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.
@blckct are you saying to store the .pem inside the s3 bucket alongside the certificate json that currently is put there? or in a location otherwise configured?
In the same bucket would be alright. My use case when I wrote was to automatically generate certificates for local development use and then just download them using cron from bucket. I've done it without lambda but a lambda solution would be nice.
Sure.... I was trying to minimize the count of files that would have to be configured ahead of time (configuration being its own burden). However, I could add a flag defaulted to false that would write to .pems with the same name as the cert object keys, with some hyphenation for the chain parts.
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.The text was updated successfully, but these errors were encountered: