AWS privateca low security documentation change
Summary
Removed reference to AWS Private CA automatically creating S3 buckets and applying default permissions policies during CA creation.
Security assessment
This change supports the security fix in create-CA.md by eliminating documentation about the removed automatic bucket creation feature. It reinforces that bucket policies must be manually configured, reducing risks of unintended public access to CRL data.
Diff
diff --git a/privateca/latest/userguide/crl-planning.md b/privateca/latest/userguide/crl-planning.md index 21396b1c3..b4957e013 100644 --- a//privateca/latest/userguide/crl-planning.md +++ b//privateca/latest/userguide/crl-planning.md @@ -100 +100 @@ If you plan to create a CRL, you need to prepare an Amazon S3 bucket to store it -Your S3 bucket must be secured by an attached IAM permissions policy. Authorized users and service principals require `Put` permission to allow AWS Private CA to place objects in the bucket, and `Get` permission to retrieve them. During the console procedure for [creating](./create-CA.html) a CA, you can choose to let AWS Private CA create a new bucket and apply a default permissions policy. +Your S3 bucket must be secured by an attached IAM permissions policy. Authorized users and service principals require `Put` permission to allow AWS Private CA to place objects in the bucket, and `Get` permission to retrieve them.