Lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (in timezone Europe/London)

• Branch creation
  • "before 4am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Caution

[High Risk] Replacing the sole ALB and NLB targets will create a period with zero healthy backends

The change replaces the only registered backend in both load balancer target groups: 540044833068.eu-west-2.elbv2-target-group.api-207c90ee-tg currently forwards port 80 traffic only to i-0bf4039822e01f430, and 540044833068.eu-west-2.elbv2-target-group.txn-feed-terraform-example currently forwards port 9090 traffic only to 10.0.101.34. Both corresponding aws_lb_target_group_attachment resources are being replaced at the same time as the backing EC2 instances, so each load balancer path will lose its sole target during cutover.

AWS only routes to newly registered ALB and NLB targets after registration completes and the target passes initial health checks. With no second target in either group, deregistration of the current instance will leave zero healthy targets until the replacement instance is up, attached, and passing /health on port 80 or TCP checks on port 9090. This will interrupt both the ALB-served API path and the NLB/direct feed path, and the simultaneous rebinding of Elastic IP 13.134.236.98 means the direct public access path moves during the same window instead of providing a stable fallback.
_{View reasoning tree here.}

Caution

[High Risk] Replacing the sole ALB-backed API instance will leave the load balancer without a healthy target during cutover

The change replaces the only EC2 instance currently registered in 540044833068.eu-west-2.elbv2-target-group.api-207c90ee-tg, which serves HTTP on port 80 and must pass the ALB health check on /health. The attachment resource for that instance is also being replaced, so during apply Terraform will remove the old backend and then register a new instance with a new ID before it can become healthy.

Because this target group currently has just one healthy instance target, the ALB will have no healthy backends during the replacement window. Requests through api-207c90ee-alb will fail until the new host finishes booting, starts its web service, and passes the ALB health checks, causing a real but transient outage of the API ingress path.
_{View reasoning tree here.}

Signals

Routine → Multiple infrastructure resources are showing unusual routine changes at only 1-3 events/week for the last 5 months, including EC2 instances, load balancer attachments, an alarm, and an SNS subscription. The most frequent pattern is 1 event/week for the last 5 months, which is infrequent compared to typical patterns.

_{Additional Change Details:} Items 84 Edges 165 model|risks_v6 ✨Encryption Key State Risk ✨KMS Key Creation