As discussed in -traffic, to mitigate the risk of reaching several rate limits accounted per user account, certcentral1001 and certcentral2001 should use different Let's Encrypt accounts.
Description
Details
Related Objects
- Mentioned In
- T207476: Create production LE accounts
Event Timeline
Change 470403 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[labs/private@master] secret: Add dummy LE ACMEv2 staging private key for certcentral2001
Change 470403 merged by Vgutierrez:
[labs/private@master] secret: Add dummy LE ACMEv2 staging private key for certcentral2001
Change 470404 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[operations/puppet@production] certcentral: Provide unique LE accounts for each certcentral hosts
Change 470404 merged by Vgutierrez:
[operations/puppet@production] certcentral: Provide unique LE accounts for each certcentral hosts
Change 471751 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[labs/private@master] secret: add dummy LE ACMEv2 private keys for certcentral[12]001
Change 471753 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[operations/puppet@production] certcentral: Switch to LE ACMEv2 production environment
Change 471751 merged by Vgutierrez:
[labs/private@master] secret: add dummy LE ACMEv2 private keys for certcentral[12]001
Change 471753 merged by Vgutierrez:
[operations/puppet@production] certcentral: Switch to LE ACMEv2 production environment