fix: increase SQS visibility timeout to 6x Lambda timeout for AWS com…

[omerdemirok]

…pliance

[github-actions]

Open in Overmind ↗

---

🔴 Change Signals

Routine 🔴 ▃▂▁ The SQS queue (image_processing_queue) is showing the first ever modification of the attribute visibility_timeout_seconds, which is unusual compared to typical patterns.

View signals ↗

---

🔥 Risks

Potential Message Processing Delays and Resource Utilization Issues Due to Increased SQS Visibility Timeout ❗Medium Open Risk ↗
The proposed increase in SQS visibility timeout to 1080 seconds could lead to potential issues if not aligned with the Lambda function's execution time and error handling strategy. Specifically, if the Lambda function takes longer than expected to process messages, it may cause delays in message reprocessing, impacting downstream systems. Additionally, without proper retry configurations, messages could remain unprocessed, leading to data loss or processing backlogs. The longer visibility timeout may also result in higher costs if messages are unnecessarily held in the queue.

---

🟣 Expected Changes

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

--- current
+++ proposed
@@ -26,3 +26,3 @@
   timeouts: null
   url: https://sqs.eu-west-2.amazonaws.com/540044833068/image-processing-terraform-example
-  visibility_timeout_seconds: 30
+  visibility_timeout_seconds: 1080

---

🟠 Unmapped Changes

+ aws_lambda_event_source_mapping › module.scenarios[0].module.message_size_breach[0].aws_lambda_event_source_mapping.sqs_trigger

--- current
+++ proposed
@@ -0,0 +1,33 @@
+type: aws_lambda_event_source_mapping
+id: github.com/overmindtech/terraform-example.aws_lambda_event_source_mapping.module.scenarios[0].module.message_size_breach[0].aws_lambda_event_source_mapping.sqs_trigger
+attributes:
+  amazon_managed_kafka_event_source_config: (known after apply)
+  arn: (known after apply)
+  batch_size: 10
+  bisect_batch_on_function_error: null
+  enabled: true
+  event_source_arn: arn:aws:sqs:eu-west-2:540044833068:image-processing-terraform-example
+  function_arn: (known after apply)
+  function_name: arn:aws:lambda:eu-west-2:540044833068:function:image-processor-terraform-example
+  function_response_types: null
+  id: (known after apply)
+  kms_key_arn: null
+  last_modified: (known after apply)
+  last_processing_result: (known after apply)
+  maximum_batching_window_in_seconds: 5
+  maximum_record_age_in_seconds: (known after apply)
+  maximum_retry_attempts: (known after apply)
+  parallelization_factor: (known after apply)
+  queues: null
+  self_managed_kafka_event_source_config: (known after apply)
+  starting_position: null
+  starting_position_timestamp: null
+  state: (known after apply)
+  state_transition_reason: (known after apply)
+  tags: null
+  tags_all: (known after apply)
+  terraform_address: module.scenarios[0].module.message_size_breach[0].aws_lambda_event_source_mapping.sqs_trigger
+  terraform_name: module.scenarios[0].module.message_size_breach[0].aws_lambda_event_source_mapping.sqs_trigger
+  topics: null
+  tumbling_window_in_seconds: null
+  uuid: (known after apply)

---

💥 Blast Radius

Items 10

Edges 9