Automating ACMEv2 Certificate Management on BIG-IP
I have questions regarding concerns when installing the ACME client directly on BIG-IP.
- Is it necessary to install and configure the ACME client each time a new load balancer is deployed?
- When equipment fails or is replaced, is it necessary to reinstall and reconfigure it on the replacement unit?
- Are there any ACME-related items that should be backed up in preparation for failures?
- If there are many load balancers, is running the ACME client within BIG-IP unsuitable?
- Is it necessary to install and configure the ACME client each time a new load balancer is deployed?
[K] Yes.
- When equipment fails or is replaced, is it necessary to reinstall and reconfigure it on the replacement unit?
[K] Yes.
- Are there any ACME-related items that should be backed up in preparation for failures?
[K] This is described in the project page: https://github.com/f5devcentral/kojot-acme, but mostly you need to save your config files in /shared/acme. The client uses these config files as "provider configs". instructing how to talk to the ACME server, and uses the data group entries as certificate configs, instructing which certificates to manage.
- If there are many load balancers, is running the ACME client within BIG-IP unsuitable?
[K] I assume you're asking if it's okay to run on one or a few BIG-IPs, vs. all of them. If that's the case, understand that the HTTP-01 validation is done at the BIG-IP that hosts the application, so you need the client on the BIG-IP that needs ACME cert renewal.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)