- Newest
- Most votes
- Most comments
Hi,
For this kind if operation, I would suggest to have the client directly upload to S3. You can even use S3-Accelaration to reduce the upload time a bit (depending on client and bucket location).
To grant your client access to S3, you have several choices:
You are already using Cognito Identity Pool: Your client will receive temporary credentials upon login. Adapt the role policies to allow S3 PutObject and have the client uploading the file via it's AWS-SDK
Have your API return a presigned URL on which the client can do a POST. Have a trigger on S3 (Object Created) that kicks-off a Lambda to process the file
Hope this helps,
Regards, Daniel
You can't increase the payload size to a Lambda function. The limit is 256KB for asynchronous invocations and 6MB for synchronous invocations (as from ALB).
The recommended approach is to generate a presigned URL and upload the file directly to S3 from the client using that URL.
Hi Daniel & Uri,
Thanks for the answers. After read your answer, we did some exploration.
We plan to use EFS together with existing ECS. Right now, we still exploring how to link those.
Thank You.
Relevant content
- asked 7 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 3 months ago