Quick Setup Overview

This guide walks you through connecting Scanner to your AWS environment and ingesting your first logs. The entire process typically takes 30-45 minutes.

Overview

Scanner's architecture ensures you retain complete ownership of your data. Your logs stay in your S3 buckets, Scanner creates optimized index files (also stored in your account), and our compute environment makes your data searchable in seconds.

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: The person performing setup needs AWS permissions to create:

• S3 buckets

• IAM roles

• SNS topics

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