# Fastly

Scanner supports Fastly access logs, which contain information about HTTP requests processed by Fastly's Content Delivery Network (CDN). In order for Scanner to see these logs, you can configure Fastly to publish them to S3.

## Step 1: Publish to S3

You can configure Fastly to write logs to an S3 bucket using its **log streaming** feature. Follow the Fastly documentation to configure it to write log events to S3. See: [Log streaming: Amazon S3](https://docs.fastly.com/en/guides/log-streaming-amazon-s3).

Note: Make sure to set the **log line format** to **Blank**, which is the default. This is important to make sure Fastly writes log events properly in JSON format. See: [Changing log line formats](https://docs.fastly.com/en/guides/changing-log-line-formats).

## Step 2: Ingest via Scanner Collect

Follow the instructions [here](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/custom-logs-aws-s3) to ingest logs from S3 via Scanner Collect


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.
