---
title: "What’s a sensible visibility timeout for an AWS Lambda SQS consumer?"  
description: "What’s a sensible visibility timeout for an AWS Lambda SQS consumer?"  
author: "Kalin"  
published: 2026-10-11  
updated: 2026-10-11  
canonical: https://www.mindstick.com/forum/162257/what-s-a-sensible-visibility-timeout-for-an-aws-lambda-sqs-consumer  
category: "Lambda with SQS"  
tags: ["AWS Lambda", "Amazon SQS", "Serverless"]  
reading_time: 1 minute  

---

# What’s a sensible visibility timeout for an AWS Lambda SQS consumer?

Our Lambda function processes SQS messages that usually finish in under a minute, but a small number take several minutes when a downstream service is slow. We’ve seen occasional duplicate processing and are reviewing the queue’s visibility timeout.

How are people choosing that timeout relative to Lambda’s maximum execution time and their retry strategy? I know a longer timeout can delay recovery from a failed invocation, while a shorter one risks another consumer picking up a message that is still being handled. What signals or failure patterns should guide the setting?


---

Original Source: https://www.mindstick.com/forum/162257/what-s-a-sensible-visibility-timeout-for-an-aws-lambda-sqs-consumer

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.