AWS Security ChangesHomeSearch

AWS privateca: Clarify CRL generation events, partitioned CRL structure, and S3 write timing

Service: privateca · 2026-10-07 · Documentation medium

File: privateca/latest/userguide/dochistory.md · Type: logging

Summary

Doc-history entries documenting that AWS Private CA emits a CRL generation event on every generation/attempt (including first CRL, periodic regeneration, retries) plus the CrlUrl event field; that partitioned CRLs also produce a complete (possibly empty) CRL in S3; and a correction on when Private CA first writes CRLs to S3, including the S3 test object used to verify bucket permissions.

Security assessment

The added lines describe certificate revocation (CRL) generation/event monitoring and bucket permission verification, which are security-adjacent audit and revocation behaviors, but they are clarifications of existing documentation rather than a fix for a specific vulnerability or incident.

Evidence

+Clarified when CRL generation events are sent| Clarified that AWS Private CA sends a CRL generation event each time it generates, or attempts to generate, a CRL. This includes the first CRL, periodic regeneration, and retries, not only CRLs that follow a certificate revocation. Also documented the `CrlUrl` field in the event details. For more information, see [Success or failure when generating a CRL](https://docs.aws.amazon.com/privateca/latest/userguide/CloudWatchEvents.html#cwe-CRL).| September 30, 2026

Diff

diff --git a/privateca/latest/userguide/dochistory.md b/privateca/latest/userguide/dochistory.md
index a48b5be..bceab06 100644
--- a//privateca/latest/userguide/dochistory.md
+++ b//privateca/latest/userguide/dochistory.md
@@ -14,0 +15,3 @@ Change| Description| Date
+Clarified when CRL generation events are sent| Clarified that AWS Private CA sends a CRL generation event each time it generates, or attempts to generate, a CRL. This includes the first CRL, periodic regeneration, and retries, not only CRLs that follow a certificate revocation. Also documented the `CrlUrl` field in the event details. For more information, see [Success or failure when generating a CRL](https://docs.aws.amazon.com/privateca/latest/userguide/CloudWatchEvents.html#cwe-CRL).| September 30, 2026  
+Documented the complete CRL written for partitioned CRLs| Added that when a CA uses partitioned CRLs, AWS Private CA also writes a complete CRL to the Amazon S3 bucket. This CRL is always empty if the CA has always used partitioned CRLs. For more information, see [CRL structure](https://docs.aws.amazon.com/privateca/latest/userguide/crl-planning.html#crl-structure).| September 29, 2026  
+Corrected when AWS Private CA first writes a CRL to Amazon S3| Corrected when AWS Private CA first writes a CRL to your Amazon S3 bucket. For a complete CRL, AWS Private CA writes the first CRL shortly after you configure the CRL, even if the CA hasn't issued any certificates. For partitioned CRLs, AWS Private CA writes the CRL for a partition only after the CA issues a certificate that refers to that partition. Also documented the name of the test object that AWS Private CA writes to verify bucket permissions. For more information, see [CRL structure](https://docs.aws.amazon.com/privateca/latest/userguide/crl-planning.html#crl-structure).| September 29, 2026