Skip to content
TrustList
News

Heroku ACM switches new certificates from RSA to ECDSA P-256 on 21 December

Editorial

By TrustList Editorial

From 21 December 2026 Heroku Automated Certificate Management issues ECDSA P-256 keys instead of RSA, migrating apps in stages to 29 January 2027; apps with older clients can opt out.

About Heroku ACM switches new certificates from RSA to ECDSA P-256 on 21 December

Heroku ACM switches new certificates from RSA to ECDSA P-256 on 21 December

17 November 2026: Heroku has told customers that its Automated Certificate Management (ACM) service will stop issuing RSA keys for TLS certificates and issue Elliptic Curve Digital Signature Algorithm (ECDSA) P-256 keys instead. The switch starts on 21 December 2026. Heroku will move apps over in stages through 29 January 2027, and an individual certificate changes type the next time ACM issues it after its app has been migrated.

Not yet independently verified. The changelog page shows an effective date of 17 November 2026 but no separate publication time. We have not tested which older clients fail with ECDSA certificates; Heroku's own page leaves that for app owners to check. We will update this when it can be confirmed, and remove this note.

Which apps and domains are covered

The change applies to custom domains on Common Runtime apps, and to both custom and default domains on apps in Fir Private Spaces. Three groups are outside it. Certificates you upload yourself are untouched, because ACM did not issue them. Apps in Cedar-generation Private Spaces, including Shield Private Spaces, are also left alone, although they can already ask for ECDSA certificates by enabling the acm-ec-cert feature. Default herokuapp.com domains on the Common Runtime are not affected either.

The practical effect is that nothing happens on a single fixed day for each app. The announcement describes a staged migration, so one account may see some apps move in December and others in January, and the new key type only appears when a certificate is next issued or renewed.

Keeping RSA if a client cannot use ECDSA

Heroku warns that some of an app's clients may not be able to use ECDSA certificates. If any of yours fall into that group, you can keep RSA certificates for that app by enabling the acm-rsa-cert feature before 21 December 2026. The command Heroku gives is heroku features:enable acm-rsa-cert -a followed by the app name. Heroku points to its documentation page on changing ACM keys for the full procedure.

What an admin should do before 21 December

Start with an inventory. List the apps on your account that use ACM for a custom domain, and separate them from apps that use uploaded certificates, which will not change. For each ACM app, think about who connects to it: browsers, mobile apps, partner integrations, webhooks sent by third parties, monitoring probes, embedded devices and older command-line tools. Anything built on a very old TLS stack, or pinned to an RSA certificate or key, is the likeliest to break.

Where you control the client, test it against an ECDSA endpoint in a staging app before the date. Where you do not, such as a customer's legacy system, decide whether to enable the acm-rsa-cert feature for that app now, so the opt-out is in place before the first migration. Record the decision in your change log so that whoever renews domains next knows why one app differs.

After the migration window, check the certificate on each custom domain with an external TLS checker or the openssl command line, and confirm that the key type shows as an elliptic curve P-256 key. Monitor error rates for a few days around each app's renewal, because a failure caused by an unsupported client will show up as failed handshakes rather than as an application error.

Our platform-as-a-service category lists hosting platforms that handle certificates in a similar way.

What the announcement does not say

Heroku does not give the date on which each app will be migrated, and it does not list the clients that cannot use ECDSA. Treat the 29 January 2027 end date as the point by which every ACM-managed certificate in scope should have been reissued.

Related on TrustList:

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in