AWS EKS

Scanner supports AWS EKS container logs and control plane logs. These logs can be generated by a few sources, including the containers running your application and the various Kubernetes control plane components of your cluster (eg. api, audit, authenticator, controllerManager, and scheduler). In order for Scanner to see them, you can configure EKS to publish logs to CloudWatch, forward to Kinesis Data Firehose, and then write them into an S3 bucket that Scanner is linked to.

Collect logs in S3

1

EKS to CloudWatch

Follow the AWS documentation to publish your EKS logs to one or more CloudWatch log groups.

For container logs (eg. your application logs), see: Send logs to CloudWatch Logs.

For control plane logs, see: Send control plane logs to CloudWatch Logs.

2

CloudWatch to Kinesis Data Firehose

Configure your CloudWatch log groups to push their logs to a Kinesis Data Firehose.

See: Send CloudWatch Logs to Firehose.

3

Kinesis Data Firehose to S3

A Kinesis Data Firehose can push logs to various destinations. We want to push to an S3 bucket that Scanner is linked to. Follow the AWS documentation to configure the Firehose to write to an S3 bucket.

See: Understand data delivery in Amazon Data Firehose.

Create an Index Rule

Once EKS logs are landing in your S3 bucket, Create an Index Rule to ingest the logs via Scanner Collect for fast search and detections.