Why appliances are the hard part
On an ordinary Linux server, an ACME client renews the certificate and reloads the web server, a pattern we walk through in automating certificate renewal with ACME. Load balancers, firewalls, VPN gateways and application delivery controllers are different:
- You usually cannot install your own software on them, so there is no ACME client on the box.
- The certificate, key and chain are uploaded through a web console or an API, and then bound to a listener, virtual server or profile.
- They often run in pairs or clusters, and every member must get the new certificate.
- One device may serve dozens of names, each with its own certificate selected by hostname.
- They sit in front of everything else, so a mistake affects many services at once.
That is why the appliance certificates are so often the ones still renewed by hand, and why shorter lifetimes, which we cover in certificate lifetimes are falling to 200, 100 and 47 days, hit them first.
Cloud load balancers
Cloud providers have their own certificate services, and how renewal works depends on where the certificate came from.
AWS
AWS Certificate Manager manages renewal of the certificates it issued that are in use, for example on a load balancer: automatically when they use DNS validation, otherwise by emailing you. Certificates you import into ACM are not renewed by ACM. You must reimport a renewed certificate before expiry, which keeps the same certificate ARN and the load balancer listeners that use it.
Azure
Azure Application Gateway can take its certificates from Azure Key Vault. Its instances poll Key Vault at four-hour intervals for a renewed version, and Microsoft recommends referencing the secret without a version so the gateway picks up new ones. If the gateway loses access to the vault, it disables the listener, so monitor that access as well.
In both clouds the job is the same: put the renewed certificate where the service reads it, then confirm the listener serves it.
On-premises appliances
Most modern appliances have a management API. Automating them follows the same steps each time:
- Get the certificate. Renew through ACME or your CA on a separate host, or generate the key on the appliance and send its CSR to the CA, if you prefer the key never to leave it.
- Upload it with a new name. Upload the certificate, key and chain as a new object, for example with the expiry date in the name, rather than overwriting the old one.
- Switch the binding. Point the listener or profile at the new certificate, on every member of the cluster or through the cluster’s own sync.
- Check what is served. Connect to each name on the device and confirm it presents the new certificate and chain.
- Keep the old one for a while. If the check fails, switch the binding back. Remove old certificates only after the new one has served cleanly.
Give the automation its own API account, with only the rights it needs to manage certificates, and keep those credentials in a secrets manager.
TLS inspection
Firewalls that inspect TLS traffic use a CA of their own to create certificates for the sites users visit. That CA certificate must be trusted by every client and has its own expiry date, often years away and easy to forget. Record it in your inventory with a clear owner, and plan its replacement, including distributing the new CA certificate to clients, well before it expires.
Fewer places to break
Every appliance that terminates TLS is one more certificate to renew. Where you can, terminate TLS in fewer places, use the cloud provider’s own certificates for cloud load balancers, and keep a list of every device that still needs a manual step, so you know exactly where the risk sits. Discovery is how you find the ones not yet on that list.
Where clm.mt fits
We make clm.mt, so this is about our own product, and the support levels matter here. Deployment to AWS Certificate Manager for Application and Network Load Balancer listeners, and to OCI Load Balancer, is supported after tests on the real services. Connectors for F5 BIG-IP, Citrix NetScaler ADC, FortiGate, Palo Alto Networks firewalls and Azure Key Vault are in preview: they have passed contract tests against the vendors' APIs, not yet a run on a customer’s device, so start with a staging device.
The integrations page has the full list with limits, the docs explain setup and pricing lists the plans.
Sources
- AWS, Managed certificate renewal in AWS Certificate Manager and Reimport a certificate.
- Microsoft, TLS termination with Azure Key Vault certificates.