| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
As Adaptive MxDR support logging through S3 or SQS, we have to export logs from cloudwatch to S3 and attach SQS to S3 bucket. Please follow below page to automate continuous export of logs from cloudwatch loggroup to S3 bucket using lambda.
CloudWatch Log Group to S3 Bucket Export Automation using Lambda
Once logs are available in the S3 bucket, If you wish to configure SQS, please follow below steps:
...
Integration Parameters
SQS:
Parameter Display Name | RequiredDefault Value | Description |
|---|---|---|
REGIONYes | N/A | Select the region of your S3 bucket |
QUEUE NAMEYes | N/A | The SQS queue name. |
ACCOUNT NUMBERYes | N/A | The account number for the SQS queue and S3 bucket. |
QUEUE ACCESS KEY ID | YesN/A | This is the 20 character ID associated with your Amazon IAM account. |
QUEUE SECRET ACCESS KEY | YesN/A | This is the 40 character access key associated with your Amazon IAM account. |
SOURCE DELETION OPTION | YesN/A | Whether to delete source files after they have been transferred to Chronicle. This reduces storage costs. Valid values are:
|
S3 BUCKET ACCESS KEY ID | No | This is the 20 character ID associated with your Amazon IAM account. Only specify if using a different access key for the S3 bucket. |
S3 BUCKET SECRET ACCESS KEY | No | This is the 40 character access key associated with your Amazon IAM account. Only specify if using a different access key for the S3 bucket. |
ASSET NAMESPACE | No | To assign an asset namespace to all events that are ingested from a particular feed, set the |
...