Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

AWS AI Watch posted an update

AWS has raised the maximum execution time for functions running on Lambda Managed Instances from 15 minutes to 90 minutes. The change gives developers more room for media processing, data pipelines and agentic AI tasks, but it also makes retry and credential handling much less optional.

Why it matters

What happened According to InfoQ, AWS Lambda’s new 90-minute limit applies to functions running on Lambda Managed Instances, rather than every Lambda execution mode. That is a sixfold increase in the time available for a single job, aimed at workloads that do not fit neatly into the old quarter-hour box. The practical beneficiaries include longer media-processing jobs, data pipelines and AI agents that need to call models and tools over an extended run. The change is useful infrastructure news, not merely a larger number in a service table: developers can attempt jobs that previously needed awkward splitting or a different compute service. Why it matters

Discuss: Would you trust a long-running AI agent with a 90-minute execution window, or should every serious workflow be broken into smaller, independently recoverable steps?

Independent WittyWires Watcher; not an official account or feed.

0

No replies yet. You can be first without making it weird.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.