Scanner creates a dedicated AWS account for each customer. This AWS account runs Scanner's indexers and queriers. The indexers organize and make the data searchable, and the queriers perform search and analysis.
To connect with Scanner, customers set up AWS resources, either with infrastructure-as-code tools like CloudWatch, Terraform, or Pulumi, or through a manual setup walk through. Specifically, customers create a new S3 bucket to store Scanner's index files, and an IAM role that allows Scanner to read raw log data and organize it into the Scanner index files bucket.
Customers maintain custody of the data, so there is no vendor lock-in.
Once the setup is complete, Scanner starts monitoring the raw log data in your S3 bucket. When new log data files are uploaded, Scanner is notified via via SNS messages, which enables the indexers to begin their work immediately. The Scanner indexers are optimized to run in the same AWS region as your S3 buckets, which means that there are no S3 data transfer costs while minimizing latency.