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|safe_for_friday

🟢 Change Signals

Routine 🟢 ▁ 1 event/day for the last day

View signals ↗

---

🔥 Risks

Potential Impact of Increasing SQS max_message_size on Downstream Applications and Costs ❗Medium Open Risk ↗
Increasing the max_message_size from 25,600 bytes to 102,400 bytes on the SQS queue 'image-processing-terraform-example' presents several risks. Downstream applications consuming messages from this queue may fail or degrade in performance if they are not configured to handle larger message sizes. This could lead to processing errors or increased latency. Additionally, the change may result in higher AWS costs due to increased data transfer and storage requirements. Monitoring and alerting systems may also need updates to accommodate the new message size limit, preventing false alarms or missed alerts.

---

🟣 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