AWS Security ChangesHomeSearch

AWS privateca: AWS Private CA: clarify CRL generation events and CrlUrl detail field

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

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

Summary

Rewrites the CRL event section to explain that AWS Private CA emits events on every CRL generation attempt (initial, post-revocation, pre-expiration regeneration, and retries), and adds the CrlUrl field to example success and failure event payloads in the CloudWatch detail object.

Security assessment

The change documents event/monitoring behavior for certificate revocation list generation, including failure reasons such as 'Failed to write CRL to S3. Check your S3 bucket permissions.', which supports operating and alerting on CRL publication (a PKI revocation-availability control). It does not disclose or fix a specific vulnerability, so it is security-relevant documentation rather than an incident response.

Evidence

+As a result, you can expect periodic CRL generation events, even when you don't revoke any certificates. A failure event can result from a scheduled regeneration, not only from a certificate revocation. For more information about CRLs, see [Set up a CRL for AWS Private CA](./crl-planning.html).

Diff

diff --git a/privateca/latest/userguide/CloudWatchEvents.md b/privateca/latest/userguide/CloudWatchEvents.md
index 7f1c867..95188d4 100644
--- a//privateca/latest/userguide/CloudWatchEvents.md
+++ b//privateca/latest/userguide/CloudWatchEvents.md
@@ -139 +139,16 @@ On success, the operation returns the ARNs of the CA and of the revoked certific
-These events are triggered by the [RevokeCertificate](https://docs.aws.amazon.com/privateca/latest/APIReference/API_RevokeCertificate.html) operation, which should result in the creation of a certificate revocation list (CRL).
+AWS Private CA sends these events each time it generates, or attempts to generate, a certificate revocation list (CRL). This includes both complete and partitioned CRLs. AWS Private CA generates a CRL in the following cases:
+
+  * After you configure a CRL for a CA, AWS Private CA writes the first CRL even if you haven't revoked any certificates.
+
+  * After you revoke a certificate by using the [RevokeCertificate](https://docs.aws.amazon.com/privateca/latest/APIReference/API_RevokeCertificate.html) operation, AWS Private CA generates a CRL.
+
+  * Before the current CRL expires, AWS Private CA begins to regenerate the CRL halfway through the validity period that you set with `ExpirationInDays`. If `ExpirationInDays` is 1, AWS Private CA regenerates the CRL every 6 hours.
+
+  * After a CRL generation fails, AWS Private CA retries the generation.
+
+
+
+
+As a result, you can expect periodic CRL generation events, even when you don't revoke any certificates. A failure event can result from a scheduled regeneration, not only from a certificate revocation. For more information about CRLs, see [Set up a CRL for AWS Private CA](./crl-planning.html). For instructions on changing the CRL validity period, see [Updating a CA's revocation configuration (console)](./PCAUpdateCA.html#update-revocation).
+
+The `detail` object of each event includes `CrlUrl`, the URL of the CRL that AWS Private CA generated or attempted to generate. For a partitioned CRL, `CrlUrl` is the URL of that partition's CRL.
@@ -143 +158 @@ These events are triggered by the [RevokeCertificate](https://docs.aws.amazon.co
-On success, the operation returns the ARN of the CA associated with the CRL.
+On success, the event includes the ARN of the CA that's associated with the CRL.
@@ -158 +173,2 @@ On success, the operation returns the ARN of the CA associated with the CRL.
-          "result":"success"
+          "result":"success",
+          "CrlUrl":"http://amzn-s3-demo-bucket.s3.us-east-1.amazonaws.com/crl/11223344-1234-1122-2233-112233445566.crl"
@@ -180 +196,2 @@ Check your Amazon S3 bucket permissions if this error occurs.
-          "reason":"Failed to write CRL to S3. Check your S3 bucket permissions."
+          "reason":"Failed to write CRL to S3. Check your S3 bucket permissions.",
+          "CrlUrl":"http://amzn-s3-demo-bucket.s3.us-east-1.amazonaws.com/crl/11223344-1234-1122-2233-112233445566.crl"
@@ -202 +219,2 @@ Retry the operation if this error occurs.
-          "reason":"Failed to write CRL to S3. Internal failure."
+          "reason":"Failed to write CRL to S3. Internal failure.",
+          "CrlUrl":"http://amzn-s3-demo-bucket.s3.us-east-1.amazonaws.com/crl/11223344-1234-1122-2233-112233445566.crl"
@@ -224 +242,2 @@ To troubleshoot this error, check your [CloudWatch metrics](https://docs.aws.ama
-          "reason":"Failed to generate CRL. Internal failure."
+          "reason":"Failed to generate CRL. Internal failure.",
+          "CrlUrl":"http://amzn-s3-demo-bucket.s3.us-east-1.amazonaws.com/crl/11223344-1234-1122-2233-112233445566.crl"