AWS privateca: Explain default Not Before date and ValidityNotBefore parameter
Summary
Adds explanation that validity starts at Not Before, defaults to 60 minutes before issuance to compensate for clock skew, and can be overridden with the optional ValidityNotBefore parameter without changing Not After.
Security assessment
Clarifies certificate validity semantics and clock-skew compensation; informational certificate configuration documentation with no vulnerability or access-control change.
Evidence
+The validity period starts at the certificate's `Not Before` date and ends at its `Not After` date.
Diff
diff --git a/privateca/latest/userguide/ca-lifecycle.md b/privateca/latest/userguide/ca-lifecycle.md index 2d1bfbf..dc9ab2a 100644 --- a//privateca/latest/userguide/ca-lifecycle.md +++ b//privateca/latest/userguide/ca-lifecycle.md @@ -16,0 +17,2 @@ The validity period of an X.509 certificate is a required basic certificate fiel +The validity period starts at the certificate's `Not Before` date and ends at its `Not After` date. By default, when AWS Private CA issues a certificate, it sets the `Not Before` date to 60 minutes before the issuance time. This compensates for clock inconsistencies across computer systems. To set a different start date, specify the optional `ValidityNotBefore` parameter when you call [IssueCertificate](https://docs.aws.amazon.com/privateca/latest/APIReference/API_IssueCertificate.html). This parameter doesn't change the `Not After` date that you specify with the required `Validity` parameter. +