> 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/getting-started/quick-setup-overview.md).

# Quick Setup Overview

### Overview

Scanner has two moving parts, and each can run in your AWS account or in Scanner's:

* **Compute** (indexing, detections, search) runs in Scanner's AWS account with Managed Scanner, or in your own AWS account with BYOC Scanner. BYOC deployments are provisioned with the Scanner team; see [BYOC / Self-Hosted](/scanner/what-and-why/how-it-works/bring-your-own-cloud-byoc-self-hosted.md).
* **Storage** (the collect buffer and index buckets) lives in S3 buckets you own by default, or in a Scanner-owned AWS account.

Logs already in your own S3 buckets are indexed in place either way. This guide walks the most common path: Managed Scanner compute with storage in your own AWS account.

{% hint style="info" %}
If Scanner hosts your storage, the Scanner team completes [Step 1](/scanner/getting-started/step-1-aws-infrastructure-setup.md) for you during onboarding.
{% endhint %}

**What you'll accomplish:**

1. Set up AWS infrastructure and link your account to Scanner
2. Configure Scanner to index your logs
3. Connect your first data source
4. Validate data is flowing and searchable

### Before You Begin

**Required Permissions:** Not needed if Scanner hosts your storage. Otherwise, the person performing setup needs AWS permissions to create:

* S3 buckets
* IAM roles
* EventBridge rules

This is typically someone from DevOps, Infrastructure, or SRE.

**Information Needed**:

* Your AWS Account ID where logs are stored
* Name of at least one S3 bucket containing logs (e.g., CloudTrail logs)

**Scanner Access:**

* Accept your email invitation to Scanner
* Log in using Google Auth, username/password, or SSO (Okta, etc.)


---

# 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/getting-started/quick-setup-overview.md?ask=<question>&goal=<endgoal>
```

`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.