What is the ACME protocol?
ACME (Automatic Certificate Management Environment) is an open protocol, standardised in RFC 8555, that automates the entire process around digital certificates: ordering, domain validation, issuance and renewal. The protocol was developed for Let's Encrypt, which has used it to make free TLS certificates the standard on the web. The manual work, where an administrator orders, retrieves and installs certificates by hand, is replaced by a client that talks directly to a Certificate Authority and handles everything itself.
How does ACME work in practice?
The core of ACME is that the client must prove control over the domain before the CA issues a certificate. This happens via so-called challenges:
- HTTP-01: The CA asks the client to place a specific file at a specific address under the domain. If the CA can fetch the file, control is proven. Simple, but it requires the server to be reachable from the internet on port 80.
- DNS-01: The client creates a specific TXT record in the domain's DNS. This also works for internal servers and wildcard certificates, but requires the client to be able to update DNS automatically.
Once a challenge is passed, the CA issues the certificate and the client installs it. The whole process takes seconds and is repeated automatically, typically when a third of the lifetime remains.
Why has automatic renewal become necessary?
The maximum lifetime of certificates has been shortened in several rounds, and the industry is moving towards lifetimes so short that manual renewal is effectively impossible to operate reliably. A forgotten certificate means downtime, browser warnings and lost trust, and it typically hits on a Friday evening. We have described the entire journey from issuance to expiry in the article on the TLS certificate lifecycle. The point is simple: when renewal has to happen frequently and flawlessly, automation is no longer a convenient add-on but a prerequisite for stable operations.
ACME in the enterprise: more than Let's Encrypt
Many associate ACME with free certificates for public websites, but the protocol is vendor-neutral. Commercial CAs offer ACME endpoints, and internal CAs in a PKI can also speak ACME, for example via ACME services on top of Active Directory Certificate Services or dedicated PKI platforms (see Microsoft Learn for documentation of the certificate services). This means internal servers, load balancers and containers can renew their certificates just as automatically as a public website. Key protection belongs in this picture too: the CA's own keys should live in an HSM, so the automation rests on a secure foundation. If you want to dig deeper into how automated certificate management and key protection work together, we have collected it all in the e-book PKI and HSM in practice.
How MI Support IT can help
We have many years of specialist experience with enterprise PKI and certificate automation and help both SMBs and larger organisations adopt ACME, from choosing clients and CAs to monitoring renewals. Read more under PKI Management, or contact us for a conversation about your certificate operations.