We are experiencing double Lambda invocations of Lambdas triggered by S3 ObjectCreated-Events. Those double invocations happen *exactly* 10 minutes after the first invocation, not 10 minutes after the first try is complete, but 10 minutes after the first invocation happened. The original invocation takes anything in the range between 0.1 to 5 seconds. No invocations results in errors, they all complete successfully.

We are aware of the fact that SQS for example does not guarantee exactly-once but at-least-once delivery of messages and we would accept some of the lambdas getting invoked a second time due to results of the distributed system underneath. A delay of 10 minutes however sounds very weird.

Of about 10k messages 100-200 result in double invocations.

The AWS Support basically says *"the 10 minute wait time is by design but we cannot tell you why"*, which is not at all helpful.

---

* Has anyone else experienced this behaviour before?
* How did you solve the issue or did you simply ignore it (which we could do)?
* One proposed solution is not to use direct S3-lambda-triggers, but let S3 put its event on SNS and subscribe a Lambda to that. Any experience with that approach?

---

*example log: two invocations, 10 minutes apart, same RequestId*

> 
> START RequestId: f9b76436-1489-11e7-8586-33e40817cb02 Version: 13  
> 
>  2017-03-29 14:14:09 INFO ImageProcessingLambda:104 - handle 1 records
> 
> 
> 

*and*

> 
> START RequestId: f9b76436-1489-11e7-8586-33e40817cb02 Version: 13  
> 
>  2017-03-29 14:24:09 INFO ImageProcessingLambda:104 - handle 1 records
> 
> 
>