I implemented ACME API V2 for creating certificates of our customer domains.
We have one account for calling all requests to ACME API.
Because of new order limits in V2 API (300 new order per 3 hours) we have create more accounts (for example 15).
Should we store information about which certificates has been created via which account?
For example:
For domain.com we create certificate via API from account Account1. This certificate will expire after 3 months. Then we create new certificate for domain.com. Do we have to create new certificate from Account1, or we can create certificate from any account?
You don’t have to use the same account the next time. [1]
Consider also whether you would be better off applying for a rate limit override, rather than creating many accounts.
1. There’s one exception to this, and that is if the domain has a CAA record and specifies an accounturi. (Not yet deployed to Let’s Encrypt production, but will be at some point).
Yes, the application form is linked on https://letsencrypt.org/docs/rate-limits/. I think it’s likely that Let’s Encrypt would prefer you use 1 account rather than 15.
This question and many more like it have answers in our Integration Guide. You may find this section especially relevant Integration Guide - Let's Encrypt
And @_az is correct, you can apply for rate limit adjustments on the linked page.
