AWS Security ChangesHomeSearch

AWS privateca: Clarify CRL S3 permission test object and write timing

Service: privateca · 2026-09-30 · Documentation medium

File: privateca/latest/userguide/crl-planning.md

Summary

Rewrites CRL planning guidance to explain the acm-pca-permission-test-key object used to verify S3 write permission, and when complete vs partitioned CRLs are written to the bucket.

Security assessment

The change documents certificate revocation list (CRL) behavior and the S3 permission-verification object, which relates to revocation infrastructure and bucket ACLs, but it is explanatory guidance rather than a fix for a specific vulnerability.

Evidence

+When you configure a CRL for a CA, AWS Private CA writes a test object to the Amazon S3 bucket to verify that it has permission to write to the bucket. The object is named `acm-pca-permission-test-key`, or `acm-pca-permission-test-key-private` if `S3ObjectAcl` is set to `BUCKET_OWNER_FULL_CONTROL`.

Diff

diff --git a/privateca/latest/userguide/crl-planning.md b/privateca/latest/userguide/crl-planning.md
index 1985ae6..947bdca 100644
--- a//privateca/latest/userguide/crl-planning.md
+++ b//privateca/latest/userguide/crl-planning.md
@@ -96 +96,5 @@ CRLs have the following format:
-The CRL will only be deposited in Amazon S3 after a certificate has been issued that refers to it. Prior to that, there will only be an `acm-pca-permission-test-key` file visible in the Amazon S3 bucket.
+When you configure a CRL for a CA, AWS Private CA writes a test object to the Amazon S3 bucket to verify that it has permission to write to the bucket. The object is named `acm-pca-permission-test-key`, or `acm-pca-permission-test-key-private` if `S3ObjectAcl` is set to `BUCKET_OWNER_FULL_CONTROL`.
+
+For a complete CRL, AWS Private CA writes the first CRL to the bucket shortly after you configure the CRL, typically within 30 minutes, even if the CA hasn't issued any certificates. The CRL is empty until you revoke a certificate, and AWS Private CA updates it periodically.
+
+For partitioned CRLs, AWS Private CA writes the CRL for a partition only after the CA issues a certificate that refers to that partition. AWS Private CA also writes a complete CRL, ``CA-ID`.crl`, to the bucket shortly after you configure the CRL, even if the CA hasn't issued any certificates. If the CA has always used partitioned CRLs, no certificate refers to this CRL, so it's always empty and you can ignore it.