What ACM renews on its own
Application and Network Load Balancer listeners take their certificates from AWS Certificate Manager (ACM). Whether ACM renews them depends on where the certificate came from. According to managed renewal in ACM:
- Issued by ACM with DNS validation: renewed automatically while it is in use, for example on a load balancer. The certificate ARN stays the same, so the listener keeps working.
- Issued by ACM with email validation: ACM emails the domain contacts, and someone has to approve the renewal.
- Imported into ACM: not renewed by ACM. This includes certificates from any other CA.
- Issued through the ACM ACME endpoint: the ACME client renews them, and AWS documents that they cannot be used with Elastic Load Balancing, because AWS does not hold the private key.
ACM certificates are regional, so a certificate in each region has to renew on its own.
Rotating an imported certificate
If your load balancer uses a certificate from another CA, for example an OV or EV certificate, you renew it outside AWS and then reimport it into the same ACM certificate ARN before it expires. Reimporting keeps the associations, so listeners that reference the ARN serve the new certificate without a change. The key type and size cannot change on reimport.
Afterwards, check the served certificate on each listener and on each SNI name. A listener can hold several certificates, and the one a client receives depends on the hostname it asks for.
Where it gets hard
- Imported certificates are easy to forget. ACM shows them, but nothing renews them for you.
- Email validation. Approvals sent to mailboxes nobody reads are a classic cause of outages, described in how to stop certificate expiry outages.
- Several accounts and regions. Every account and region has its own list of certificates.
- Lifetimes. Certificates from other CAs are moving toward 47 days, as covered in certificate lifetimes are falling to 200, 100 and 47 days, so reimports become frequent.
How clm.mt handles ALB and NLB
clm.mt renews the certificate from your chosen CA, imports or reimports it into ACM for the listeners that use it, checks the served certificate and can restore the previous one. Other services that consume ACM certificates, such as CloudFront and API Gateway, are not covered by this test.
clm.mt status
Supported for AWS ACM for ALB / NLB. Real service rotation and recovery. Other ACM consumers are not validated. See the integrations board for every tested scope, and the documentation to plan a pilot.
Other platform guides
- AD CS certificate autoenrollment and auto renewal
- Azure Key Vault certificate auto renewal, and when it does not happen
- F5 BIG-IP SSL certificate renewal automation
- FortiGate ACME certificates and automatic renewal
- IIS SSL certificate auto renewal on Windows Server
- Kubernetes certificate management and TLS Secret renewal
- NetScaler ADC SSL certificate renewal and update
- NGINX SSL certificate auto renewal with ACME
- Palo Alto firewall certificate renewal automation