Priority 1 - Reduces manual work and errors
Target audience: DevOps, Platform Teams
Guides for automating certificate operations in a PQ-enabled PKI.
| Scenario | Description | Complexity | Use Case |
|---|---|---|---|
| ACME Integration | Let's Encrypt / ACME protocol with PQ | Medium | Web servers, APIs |
| CI/CD Code Signing | Automatic signing in pipelines | High | Software releases |
| Kubernetes Cert-Manager | Automate certificates in Kubernetes | High | Cloud-native apps |
| Scheduled Renewal | Automatic certificate renewal | Low | All servers |
| Component | Version | Purpose |
| ———– | ——— | ——— |
| OpenSSL | 3.6+ | PQ algorithms |
| Certbot | 2.0+ | ACME client |
| cert-manager | 1.12+ | Kubernetes |
| HashiCorp Vault | 1.15+ | Secrets management |
1. Simplest Automation (Cron + Script):
# /etc/cron.weekly/cert-renew #!/bin/bash /usr/local/bin/renew-certificates.sh >> /var/log/cert-renew.log 2>&1
→ Details: Scheduled Renewal
2. ACME for public web servers:
# Certbot with DNS challenge certbot certonly --dns-cloudflare -d example.com --deploy-hook /etc/letsencrypt/renewal-hooks/deploy/reload-nginx.sh
→ Details: ACME Integration
3. Kubernetes Cert-Manager:
apiVersion: cert-manager.io/v1 kind: Certificate metadata: name: my-app-tls spec: secretName: my-app-tls issuerRef: name: pq-issuer kind: ClusterIssuer dnsNames: - app.example.com
→ Details: Cert-Manager
« <- Operator Scenarios | -> ACME Integration »
Wolfgang van der Stille @ EMSR DATA d.o.o. - Post-Quantum Cryptography Professional