SSL Cert Automation

SSL Cert Automation #

Automated SSL certificate provisioning and renewal for substrate services.

✓ 0 | ↻ 0 | ⏳ 16 (16 total)

Legend: βœ… Complete | πŸ”„ In Progress | ⏳ Planned


Project Vision & Scope #

Eliminate browser security warnings and enable secure communication between substrate services by deploying an internal Certificate Authority and automating certificate lifecycle management.

In Scope

  • Internal CA deployment and trust distribution
  • SSL certificates for infrastructure web UIs (Proxmox, OPNsense, Omada)
  • Automated certificate renewal
  • Expiration monitoring

Out of Scope

  • Public-facing certificates (use Let’s Encrypt separately)
  • Client certificate authentication
  • Code signing certificates

Requirements ⏳ #

  • ⏳ Define certificate naming conventions
  • ⏳ Define certificate validity periods
  • ⏳ Define renewal thresholds and alerting

Certificate Authority ⏳ #

Internal CA infrastructure for issuing trusted certificates.

  • ⏳ Evaluate CA options (step-ca, smallstep, CFSSL)
  • ⏳ Deploy internal CA on bootstrap node
  • ⏳ Distribute root CA to substrate hosts
  • ⏳ Configure browser/OS trust stores

Infrastructure Services ⏳ #

SSL certificates for core infrastructure web UIs.

  • ⏳ Proxmox VE admin UI (pve.dvnt.deevnet.net)
  • ⏳ OPNsense admin UI (opnsense.dvnt.deevnet.net)
  • ⏳ Omada Controller UI (omada.dvnt.deevnet.net)

Certificate Lifecycle ⏳ #

Automated renewal and distribution.

  • ⏳ ACME client deployment (certbot, acme.sh, or step CLI)
  • ⏳ Automated certificate renewal via cron/systemd timer
  • ⏳ Certificate deployment playbook
  • ⏳ Expiration monitoring and alerting

Documentation ⏳ #

  • ⏳ Certificate management runbook
  • ⏳ Manual renewal procedure (fallback)
Page last modified: March 26, 2026