Automating TLS Certificate Monitoring with GitHub Actions, certificate_watcher, and Slack
Briefly

Automating TLS Certificate Monitoring with GitHub Actions, certificate_watcher, and Slack
"As a consultant constantly working with clients, I found myself in a familiar predicament: my head was always down, focused on delivering value to customers, but my own infrastructure monitoring was non-existent. I had no simple way to track SSL/TLS certificate expirations across the multiple domains I managed - personal sites, client projects, and community services. I needed a solution, but I had several constraints:"
"No time for complex setup: I couldn't afford to spend days installing, configuring, and deploying yet another monitoring service Easy maintenance: Whatever I built had to be low-maintenance - I didn't want another system to babysit Transparency and control: I wanted a simple text file in Git listing the hosts to monitor, so I could see exactly what was being checked and track changes over time Zero infrastructure: No servers to provision, patch, or pay for"
Many operators lack a simple way to track SSL/TLS certificate expirations across multiple domains, including personal sites, client projects, and community services. Constraints include limited time for complex setup, desire for low maintenance, need for transparent control via a Git-hosted hosts list, and avoidance of any server infrastructure. The solution combines certificate_watcher, a lightweight Python tool, with GitHub Actions to run weekly checks and Slack for notifications. The workflow reads a simple text file in Git listing hosts to monitor, checks certificates, and posts results to Slack. The approach is serverless, requires minimal maintenance, and can be set up in under an hour.
Read at Stephane's Blog
Unable to calculate read time
[
|
]