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 ↗

---

🟢 Change Signals

Routine 🟢 ▁ 1 event/day for the last day

View signals ↗

---

🔥 Risks

Potential Latency, Cost, and Compatibility Risks from Increased SQS Message Size ❗Medium Open Risk ↗
Increasing the max message size in the SQS queue 'image-processing-terraform-example' from 25600 bytes to 102400 bytes presents several risks. Larger messages may lead to increased latency and reduced throughput if downstream systems are not optimized for larger payloads. This could affect the efficiency of the message processing pipeline. Additionally, the cost of using SQS will increase due to larger payload sizes. Compatibility issues may arise if consumer applications have hardcoded limits on message size, potentially leading to processing failures. The increased data transfer could strain network resources, impacting other services if the current configuration is insufficient. Lastly, if error handling and retry mechanisms are not robust, larger messages could lead to increased transmission errors and retries, affecting reliability.

---

🟣 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