AWS: lambda trigger is disabled

Sometimes a lambda trigger for example on an SQS queue gets disabled. This can happen for a variety of reasons, e.g.:

• there is a misconfiguration in the policy
• the lambda execution fails repeatedly
• the lambda ARN is misspelled

Though the problem is localised and fixed, the trigger is not automatically enabled. The trigger needs to be enabled manually.

The steps below illustrate enabling lambda trigger on an SQS queue:

1. Go to AWS console, select SQS, and your queue.
2. Under “Lambda triggers” you will see your trigger with status Disabled. Copy the UUID.
3. Execute with aws-cli:

aws lambda update-event-source-mapping — uuid <YOUR_UUID> — enabled

You lambda trigger should be enabled now.