# Beautifying the awslamda nested logs Using Logstash in Kibana

**URL:** <https://discuss.elastic.co/t/beautifying-the-awslamda-nested-logs-using-logstash-in-kibana/358261>\
**Category:** Logstash\
**Created:** [April 26, 2024, 5:30am UTC](https://discuss.elastic.co/t/beautifying-the-awslamda-nested-logs-using-logstash-in-kibana/358261 "2024-04-26T05:30:36Z")\
**Posts on this page:** 1\
**Showing post:** 42

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 2, 2024, 8:07pm UTC](https://discuss.elastic.co/t/beautifying-the-awslamda-nested-logs-using-logstash-in-kibana/358261/42 "2024-05-02T20:07:54Z")

</div>

Here is what I wrote a week ago.

> [@dadoonet](#):
>
> But actually, I also noticed that you should may be not be using Logstash with a non official and not maintained plugin (unless I'm wrong) but instead use this integration: [AWS CloudWatch | Documentation](https://docs.elastic.co/en/integrations/aws/cloudwatch)

This is still valid. You should switch to this as it's the "official" way to collect logs from cloudwatch.

There was also a previous discussion regarding this: [Sending AWS Cloud Watch Logs to Elasticsearch](https://discuss.elastic.co/t/346459)

---

_[View the full topic](https://discuss.elastic.co/t/beautifying-the-awslamda-nested-logs-using-logstash-in-kibana/358261)._