AWS Route53 Resolver

Last updated 7 months ago

Was this helpful?

AWS Route53 Resolver

Scanner supports AWS Route53 Resolver logs, which contain information about DNS queries. In order for Scanner to see these logs, you can configure Route53 to publish them to S3.

Step 1: Configure Route53 Resolver to write logs to S3

You can follow the AWS documentation to configure the Route53 Resolver to write DNS query logs to an S3 bucket. See: .

Step 2: Link the S3 bucket to Scanner

If you haven't done so already, link the S3 bucket containing your Route53 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_aws_route53_resolver_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 aws:route53_resolver, but you are free to choose any name. However, out-of-the-box detection rules will expect aws:route53_resolver.
For AWS Account, choose the account that contains the S3 bucket containing Route53 Resolver logs.
For S3 Bucket, choose the S3 bucket containing your Route53 Resolver logs.
For S3 Key Prefix, type the prefix (i.e. directory path) where Route53 is writing logs. This is usually just AWSLogs/. We will use Additional Regex to refine the selection further.
Click + Additional Regex, and type: .*/vpcdnsquerylogs/.*\.log\.gz
1. This will ensure that we only index files gzipped JSON files in the directory /vpcdnsquerylogs/, and skip any files in other directories.
For File type, choose JsonLines with Gzip compression.
For Timestamp extractors, under Column name, type query_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.

PreviousAWS Lambda NextAWS VPC Flow

Last updated 7 months ago

Was this helpful?

Scanner supports AWS Route53 Resolver logs, which contain information about DNS queries. In order for Scanner to see these logs, you can configure Route53 to publish them to S3.

Step 1: Configure Route53 Resolver to write logs to S3

You can follow the AWS documentation to configure the Route53 Resolver to write DNS query logs to an S3 bucket. See: .

Step 2: Link the S3 bucket to Scanner

If you haven't done so already, link the S3 bucket containing your Route53 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_aws_route53_resolver_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 aws:route53_resolver, but you are free to choose any name. However, out-of-the-box detection rules will expect aws:route53_resolver.
For AWS Account, choose the account that contains the S3 bucket containing Route53 Resolver logs.
For S3 Bucket, choose the S3 bucket containing your Route53 Resolver logs.
For S3 Key Prefix, type the prefix (i.e. directory path) where Route53 is writing logs. This is usually just AWSLogs/. We will use Additional Regex to refine the selection further.
Click + Additional Regex, and type: .*/vpcdnsquerylogs/.*\.log\.gz
1. This will ensure that we only index files gzipped JSON files in the directory /vpcdnsquerylogs/, and skip any files in other directories.
For File type, choose JsonLines with Gzip compression.
For Timestamp extractors, under Column name, type query_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.