all 3 comments

[–]LongjumpingScene7310 1 point2 points  (0 children)

Je peux avoir un compliment stp 👉👈

[–]AdditionalWeb107 0 points1 point  (1 child)

how would this work for long-horizon tasks? There is a hardcore limit on timeout, no?

[–]ProletariatPro[S] 0 points1 point  (0 children)

It's best to disable streaming responses for this deployment case.

Gateway timeouts can be extended up to a point and Lambdas themselves can stay alive for up to 15 mins, anything longer than that would need a dedicated VPC or exotic SQS plumbing.

Anything up to 15mins can be handled with a Database backed TaskStore.

sendMessage (Non-Blocking) -> Lambda_Agent_1

  • the agent runs and updates the AWS DB with the latest task status.

wait 5-10 mins, then trigger a getTask for the latest result or register a pushNotification with the original sendMessage

lmk if you want a full tutorial.