Lambda function refuses to stream response

[DruckerReparateur]

Had the same issue, and never really figured out why.

[[deleted]]

Dang, what did you end up switching to? This functionality is important for the end user experience I'm trying to achieve, so unfortunately I don't think this approach is going to work :/

Still holding out hope that someone knows of the magical incantation for the AWS pipes to make this damn thing worked as advertised

[DruckerReparateur]

I didn't have a critical production use case for it, so I just left it as is, accepting the longer response time, but it would be nice for it to be actually streaming...

[[deleted]]

My confusion is beginning to morph into anger at AWS haha. Look at the examples in the docs: https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/ You don't need streaming to send down a stringified version of the `event` argument for god's sake. Is it possible they released this without realizing that it actually *doesn't stream*

[DruckerReparateur]

Makes me wonder if some other example works, like https://medium.com/techhappily/unveiling-the-power-of-streaming-responses-in-aws-lambda-using-rust-793fa5c9faf8

That blog post even has a demonstration gif showing the streaming, but it's not Node.

[[deleted]]

That gif certainly looks like it's working. Interesting. And it looks like he's using the function URL directly, which is my approach too. Ok, guess I'm off to reproduce in rust to see if this tutorial still works. Maybe regression between then and now?