Skip to main content

CollectorsCloud Collectors Administration Guide

Table of Contents

Prerequisites to Configure the SentinelOne Cloud Funnel Cloud Collector

Before you configure the SentinelOne Cloud Funnel Cloud Collector, complete the following prerequisites:

Note

This guide assumes an existence of S3 bucket, and an SQS queue. Before you begin, identify the names for your S3 Bucket and the SQS queue ARNs. If you do not know the names for your S3 Bucket and the SQS queue ARNs, you can find them on the AWS Web Console or use the CLI. Configure the S3 bucket and the SQS queue such that whenever a new object is put into the S3 bucket, the SQS queue gets a notification.

Create the S3 Bucket

For storing your data and for providing SentinelOne with permissions: write objects and list objects, and sharing your S3 details to SentinelOne, create the S3 bucket.

To create the S3 bucket:

  1. Log in to the AWS console with your credentials.

  2. Navigate to the S3 console and click Create bucket. For more information see Creating a Bucket in the AWS documentation. While creating a bucket, when you specify a name for your S3 bucket, ensure that the bucket name is unique and follows the Bucket naming rules mentioned by AWS. For example, mylogs.mycompanyname.

  3. After creating a bucket, add SentinelOne to the list of accounts that can read and write objects in your S3 bucket. For more information see Configuring ACLs.

    1. Access the AWS Console.

    2. In the Buckets list, click the name of the bucket for which you want to set permissions.

    3. Click Permissions.

    4. Scroll down to Access Control List (ACL) and click Edit.

      Prerequisites_1.png

    5. Click Add grantee.

      Prerequisites_2.png

    6. Enter our [email protected] canonical ID: c768943f39940f1a079ee0948ab692883824dcb6049cdf3d7725691bf4f31cbb.

      Prerequisites_3.png

    7. Enable both List and Write objects.

    8. Click Save changes.

Configure S3/SQS Integration

Use the following steps to configure the SQS queue that receives a notification when new objects are added to the S3 Bucket.

  1. In the AWS Web Console, navigate to the S3 bucket where the data is located.

  2. Under Properties, enable event notification for the SQS queue in the S3 bucket on which you want to receive logs.

    For more information, see Enable Event Notifications in the AWS documentation.

  3. Choose All object create events events to be notified.

    Configure_S3SQS_Integration_updated.png

  4. Allow the S3 Bucket to send events to the SQS Queue.

  5. Replace the access policy attached to the queue with the following policy (in the SQS console, you select the queue, and in the Access policy tab, click Edit Access policy (Permissions).

    {
   "Version":"2012-10-17",
   "Id":"example-ID",
   "Statement":[
      {
         "Sid":"example-statement-ID",
         "Effect":"Allow",
         "Principal":{
            "AWS":"*"
         },
         "Action":[
            "SQS:SendMessage"
         ],
         "Resource":"SQS-queue-ARN",
         "Condition":{
            "ArnLike":{
               "aws:SourceArn":"arn:aws:s3:*:*:bucket-name"
            }
         }
      }
   ]
}

Obtain the SQS Properties

To obtain the SQS properties (SQS URL, SQS Region, and the SQS Message Origin), log in to your AWS account and refer to the following steps:

  • SQS URL – Go to the SQS service and check the SQS Queue used for the S3 events notifications. In the Details tab copy the URL value.

    360012776914-mceclip0.png

  • SQS Region – In the SQS Service page in the SQS Details tab, you view the SQS region. It is the string between the sqs and amazonaws strings in the URL. In the example above, the region is: us-east-1.

  • SQS Message Origin – Based on the integration you are configuring; messages are put in the queue in different ways.

    • For the messages put in the queue by the above setup, in which S3 notifies the SQS directly, select S3_TO_SQS.

    • For the messages put in the queue using the above method, in which the messages are sent from S3 to SNS, and then configured in SNS to be sent to SQS, select S3_TO_SNS_TO_SQS.