We maintain a rather large number (tens of thousands) of certificates on behalf of our customers, and we’re switching our workflow to use Certbot as an Acme client to create and renew certificates. (We don’t need Certbot to manage renewals, we just use it to interact with Let’s Encrypt.)
It would be much simpler for us to not keep track of the private keys needed for renewal requests, and to instead request brand new certificates every three months.
We want to be respectful users of this great service, so we’re wondering if this is okay with Let’s Encrypt (subject to rate limits of course).
Do you mean the ACME account keys here (so you would register new accounts every few months)?
We plan to stick to using just the one account for the foreseeable future (moving the account files from server to server as we deploy new code).
So, you’re just planning to issue the new certificates with a different private key instead of the same private key? That’s already the default behavior of Certbot and is totally unobjectionable.
Excellent! We thought we might need to keep an EBS volume going to move from instance to instance on deployment.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.