# Ingesting CloudWatch logs from AWS Lambdas

**URL:** <https://discuss.elastic.co/t/ingesting-cloudwatch-logs-from-aws-lambdas/352675>\
**Category:** Elastic Observability\
**Tags:** docker, fleet, lambda\
**Created:** [February 6, 2024, 7:00pm UTC](https://discuss.elastic.co/t/ingesting-cloudwatch-logs-from-aws-lambdas/352675 "2024-02-06T19:00:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pzemgulys](https://avatars.discourse-cdn.com/v4/letter/p/ba9def/32.png) [@pzemgulys](https://discuss.elastic.co/u/pzemgulys)\
**Post date:** [February 6, 2024, 7:00pm UTC](https://discuss.elastic.co/t/ingesting-cloudwatch-logs-from-aws-lambdas/352675/1 "2024-02-06T19:00:02Z")

</div>

New to Elastic...

I have what I thought was a simple use case. I have a number of containerized lambdas, running in AWS, and generating CloudWatch Logs.

I simply want to ingest these into Elastic Observability.

Does this require setting up an agent somewhere in a container? EC2? I've looked at using the "Elastic Serverless Forwarder" as well. What are my options?

---

<div class="post-metadata">

**Author:** ![Julia\_Bardi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julia_bardi/32/79463_2.png) [@Julia\_Bardi](https://discuss.elastic.co/u/Julia_Bardi)\
**Post date:** [March 25, 2024, 2:10pm UTC](https://discuss.elastic.co/t/ingesting-cloudwatch-logs-from-aws-lambdas/352675/2 "2024-03-25T14:10:19Z")

</div>

Hi Paul, welcome to the community!

I think you can use the CloudWatch integration with Elastic Agent, see these guides:

> **[AWS CloudWatch | Documentation](https://docs.elastic.co/en/integrations/aws/cloudwatch)**
>
> Use this integration to collect logs and metrics from Amazon CloudWatch with Elastic Agent, where no out of the box integration is available.

> **[Getting started: Monitor hosts with Elastic Observability | Starting with the...](https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/getting-started-observability.html)**

Yes, you would need an Agent running somewhere on a host/VM.

I'm not really familiar with Elastic Serverless Forwarder, but you can have a look at the documentation if it fits your use case: [Elastic Serverless Forwarder for AWS | Elastic Serverless Forwarder Guide | Elastic](https://www.elastic.co/guide/en/esf/current/aws-elastic-serverless-forwarder.html)