# Lambda with SQS event trigger failing invocation from CloudWatch Events Rule

**URL:** <https://forum.serverless.com/t/lambda-with-sqs-event-trigger-failing-invocation-from-cloudwatch-events-rule/8287>\
**Category:** Serverless Framework\
**Tags:** lambda\
**Created:** [May 16, 2019, 5:17am UTC](https://forum.serverless.com/t/lambda-with-sqs-event-trigger-failing-invocation-from-cloudwatch-events-rule/8287 "2019-05-16T05:17:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mlevit](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/mlevit/32/3325_2.png) [@mlevit](https://forum.serverless.com/u/mlevit)\
**Post date:** [May 16, 2019, 5:17am UTC](https://forum.serverless.com/t/lambda-with-sqs-event-trigger-failing-invocation-from-cloudwatch-events-rule/8287/1 "2019-05-16T05:17:04Z")

</div>

Hey all,

I have a Lambda function with an SQS event trigger. The SQS is populated by a CloudWatch Events Rule (based on AWS Config changes). However when looking into the CloudWatch Events Rule metrics, all attempted invocations to place a message onto SQS failed. The SQS event trigger works if I manually send a message to SQS, but the link between CloudWatch Events Rule and SQS doesn’t work.

If I remove the link and re-create it manually via the console it’ll begin to work… however then when I try to run a `serverless remove` I’ll receive an error that the CloudWatch Events Rule `has a target`.

Any ideas/suggestions?