We're scaling up our prototype and now need to send larger payloads (around 100MB) to our backend. Currently, the data is routed through CloudFront to API Gateway and then to Lambda, but I've learned that API Gateway has a limit of 250KB per request. I'm considering creating a new endpoint that fetches a signed PUT URL from S3 for uploading, then calling the original endpoint with a GET request to retrieve it in Lambda. However, that seems a bit overly complicated. Does anyone have better suggestions?
3 Answers
Another option is to invoke the Lambda function directly from AWS services, if that's feasible for your setup. It can save some time instead of going through API Gateway.
You might want to trigger your Lambda function directly when the S3 upload is successful. This way, you bypass the need for orchestration from the client side entirely.
That plan sounds reasonable to me! It's a solid way to handle larger uploads, but do consider if it's the most efficient route for your use case.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically