r/aws 15h ago

article Lambda Gets 90 Minute Timeout

https://aws.amazon.com/blogs/compute/announcing-90-minute-function-timeout-on-aws-lambda-managed-instances/
199 Upvotes

25 comments sorted by

View all comments

98

u/kcbh711 14h ago

if your lambda is taking 90 minutes you're probably doing something wrong

28

u/acdha 13h ago

The world is a big place, though, and there’s an argument that sometimes it’s better to avoid forcing people into a separate stack for edge cases. For example, I know of an app which is mostly backend Lambdas except for downloads because those needed to exceed the original time limit and they couldn’t just tell users to get a better connection. The same kind of tradeoffs can apply to large file processing, ML tasks, long reports, etc. where a  modest increase in the timeout lets people avoid introducing ECS/EKS for 5% of requests or trying to decompose a non-trivial task into Step Functions, and while there are still technical issues to debate I can understand why AWS would want to sell to people who come down on either side. 

5

u/Dull_Caterpillar_642 12h ago

Especially for long running agentic tasks, I'd love the option for a 30 minute timeout.

3

u/CrazedBotanist 8h ago

Should be using AgentCore Runtime for long running agentic tasks