AWS privateca documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in OCSP configuration context.
Security assessment
Update maintains existing security documentation about OCSP revocation but doesn't add new security content. The change is purely terminological.
Diff
diff --git a/privateca/latest/userguide/revocation-setup.md b/privateca/latest/userguide/revocation-setup.md index 3d00043a4..f9f7117fe 100644 --- a//privateca/latest/userguide/revocation-setup.md +++ b//privateca/latest/userguide/revocation-setup.md @@ -19 +19 @@ If you create your CA without configuring revocation, you can always configure i -AWS Private CA provides a fully managed OCSP solution to notify endpoints that certificates have been revoked without the need for customers to operate infrastructure themselves. Customers can enable OCSP on new or existing CAs with a single operation using the AWS Private CA console, the API, the CLI, or through AWS CloudFormation. Whereas CRLs are stored and processed on the endpoint and can become stale, OCSP storage and processing requirements are handled synchronously on the responder backend. +AWS Private CA provides a fully managed OCSP solution to notify endpoints that certificates have been revoked without the need for customers to operate infrastructure themselves. Customers can enable OCSP on new or existing CAs with a single operation using the AWS Private CA console, the API, the CLI, or through CloudFormation. Whereas CRLs are stored and processed on the endpoint and can become stale, OCSP storage and processing requirements are handled synchronously on the responder backend.