Certificate Lifecycle Service · View 08 of 21 · Structure
The one synchronous path
- Workload issuance is on a request path: a pod that cannot obtain a leaf at startup does not start. p99 ≤ 250 ms in-region (stated assumption).
- Everything else may queue. A tenant's domain order, a renewal, a revocation publication and an audit export all tolerate minutes.
Decisions
- Two public CA accounts sit behind one integration, so failover is a configuration change rather than a new surface to build under pressure.
- Route 53 appears as a platform component, not a dependency: it is the delegated zone the DNS-01 responder answers in.
- Relying parties validating revocation talk to CRL and OCSP, which are published independently of this service and held to a higher availability target than issuance.
Assumption
- Public CA rate limits are tracked per registered domain and per account; approaching a limit queues rather than fails.