You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's maybe a scenario to explain why this would be needed:
If I create an SQS EventSourceMapping for a Lambda, and then later delete and recreate that queue, the EventSourceMapping will go from ENABLED state to DISABLED state (AWS Lambda does this) and it does not switch back. Cloudformation does not detect this drift and consequently, lambda functions fail to get invoked thus breaking apps.
Name of the resource
AWS::Lambda::EventSourceMapping
Resource name
No response
Description
Drift detection is not supported for AWS::Lambda::EventSourceMapping.
Other Details
Here's maybe a scenario to explain why this would be needed:
If I create an SQS EventSourceMapping for a Lambda, and then later delete and recreate that queue, the EventSourceMapping will go from ENABLED state to DISABLED state (AWS Lambda does this) and it does not switch back. Cloudformation does not detect this drift and consequently, lambda functions fail to get invoked thus breaking apps.
Ref:
The text was updated successfully, but these errors were encountered: