What ACME is
ACME, the Automatic Certificate Management Environment, is the standard protocol for getting certificates without a person in the loop. It is defined in RFC 8555. Let’s Encrypt made it popular, and many other public CAs and several internal CAs now support it.
In one exchange, an ACME client on your side:
- creates an account with the CA, identified by a key pair;
- places an order for the names it wants;
- proves control of each name by answering a challenge;
- sends a certificate signing request (CSR) to finalise the order;
- downloads the certificate.
Renewal is the same exchange again. Because no step needs a person, it can run as often as short lifetimes require. Public certificates now last at most 200 days, falling to 47 by 2029, as we explain in certificate lifetimes are falling to 200, 100 and 47 days.
Step 1: choose a client
Pick a client that fits where the certificate is used. Web servers such as Caddy have ACME built in. General clients such as certbot, acme.sh and lego run on a host and write files. Kubernetes has controllers such as cert-manager. Let’s Encrypt keeps a list of ACME clients.
What matters most is whether the client can run a command after renewal to install the certificate and reload the service. Without that, you get a new certificate on disk and an old one served.
Step 2: start with a staging directory
Most CAs offer a staging or test directory that issues untrusted certificates with higher limits. Let’s Encrypt’s is described in its staging environment documentation. Get the whole flow working there first, including install and reload, then switch the directory URL to production.
Step 3: register the account
With Let’s Encrypt, an account needs only a key pair and, optionally, a contact address. Commercial CAs often require External Account Binding, defined in RFC 8555 section 7.3.4, which links the ACME account to your paid account with a key ID and secret from the CA’s portal. Store that secret like any other credential, not in the client’s configuration file in plain text if you can avoid it.
Step 4: choose a challenge type
Let’s Encrypt’s challenge types page explains the options well. In short:
- HTTP-01 puts a file on the web server at a known path, and works only on port 80. It is the simplest choice for public web servers but cannot issue wildcard certificates.
- DNS-01 puts a TXT record under
_acme-challengein your DNS. It works for servers that are not reachable from the internet and is the only one that can issue wildcards. It needs DNS API access, so give the client the narrowest rights you can, or delegate the challenge name with a CNAME to a zone used only for this. - TLS-ALPN-01, defined in RFC 8737, answers on port 443 during the TLS handshake. It suits servers where port 80 is closed, but fewer clients support it.
Domain validation reuse is shrinking. From March 2029 public CAs may reuse a domain check for only 10 days, so expect a challenge on nearly every renewal and make sure it is fully automated.
Step 5: lock it down with CAA
A CAA record (RFC 8659) in your DNS says which CAs may issue for your domain. RFC 8657 adds accounturi and validationmethods, so you can limit issuance to your own ACME account and to the challenge types you use. The Baseline Requirements oblige public CAs to process both parameters from 15 March 2027. Add CAA records once your issuance works, so a mistake does not block it.
Step 6: install, reload and check
Use the client’s deploy hook to copy the certificate and key to the right place, set file permissions, and reload the service. Then connect to the endpoint by hostname and check that it serves the new certificate. If the check fails, alert and keep the previous certificate available so you can roll back.
Step 7: schedule renewals properly
Do not renew on a fixed number of days. Let’s Encrypt has announced that its default certificates will drop from 90 days to 64 days on 10 February 2027 and to 45 days on 16 February 2028, and says that renewing at a fixed 60 days will no longer be enough.
- Use ACME Renewal Information (RFC 9773) if your client and CA support it. The CA tells the client when to renew, including early if a certificate must be replaced.
- Without ARI, renew at about two thirds of the certificate’s lifetime, worked out from the certificate itself.
- Run the client at least daily, at a random minute, so it checks often without hitting the CA at the same moment as everyone else.
Step 8: monitor for the renewal that did not happen
Automation fails quietly. Alert when a served certificate passes two thirds of its lifetime, which means a renewal should already have happened. Send that alert somewhere a team will see it. Our checklist for stopping expiry outages covers the rest.
Where clm.mt fits
We build clm.mt, so this is our product. Its agents act as the ACME client, deploy the certificate to the service and check what is served afterwards. ACME with DNS-01 and ACME Renewal Information is supported and tested against a real ACME server. Presets for public CAs, including Let’s Encrypt, are in preview until production issuance from each is recorded, and External Account Binding for commercial CAs has passed contract tests only. See the integrations page for the current list, the docs for setup and pricing for the plans.
Sources
- IETF, RFC 8555: Automatic Certificate Management Environment (ACME).
- IETF, RFC 8737: ACME TLS-ALPN-01 challenge.
- IETF, RFC 8659: DNS Certification Authority Authorization (CAA) and RFC 8657: CAA accounturi and validationmethods.
- IETF, RFC 9773: ACME Renewal Information (ARI).
- Let’s Encrypt, Challenge Types, Staging Environment and Decreasing Certificate Lifetimes to 45 Days.
- CA/Browser Forum, TLS Baseline Requirements, sections 4.2.1 and 4.2.2.1.2.