trigger: activate dangerous message size breach scenario

[omerdemirok]

• Increase message_size_breach_max_size from 25KB to 100KB
• With batch_size=10, total payload becomes 1MB (4x Lambda's 256KB async limit)
• This will cause complete Lambda processing failure during Black Friday
• Demonstrates Overmind's ability to catch non-obvious cross-service limits
• Perfect demo of hidden risk: innocent config change with catastrophic impact

[github-actions]

Open in Overmind ↗

---

✨friday_deployment_wisdom|monday_only

🟢 Change Signals

Routine 🟢 ▁ 1 event/day for the last day

View signals ↗

---

🔥 Risks

Potential Compatibility and Performance Issues with Increased SQS Message Size ❗Medium Open Risk ↗
Increasing the max_message_size for the SQS queue image-processing-terraform-example from 25600 bytes to 102400 bytes could lead to errors or performance degradation in downstream services if they are not configured to handle larger messages. This change may also impact the queue's throughput and latency due to increased resource consumption for larger messages. Without specific evidence of downstream services' configurations, the risk remains speculative, but it is essential to verify compatibility and update monitoring systems accordingly.

---

🟣 Expected Changes

~ sqs-queue › https://sqs.eu-west-2.amazonaws.com/540044833068/image-processing-terraform-example

--- current
+++ proposed
@@ -8,5 +8,5 @@
   id: https://sqs.eu-west-2.amazonaws.com/540044833068/image-processing-terraform-example
   kms_data_key_reuse_period_seconds: 300
-  max_message_size: 25600
+  max_message_size: 102400
   message_retention_seconds: 1.2096e+06
   name: image-processing-terraform-example

---

---

💥 Blast Radius

Items 10

Edges 9