> 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-vpc-transit-gateway-flow.md).

# AWS VPC Transit Gateway Flow

Scanner supports AWS VPC Transit Gateway flow logs, which contain data about the IP traffic going to and from your transit gateways. In order for Scanner to see these logs, you can configure VPC to publish these logs to an S3 bucket that Scanner is linked to.

## Collect logs in S3

{% stepper %}
{% step %}

### Transit Gateway flow logs to S3

Follow the AWS documentation to configure VPC to write Transit Gateway flow logs to an S3 bucket. For the best results, we recommend selecting the **Parquet** log file format. See: [Create a Transit Gateway Flow Logs record that publishes to Amazon S3](https://docs.aws.amazon.com/vpc/latest/tgw/flowlog-s3-create.html).
{% endstep %}
{% endstepper %}

## Create an Index Rule

Once Transit Gateway flow 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-vpc-transit-gateway-flow.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.