From dab788408c4c0d5d632dc07bf6b3053533e78fb2 Mon Sep 17 00:00:00 2001
From: Melanie Barker <melanie.barker@exygy.com>
Date: Wed, 30 Sep 2026 10:31:01 -0400
Subject: [PATCH] Filter AWS-managed ElastiCache defaults from e2e aws-nuke

Since 2026-09-29, AWS auto-creates the ElastiCache user default.iam-user
and user group default.iam-user-group. They can't be deleted, so aws-nuke
fails on both the pre and post nuke steps. Filter them until aws-nuke
handles them itself (ekristen/aws-nuke#1039).
---
 e2e-test/nuke.yaml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/e2e-test/nuke.yaml b/e2e-test/nuke.yaml
index 32f7789a..e5937f3c 100644
--- a/e2e-test/nuke.yaml
+++ b/e2e-test/nuke.yaml
@@ -60,6 +60,14 @@ accounts:
         - type: glob
           property: "DomainName"
           value: "*.civiform.dev"
+      # AWS-managed defaults that can't be deleted. Remove these filters once
+      # aws-nuke filters them itself: https://github.com/ekristen/aws-nuke/issues/1039
+      ElasticacheUser:
+        - property: "UserName"
+          value: "default.iam-user"
+      ElasticacheUserGroup:
+        - property: "ID"
+          value: "default.iam-user-group"
       IAMOpenIDConnectProvider:
         - type: glob
           value: "arn:aws:iam::*:oidc-provider/token.actions.githubusercontent.com"