Replies: 1 comment 2 replies
-
I'm pretty sure there is no guarantee (nor even expectation) that S3 events will come out in any particular order. On this page of the docs it says it can take up to a minute for an event to fire. So if the events coming out of S3 are in an unreliable order there's no Lambda configuration that can overcome that. If your Use Case requires that objects be processed in the exact order they are stored, I'd suggest having the process that stores the object to S3 then put a message with a link to the object in a FIFO queue, and trigger a Lambda function off that queue. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was wondering if we have support for FIFO File processing, say.
I have first lambda function which is trigged if an object is dropped in a S3 bucket, which further on goes to processing in the second lambda function and meanwhile I upload another object in the same S3 bucket but this time the second object is completed in process and then the first object is processed.
So I was wondering if there is any way to process file sequentially i.e. FIFO.
Beta Was this translation helpful? Give feedback.
All reactions