Description
Hi @akhilerm, the integration stopped working since last week.
Cooncidently I also received the following mail:
We are reaching out to you to notify you about upcoming changes to AWS Lambda’s recursive loop detection.
Recursive loop detection detects and terminates recursive loops between AWS Lambda and other supported services, preventing runaway workloads due to misconfiguration. Recursive loop detection is currently supported for loops between AWS Lambda, Amazon SQS, and Amazon SNS. In 2024, Lambda will be extending recursive loop detection support to Amazon S3. As an incremental step in the full launch of this feature, Lambda will be making underlying changes to how recursive loop detection works.
Starting July 8, 2024, recursive invocations that pass through Lambda and S3 where S3 is NOT the event source or trigger to the Lambda function will be detected and terminated after approximately 16 recursive invocations. An example of a recursive loop that will now be terminated is a Lambda function storing data in S3 bucket, which triggers notifications to SNS, which triggers the same Lambda function. This update will be gradually rolled out in June in all commercial regions where recursive loop detection is supported (Recursive loop detection is not currently supported in the following commercial regions: Middle East (UAE), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Israel (Tel Aviv), Canada West (Calgary), Europe (Spain), and Europe (Zurich)).
What action should I take?
If you have a function that relies on intentional recursion with Amazon S3, you should contact AWS Support [1] to opt your account out of recursive loop detection to avoid potential disruption of this workload. Please create a support case for each account that requires opt-out and state which region requires the opt-out.
Could this have anything to do with it?