TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities and articles.
Top engineers at Anthropic and OpenAI say AI now writes 100% of their code.
If you're not using AI, you're spending 40 hours doing what they do in 4.
These 100+ Claude Code hacks fix that and help you ship 10x faster.
Sign up for The Code and get:
100+ Claude Code hacks used by top engineers — free
The Code newsletter — learn the latest AI tools, tips, and skills to code faster with AI in 5 minutes a day
🛠 TOOL OF THE DAY
CK-X - Kubernetes certification exam simulator, open-source, free to use, and super easy to self-host with Docker. Includes a web UI, timed tasks, question navigator, and pre-configured K8s environments. Supports Docker, Helm and multiple exam preparation.
🧠 USE CASE
Why SSL Certificates Scale Better Than SSH
We DevOps and Cloud Engineers use SSH and SSL every day, but for very different reasons.
SSH is how we log into servers. It's authentication and remote shell access. You generate a keypair with ssh-keygen, copy the public key to the server, and you're in.
How SSH works
SSL is how we secure services. It's encryption and identity for traffic between browsers, APIs, and services enabled using certificates like those from Let's Encrypt or AWS ACM.
How SSL works
In short:
In a typical SSH setup, every user has a keypair, and the server stores public keys. If you’ve worked on legacy fleets or unmanaged clusters, you know what’s coming: SSH key sprawl.
I saw a case where 8 engineers were rotating on-call duties. Over time, they accumulated 45 public keys across 30 EC2 instances. Some belonged to interns who had left. Some were from CI runners we no longer used. No expiry, no labels, no audit.
Worse, people were doing ssh-copy-id directly or using Ansible with inventory files that were never cleaned.
To clean it up, they had to:
Run
find ~/.ssh/authorized_keyson every nodeBuild an internal tool to map keys to owners based on fingerprints
Rotate all keys using
ssh-keygen -Rand centralized provisioning via SSH certificates
It was a mess. And we swore to never let SSH become the main trust system again.
When we switched to ALB-based apps on AWS, we used ACM certificates for TLS termination. The setup was a one liner in Terraform:
listener {
port = 443
protocol = "HTTPS"
ssl_policy = "ELBSecurityPolicy-TLS13-1-3-2021-06"
certificate_arn = aws_acm_certificate.app_cert.arn }
The certs renewed automatically. Zero manual rotation.
Here’s the kicker: SSL certificates expire by design, are traceable, and bind to services, not users. That makes them scalable.
If you’re building for scale, use SSL for service-to-service, client-to-server, or browser-to-backend.
Looking to promote your company, product, service, or event to 44,000+ Cloud Native Professionals? Let's work together.
