Skip to content
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

Responses larger than Lambda-imposed 6MB limit #245

Open
bmallary opened this issue Jun 19, 2018 · 1 comment
Open

Responses larger than Lambda-imposed 6MB limit #245

bmallary opened this issue Jun 19, 2018 · 1 comment

Comments

@bmallary
Copy link

I've run into a use case where the response when running a Lambda function via an HTTP POST to an API Gateway endpoint will likely exceed the Lambda imposed limit if 6MB. I have made a modification to SCAR to inspect the size of the response, and deliver it via a write to S3 with a pre-signed URL delivered via a 302 redirect.

Interested to know if there are any other approaches that have been tried.

@alpegon
Copy link
Collaborator

alpegon commented Jun 20, 2018

Hi, for large responses we always use an S3 bucket to store the output.
The scripts that we use in our different examples are in charge of creating/moving the output files generated by the container in the output folder that the supervisor will check when the execution is finished.
If for any reason you could not create or move this files, your alternative could be valid. Also, if the user already defined an output bucket/folder we could use it as default instead of the pre-signed URL.
I can add this check, but if you already have it working I encourage you to do a PR so we can add it to our framework 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants