<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tls on GeekyRyan</title><link>https://rnemeth90.github.io/tags/tls/</link><description>Recent content in Tls on GeekyRyan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 29 Aug 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://rnemeth90.github.io/tags/tls/index.xml" rel="self" type="application/rss+xml"/><item><title>Annual TLS Certificate Renewal Across Customer-Facing Endpoints</title><link>https://rnemeth90.github.io/projects/2024-08-29-yearly-tls-certificate-renewal/</link><pubDate>Thu, 29 Aug 2024 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2024-08-29-yearly-tls-certificate-renewal/</guid><description>&lt;p&gt;Every year: renew the TLS certificates before they expire. It&amp;rsquo;s not glamorous, but it&amp;rsquo;s one of the more embarrassing ways to take down a customer-facing service if you slip up on it.&lt;/p&gt;&#10;&lt;p&gt;This round meant hitting certificates in multiple places - NGINX endpoints, IIS services, and some Terraform configs where certs are hard-coded and need manual updates instead of just dropping in a new one. Each has its own deployment quirks, so the real discipline is keeping an accurate inventory of everywhere a cert lives, not just the obvious spots.&lt;/p&gt;</description></item></channel></rss>