Clamscan alarm fires frequently in `dev` and `anvildev`

[achave11-ucsc]

The red rectangles represent the transition to ALARM state.
Foreground image is sorted desc, while the background one is asc.

[achave11-ucsc]

Likely solution:

Index: terraform/shared/shared.tf.json.template.py
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/terraform/shared/shared.tf.json.template.py b/terraform/shared/shared.tf.json.template.py
--- a/terraform/shared/shared.tf.json.template.py	(revision 49de05fc58f4e08c9574abc93aa40c4cca33c9d3)
+++ b/terraform/shared/shared.tf.json.template.py	(date 1758744385782)
@@ -116,10 +116,10 @@
 
 # The deployment and/or backup of the GitLab instance requires a reboot, which
 # can interrupt an ongoing ClamAV scan. Since scans are run twice a day, we set
-# the alarm period to 24 hours (maximum allowed by CloudWatch) to allow enough
-# time for the next scan to complete following an interrupted scan.
+# the alarm period to 36 hours to allow enough time for the next scan to
+# complete following an interrupted scan.
 #
-clam_alarm_period = 24 * 60 * 60
+clam_alarm_period = 36 * 60 * 60
 
 tf_config = {
     'data': {