Amazon AWS S3 REST API log source parameters for Amazon AWS Route 53 when using a directory prefix

If you want to collect AWS Route 53 Resolver query logs from a single account and region in an Amazon S3 bucket, add a log source on the IBM® QRadar Console that uses the Amazon AWS S3 REST API protocol with a directory prefix.

When you use the Amazon AWS S3 REST API protocol with a directory prefix, there are specific parameters that you must configure.

The following table describes the parameters that require specific values to collect Amazon AWS S3 REST API events from Amazon AWS Route 53:

Table 1. Amazon AWS S3 REST API log source parameters for the Amazon AWS Route 53 DSM
Parameter	Value
Log Source type	Amazon AWS Route 53
Protocol Configuration	Amazon AWS S3 REST API
Log Source Identifier	Type a unique name for the log source. The Log Source Identifier can be any valid value and does not need to reference a specific server. The Log Source Identifier can be the same value as the Log Source Name. If you have more than one Amazon AWS Route 53 log source that is configured, you might want to identify the first log source as `awsroute53-1`, the second log source as `awsroute53-2`, and the third log source as `awsroute53-3`.
Authentication Method	Access Key ID / Secret Key Standard authentication that can be used from anywhere. For more information about configuring security credentials, see Configuring security credentials for your AWS user account. Assume IAM Role Authenticate with keys and then temporarily assume a role for access. This option is available only when you use the SQS Event Notifications collection method. For more information about creating IAM users and assigning roles, see Creating an Identity and Access Management (IAM) user in the AWS Management Console. EC2 Instance IAM Role If your managed host is running on an AWS EC2 instance, choosing this option uses the IAM Role from the instance metadata that is assigned to the instance for authentication; no keys are required. This method works only for managed hosts that are running within an AWS EC2 container.
Access Key ID	If you selected Access Key ID / Secret Key for the Authentication Method, the Access Key ID parameter is displayed. The Access Key ID that was generated when you conﬁgured the security credentials for your AWS user account. This value is also the Access Key ID that is used to access the AWS S3 bucket.
Secret Key	If you selected Access Key ID / Secret Key for the Authentication Method, the Secret Key ID parameter is displayed. The Secret Key that was generated when you conﬁgured the security credentials for your AWS user account. This value is also the Decret Key ID that is used to access the AWS S3 bucket.
Event Format	Select AWS Cloud Trail JSON. The log source retrieves JSON formatted events.
S3 Collection Method	Select Use a Specific Prefix.
Bucket Name	The name of the AWS S3 bucket where the log files are stored.
Directory Prefix	The root directory location on the AWS S3 bucket from where the Resolver logs are retrieved; for example, AWSLogs/<`AccountNumber`>/Resolver/<`RegionName`>/ To pull files from the root directory of a bucket, you must use a forward slash (/) in the Directory Prefix file path. Note: Changing the Directory Prefix value clears the persisted file marker. All files that match the new prefix are downloaded in the next pull. The Directory Prefix file path cannot begin with a forward slash (/) unless only the forward slash is used to collect data from the root of the bucket. If the Directory Prefix file path is used to specify folders, you must not begin the file path with a forward slash (for example, use folder1/folder2 instead).
Region Name	The region that the SQS Queue or the AWS S3 bucket is in. Example: us-east-1, eu-west-1, ap-northeast-3
Use as a Gateway Log Source	Select this option for the collected events to flow through the QRadar Trafﬁc Analysis engine and for QRadar to automatically detect one or more log sources.
Log Source Identifier Pattern	This option is available when Use as a Gateway Log Source is set to yes. Use this option if you want to deﬁne a custom Log Source Identiﬁer for events being processed. This ﬁeld accepts key value pairs to deﬁne the custom Log Source Identiﬁer, where the key is the Identiﬁer Format String, and the value is the associated regex pattern. You can deﬁne multiple key value pairs by entering a pattern on a new line. When multiple patterns are used, they are evaluated in order until a match is found and a custom Log Source Identiﬁer can be returned.
Show Advanced Options	Select this option if you want to customize the event data.
File Pattern	This option is available when you set Show Advanced Options to Yes. Type a regex for the ﬁle pattern that matches the ﬁles that you want to pull; for example, .*?\.json\.gz
Local Directory	This option is available when you set Show Advanced Options to Yes. The local directory on the Target Event Collector. The directory must exist before the AWS S3 REST API PROTOCOL attempts to retrieve events.
S3 Endpoint URL	This option is available when you set Show Advanced Options to Yes. The endpoint URL that is used to query the AWS S3 REST API. If your endpoint URL is different from the default, type your endpoint URL. The default is `https://s3.amazonaws.com`.
Use S3 Path-Style Access	Forces S3 requests to use path-style access. This method is deprecated by AWS. However, it might be required when you use other S3 compatible APIs. For example, the https://s3.region.amazonaws.com/bucket-name/key-name path-style is automatically used when a bucket name contains a period (.). Therefore, this option is not required, but can be used.
Use Proxy	If QRadar accesses the Amazon Web Service by using a proxy, enable Use Proxy. If the proxy requires authentication, configure the Proxy Server, Proxy Port, Proxy Username, and Proxy Password fields. If the proxy does not require authentication, configure the Proxy IP or Hostname field.
Recurrence	How often a poll is made to scan for new data. If you are using the SQS event collection method, SQS Event Notifications can have a minimum value of 10 (seconds). Because SQS Queue polling can occur more often, a lower value can be used. If you are using the Directory Prefix event collection method, Use a Specific Prefix has a minimum value of 60 (seconds) or 1M. Because every listBucket request to an AWS S3 bucket incurs a cost to the account that owns the bucket, a smaller recurrence value increases the cost. Type a time interval to determine how frequently the poll is made for new data. The time interval can include values in hours (H), minutes (M), or days (D). For example, 2H = 2 hours, 15M = 15 minutes, 30 = seconds.
EPS Throttle	The maximum number of events per second that QRadar ingests. If your data source exceeds the EPS throttle, data collection is delayed. Data is still collected and then it is ingested when the data source stops exceeding the EPS throttle. The default is 5000.

For more information about the Amazon AWS S3 REST API protocol, see Amazon AWS S3 REST API protocol configuration options.