> 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-cloudtrail.md). # AWS CloudTrail AWS CloudTrail is cloud audit log data that describes activity across your AWS accounts. This is one of the most valuable data sources for running detections in AWS. This guide walks through how to set up AWS CloudTrail as a log source in Scanner Collect, so that logs can be ingested from S3, normalized, and indexed for search and detection. ## Create an Index Rule Since AWS CloudTrail logs already land in S3, follow the [Create an Index Rule](/scanner/using-scanner-complete-feature-reference/data-ingestion/create-an-index-rule.md) guide to index them via Scanner Collect. ### AWS CloudTrail Defaults During creation, select `AWS: CloudTrail` as the source type to have the following defaults pre-populated: * **File Type**: `CloudTrailJson` * **Compression**: `Gzip` * **File Regex**: `.*/CloudTrail/.*\.json\.gz$` * **Transformations**: Add Metadata, Parse JSON Columns, ECS Normalization: AWS CloudTrail * **Timestamp Field**: `.eventTime` --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/aws-cloudtrail.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.