Search overlay panel for performing site-wide searches

Build Your Next Big Thing on Heroku. Sign Up Now!

Automated Certificate Management is Moving to ECDSA Certificates

Heroku Automated Certificate Management (ACM) is moving from Rivest-Shamir-Adleman (RSA) keys to Elliptic Curve Digital Signature Algorithm (ECDSA) keys for the Transport Layer Security (TLS) certificates it issues.

ECDSA certificates are more secure: every connection gets forward secrecy, and the keys are stronger. They’re also the only certificate type allowed in the strictest profile of TLS Ref, which now maintains the TLS guidelines Mozilla used to publish. Starting December 21, 2026, Heroku will begin automatically refreshing ACM certificates to switch them from RSA to ECDSA. By January 29, 2027, all ACM certificates for eligible apps will be ECDSA.

Most apps don’t need to do anything. If our monitoring has detected clients that can’t use ECDSA connecting to your app, we’ll keep the app on RSA certificates automatically and your app will continue working normally for all clients. We’ve also sent you an email with details.

To keep RSA certificates for an app, or to go back to RSA after it switched:

$ heroku features:enable acm-rsa-cert -a example-app
$ heroku certs:auto:refresh -a example-app

To switch an app to ECDSA early:

$ heroku features:enable acm-ec-cert -a example-app
$ heroku certs:auto:refresh -a example-app

Why is ACM moving to ECDSA certificates

ECDSA certificates make connections to your app more secure:

  • Forward secrecy on every connection. Each connection uses its own one-time key, so recorded traffic can’t be decrypted later, even if someone gets the certificate’s private key.
  • Stronger keys. The National Institute of Standards and Technology (NIST) rates an ECDSA P-256 key as strong as a 3072-bit RSA key, and stronger than the 2048-bit RSA keys ACM issues today (NIST’s key size guide, Table 2).
  • A better SSL Labs grade. With an ECDSA certificate, your custom domain no longer offers the older RSA cipher suites, so SSL Labs grades it A instead of B.

Recommended actions

  • Check your clients. Most clients support ECDSA, but some very old devices and software support only RSA. To check a client, open https://ecc256.badssl.com from it. This page uses the same kind of Let’s Encrypt ECDSA certificate that ACM issues. If it loads, the client works with ECDSA. If it doesn’t, keep RSA for the app with the commands above before December 21, 2026.
  • Enable only one of the two features. If an app has both acm-rsa-cert and acm-ec-cert enabled, acm-rsa-cert takes priority and the app gets RSA certificates.
  • Check when a certificate renews. Run heroku certs -a example-app and check the Expires column. ACM renews a certificate about a month before that date.

What changes with this move from RSA to ECDSA

  • Certificates you upload yourself: no change.
  • Apps on Common Runtime: certificates for custom domains. Default *.herokuapp.com domains aren’t affected. They use a shared certificate that Heroku manages separately from ACM.
  • Apps in Fir Private Spaces: certificates for custom domains and the default domain.
  • Apps in Cedar-generation Private Spaces, including Shield Private Spaces: no change. They stay on RSA certificates. To get ECDSA certificates for one of these apps, enable the acm-ec-cert feature with the commands above.
  • Apps with clients that can’t use ECDSA: no change. Before and during the rollout, we check each app’s recent traffic. If we see clients that can’t use ECDSA, we keep the app on RSA certificates and email the app owner. We can’t catch every client, for example one that connects only rarely, so if you’re not sure, check your clients and keep RSA if needed.

Timeline for Automated Certificate Management moving from RSA to ECDSA certificates

Date What happens
November 18, 2026 You can keep RSA certificates, or get ECDSA certificates early, with a Heroku feature
December 21, 2026 Heroku starts moving apps to ECDSA
January 29, 2027 All common runtime apps not flagged into RSA have moved

After your app moves, new domains get an ECDSA certificate right away, and existing certificates switch automatically, at the latest when ACM renews them, about a month before they expire. Each domain keeps serving its current certificate until the new one is ready.

To switch your app’s certificates right away instead of waiting, run:

$ heroku certs:auto:refresh -a example-app

Have questions about ACM moving to ECDSA certificates?

See Heroku Labs: Change Automated Certificate Management Keys on Dev Center, or contact Heroku Support.

Ready to Get Started?

Stay focused on building great data-driven applications and let Heroku tackle the rest.

Talk to A Heroku Rep   Sign Up Now

More from the Author
Software Engineering MTS at Heroku
Heroku Staff

Browse the archives for News or all blogs. Subscribe to the RSS feed for News or all blogs.