auto-ssl/lua-resty-auto-ssl

Migrating previous letsencrypt certs to resty-auto-ssl

Open

#144 opened on Jun 16, 2018

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Lua (1,894 stars) (180 forks)batch import
enhancementhelp wanted

Description

Hi there,

We’ve been using a cron’d letsencrypt/certbot script for the last few years and are preparing to move to resty-auto-ssl. We currently have about 1200 certs from our previous implementation. I’m a little nervous about switching to auto-ssl in our production environment given that it can take 2-3 seconds for auto-ssl to provision the cert. My concern is that requests will queue and nginx will crash (we get about 1000 requests per minute).

So my question is if it’s possible to manually “migrate” the existing certs into auto-ssl. We’ll be using the redis store. Would that work and prevent the initial provisioning time for the existing ones?

Any ideas or suggestions?

Thank you!

Contributor guide

Tech stack
None
Domain
securitybackend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of Let's Encrypt and SSLFamiliarity with Redis
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the storage format used by resty auto ssl in Redis (likely keys and values structure). Look at the source code for how certificates are stored and retrieved (e.g., in the Redis storage adapter). Test migration with a small subset of existing certs in a non production environment. Consult the existing comments in issue #144 for any maintainer suggestions or community solutions.