# ARI RFC 9773 Support in community.crypto.acme\_certificate

**URL:** <https://forum.ansible.com/t/ari-rfc-9773-support-in-community-crypto-acme-certificate/45106>\
**Category:** Project Discussions\
**Tags:** acme\
**Created:** [January 14, 2026, 3:09pm UTC](https://forum.ansible.com/t/ari-rfc-9773-support-in-community-crypto-acme-certificate/45106 "2026-01-14T15:09:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TimmayG](https://avatars.discourse-cdn.com/v4/letter/t/e19adc/32.png) [@TimmayG](https://forum.ansible.com/u/TimmayG)\
**Post date:** [January 14, 2026, 3:09pm UTC](https://forum.ansible.com/t/ari-rfc-9773-support-in-community-crypto-acme-certificate/45106/1 "2026-01-14T15:09:03Z")

</div>

Hi All!

I’ve been a user of community.crypto.acme\_certificate to get ACME certs from Lets Encrypt for quite some time.

Now that LE has started issuing ‘shortlived’ certs (certs with a lifetime of 6 days) in LE Prod the recommended method of renewing certificates is with ACME Renewal Info (ARI).

> **[ACME Renewal Information (ARI) Published as RFC 9773](https://letsencrypt.org/2025/09/16/ari-rfc)**
>
> Let’s Encrypt has been proud to work with the IETF to maintain ACME as an open standard since we first developed the technology a decade ago. We’re happy to announce that IETF has published our latest addition to the ACME protocol, ACME Renewal...

> **[Limit Exemptions for Renewals - Rate Limits](https://letsencrypt.org/docs/rate-limits/#limit-exemptions-for-renewals)**
>
> Let’s Encrypt provides rate limits to ensure fair usage by as many people as possible. We believe these rate limits are high enough to work for most people by default. We’ve also designed them so that renewing a certificate almost never hits a rate...

Ive looked through the docs on the ansible module and don’t think I see any ways of using the ARI functionality. Is ARI something that will be introduced into the module?

Thanks  
Tim

---

<div class="post-metadata">

**Author:** ![TimmayG](https://avatars.discourse-cdn.com/v4/letter/t/e19adc/32.png) [@TimmayG](https://forum.ansible.com/u/TimmayG)\
**Post date:** [January 14, 2026, 5:17pm UTC](https://forum.ansible.com/t/ari-rfc-9773-support-in-community-crypto-acme-certificate/45106/2 "2026-01-14T17:17:24Z")

</div>

Im answering my own question , well kinda.

It appears that this feature may be what I’m looking for. If anyone has used this Id like to hear about it!

> **[Parameters - community.crypto.acme\_certificate module – Create SSL/TLS...](https://docs.ansible.com/projects/ansible/latest/collections/community/crypto/acme_certificate_module.html#parameter-include_renewal_cert_id)**
>
> Parameter

Thanks!  
Tim

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [January 14, 2026, 6:06pm UTC](https://forum.ansible.com/t/ari-rfc-9773-support-in-community-crypto-acme-certificate/45106/3 "2026-01-14T18:06:26Z")

</div>

> [@TimmayG](#):
>
> It appears that this feature may be what I’m looking for. If anyone has used this Id like to hear about it!

I’ve tried using it in the beginning (I also implemented it), with mixed results - I added `order_creation_error_strategy` to fix that. With that, I think it worked well.

I’ve switched to the community.crypto.acme\_certificate\_\* modules some time ago though (community.crypto.acme\_certificate\_renewal\_info, community.crypto.acme\_certificate\_order\_create, community.crypto.acme\_certificate\_order\_validate, community.crypto.acme\_certificate\_order\_finalize, community.crypto.acme\_certificate\_deactivate\_authz) since I personally find it easier to implement an ACME certificate role with these than with the somewhat clunky interface of acme\_certificate.