> For the complete documentation index, see [llms.txt](https://docs.scanner.dev/scanner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/aws-lambda.md).

# AWS Lambda

Scanner supports AWS Lambda logs, which are logs generated by the code running in Lambda functions. These tend to be application logs. In order for Scanner to see them, you can configure Lambda to publish logs to CloudWatch, forward the CloudWatch log groups to a Kinesis Data Firehose, and then write them into an S3 bucket that Scanner is linked to.

## Collect logs in S3

{% stepper %}
{% step %}

### Lambda to CloudWatch

Follow the AWS documentation to publish your Lambda logs to one or more CloudWatch log groups.

See: [Using CloudWatch Logs logs with Lambda](https://docs.aws.amazon.com/lambda/latest/dg/monitoring-cloudwatchlogs.html).
{% endstep %}

{% step %}

### CloudWatch to Kinesis Data Firehose

Configure your CloudWatch log groups to push their logs to a Kinesis Data Firehose.

See: [Send CloudWatch Logs to Firehose](https://docs.aws.amazon.com/firehose/latest/dev/writing-with-cloudwatch-logs.html).
{% endstep %}

{% step %}

### Kinesis Data Firehose to S3

A Kinesis Data Firehose can push logs to various destinations. We want to push to an S3 bucket that Scanner is linked to. Follow the AWS documentation to configure the Firehose to write to an S3 bucket.

See: [Understand data delivery in Amazon Data Firehose](https://docs.aws.amazon.com/firehose/latest/dev/basic-deliver.html).
{% endstep %}
{% endstepper %}

## Create an Index Rule

Once Lambda logs are landing in your S3 bucket, [Create an Index Rule](/scanner/using-scanner-complete-feature-reference/data-ingestion/create-an-index-rule.md) to ingest the logs via Scanner Collect for fast search and detections.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/aws-lambda.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.