New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: awslambda.streamifyResponse support for lambda #10751
Comments
Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide. |
I'd be happy to take this one as I'd really like to see this implemented & have been in the same situation |
Thank you for @ptfpinho23 for letting us know you are interested in this feature. We have an internal backlog item for this feature and are happy to prioritize highly requested features (also see support depending on our subscription plans). This feature is quite complex because it requires a deep understanding of:
If you are confident in all these areas, feel free to give it a try and demonstrate a working implementation covered by an AWS Parity test. |
Thanks for the breakdown @joe4dev . I've been taking a closer look in the meantime & will definitely give it a try. |
Is there an existing issue for this?
Feature description
AWS introduced streaming responses.
https://docs.aws.amazon.com/lambda/latest/dg/configuration-response-streaming.html
This comes in handy when creating handlers working with LLM's.
Other middleware like Middy also supports response streaming.
https://middy.js.org/docs/intro/streamify-response/
As of now, these streamed lambdas are not working in localstack. Getting an internal server error for the same.
It would be good to have the feature as LLM-based applications are growing.
Another approach will be to use websockets. But a clean approach will always be to use streams for pushing out each response piece by piece for faster resolution.
🧑💻 Implementation
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: