<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Redis on ferkakta.dev</title><link>https://ferkakta.dev/tags/redis/</link><description>Recent content in Redis on ferkakta.dev</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright fizz.</copyright><lastBuildDate>Fri, 13 Feb 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://ferkakta.dev/tags/redis/index.xml" rel="self" type="application/rss+xml"/><item><title>ElastiCache auth-token to RBAC migration has a Terraform provider bug</title><link>https://ferkakta.dev/elasticache-auth-token-to-rbac-migration/</link><pubDate>Fri, 13 Feb 2026 09:00:00 -0600</pubDate><guid>https://ferkakta.dev/elasticache-auth-token-to-rbac-migration/</guid><description>&lt;p&gt;Needed to migrate a shared ElastiCache Redis cluster from a single auth token to per-user RBAC. Breaking change — every service on the cluster goes dark if you get the sequencing wrong.&lt;/p&gt;
&lt;h2 id="the-terraform-provider-bug"&gt;The Terraform provider bug&lt;/h2&gt;
&lt;p&gt;Step one: don&amp;rsquo;t touch the real cluster. Built a throwaway copy and ran the migration there first.&lt;/p&gt;
&lt;p&gt;Good thing — the Terraform AWS provider has a bug in the auth-token removal step. It tells you the auth token was removed. Updates its state file. The plan shows no changes. But the underlying API call silently fails. The token is still active on the cluster.&lt;/p&gt;</description></item></channel></rss>