Heroku
Heroku Automated Certificate Management moves to ECDSA certificates December 21, 2026
32 days left — Dec 21, 2026
- What stops working
- Starting December 21, 2026 Heroku's Automated Certificate Management (ACM) issues ECDSA P-256 certificates instead of RSA, migrating apps in stages through January 29, 2027. Clients, SDKs or embedded devices that cannot negotiate an ECDSA certificate fail their TLS handshake against the app once its certificate renews.
- Who is affected
- Owners of Heroku apps with custom domains on the Common Runtime, and custom or default domains in Fir Private Spaces, whose users include older clients.
- Official migration path
- Before December 21, 2026 run 'heroku features:enable acm-rsa-cert -a <app>' on any app that must keep RSA; otherwise accept ECDSA. Uploaded certificates and Cedar Private Spaces are unaffected.
- What the official path does not cover
- Someone has to inventory client TLS capabilities per app (legacy Java, IoT devices, payment terminals, old Android), decide per app, and watch for handshake failures during the staged rollout to January 29, 2027.
- Source
- Heroku Changelog item 3898: ECDSA certificates for ACM (effective Nov 17, 2026) · announced 2026-11-17 · verified 2026-11-18
Need this done before Dec 21, 2026?
Fixed price, fixed scope, fixed date. From $4,000 for a single integration or workflow; you get the working replacement, the code, and a before/after check. Quote within one business day.
One short form (company, email, what runs on this, needed-by). Reply within one business day.
Not ready yet? Get an email when Heroku deadlines approach · Firms: get listed for Heroku work.
Spotted a wrong date? Report it — corrected with the source within one business day.