<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>vault on Dennis T. Bielinski</title><link>https://www.sudoaccess.com/tags/vault/</link><description>Recent content in vault on Dennis T. Bielinski</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 25 Mar 2020 20:45:00 -0400</lastBuildDate><atom:link href="https://www.sudoaccess.com/tags/vault/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing a stuck TTL on HashiCorp&#39;s Vault PKI</title><link>https://www.sudoaccess.com/posts/fix-hashicorp-vault-pki-ttl/</link><pubDate>Wed, 25 Mar 2020 20:45:00 -0400</pubDate><guid>https://www.sudoaccess.com/posts/fix-hashicorp-vault-pki-ttl/</guid><description>My shop has been using consul-template to rotate the vault certificates for us each month, but unfortunately this turned out to not be very reliable. Since my current shop is actually replacing vault for AWS SSM, it hasn&amp;rsquo;t gotten much TLC lately and there&amp;rsquo;s really no reason to pour work into this setup to make it more resiliant; plus it&amp;rsquo;s mostly used by our legacy staging environments, which naturally don&amp;rsquo;t get much TLC in any environment.</description></item></channel></rss>