# Filter subscription in AWS Cloudwatch Logs

**URL:** <https://community.graylog.org/t/filter-subscription-in-aws-cloudwatch-logs/21603>\
**Category:** Graylog Central (peer support)\
**Tags:** pipeline-rules\
**Created:** [October 27, 2021, 2:09pm UTC](https://community.graylog.org/t/filter-subscription-in-aws-cloudwatch-logs/21603 "2021-10-27T14:09:49Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![gsmith](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gsmith/32/1222_2.png) [@gsmith](https://community.graylog.org/u/gsmith)\
**Post date:** [October 27, 2021, 9:53pm UTC](https://community.graylog.org/t/filter-subscription-in-aws-cloudwatch-logs/21603/4 "2021-10-27T21:53:11Z")

</div>

Hello && Welcome

I might be able to help.

> [@leandrodamascena](#):
>
> We know Lambda creates logs with messages like START/END/EXECUTION and I don’t need to stream that because I don’t need those message,

Have you tried using a pipeline to drop those messages and filter them into a stream?  
I found some posts on these subjects as shown below.

[Drop Messages using pipeline](https://community.graylog.org/t/dropping-messages-using-pipelines/11229)

[Route to Stream](https://community.graylog.org/t/pipeline-doest-not-route-to-stream/16534/4)

Hope that helps

---

_[View the full topic](https://community.graylog.org/t/filter-subscription-in-aws-cloudwatch-logs/21603)._