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: Configure Fastly to stream logs 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.
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.
Step 2: Link your S3 bucket to Scanner
If you haven't done so already, link the S3 bucket containing your Fastly logs to Scanner using the Linking AWS Accounts guide.
Step 3: Set up an S3 Import Rule in Scanner
Within Scanner, navigate to Settings > S3 Import Rules.
Click Create Rule.
For Rule name, type a name like
my_team_name_fastly_access_logs.For Destination Index, choose the index where you want these logs to be searchable in Scanner.
For Status, set to Active if you want to start indexing the data immediately.
For Source Type, we recommend
fastly:access, but you are free to choose any name. However, out-of-the-box detection rules will expectfastly:access.For AWS Account, choose the account that contains the S3 bucket containing Fastly access logs.
For S3 Bucket, choose the S3 bucket containing Fastly access logs.
For S3 Key Prefix, type the prefix (i.e. directory path) where the Fastly is writing logs.
For File type, choose JsonLines with Gzip compression.
For Timestamp extractors, under Column name, type
timestamp. This is the field in each log event that contains the timestamp information.Click Preview rule to try it out. Check that the S3 keys you expect are appearing, and check that the log events inside are being parsed properly with the timestamp detected properly.
When you're ready, click Create.
Last updated