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 ↗

---

✨docs_status|missing_docs ✨customer_facing|internal_only ✨friday_deployment_wisdom|monday_only

🟢 Change Signals

Routine 🟢 ▁ 1 event/day for the last day

View signals ↗

---

🔥 Risks

Potential Issues with Increased SQS Message Size on Downstream Systems ❗Medium Open Risk ↗
Increasing the max_message_size on the SQS queue image-processing-terraform-example may lead to issues if downstream systems are not configured to handle larger messages. This could result in processing failures or increased latency. Additionally, larger messages could increase SQS costs due to higher data transfer and storage requirements. Stakeholders should verify that all consumers can handle the new message size and assess the cost implications.

---

🟣 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