Configuring AWS CloudTrail Connectors

This connector allows Stellar Cyber to collect data from external sources and add the records to the data lake. The incoming information is included in Interflow records in the AWS Events index.

Integration with AWS and S3 enables organizations to securely store and manage their data while providing real-time threat detection and response capabilities through Stellar Cyber's advanced security analytics and machine learning algorithms.

You can have any number of AWS connectors active in the system. You will typically have one or two connectors for each account being used by anyone in the network.

However, if you have AWS Control Tower set up, you can use an asterisk as a wildcard character instead of a specific Account ID in the Prefix field.

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: AWS CloudTrail

Capabilities

Collect: Yes
Respond: No
Native Alerts Mapped: No
Runs on: DP
Interval: 5 minutes

Collected Data

Content Type	Index	Locating Records
cloudtrail vpcflow waf	AWS Events (non-traffic) Traffic (VPC flow)	msg_class: cloudtrail vpcflow aws_waf msg_origin.source: cloudtrail msg_origin.vendor: aws msg_origin.category: paas `waf` (for aws_waf)

Content Type

Index

Locating Records

cloudtrail

vpcflow

waf

AWS Events (non-traffic)

Traffic (VPC flow)

msg_class:

cloudtrail

vpcflow

aws_waf

msg_origin.source:

cloudtrail

msg_origin.vendor:

aws

msg_origin.category:

paas

waf (for aws_waf)

Domain

https://s3.amazonaws.com

https://s3-<Region>.amazonaws.com

https://<Bucket>.s3.amazonaws.com

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials and Configurations

For Access Key / Secret Key Auth Method: Access Key and Secret Key, plus Sub Type, Bucket, Prefix, and File Type
For IAM Role Auth Method: Source Account Access Key, Source Account Secret Key, and IAM Role ARN, plus Sub Type, Bucket, Prefix, and File Type

Adding an AWS CloudTrail Connector

To add an AWS CloudTrail connector:

Create an AWS CloudTrail trail
Add a user with the appropriate permissions
Create an access key
(Optional) Create an IAM role in same AWS account
(Optional) Create an IAM role across AWS accounts
Get the required information
(Optional) Set up AWS Control Tower
Add the connector in Stellar Cyber
Test the connector
Verify ingestion

Creating the AWS CloudTrail Trail

To create an AWS CloudTrail trail:

Use our example as a guideline, as you might be using a different software version.

Log in to your AWS Management Console at https://aws.amazon.com .
In Find Services, start entering cloudtrail. As you type, suggestions appear. Click on CloudTrail.

The CloudTrail Dashboard appears.
Click Create trail. The Choose trail attributes page appears.
Enter a Trail name.
Leave the default configurations for the various event information settings.
Under Storage location, choose Yes for Create a new S3 bucket.
Enter the name.

Make note of this, as you need the bucket name when configuring the connector in Stellar Cyber.
Enter the AWS KMS alias.
Leave the remaining options at the default settings.
Click Next. The Choose log events page appears.
Choose the events you want to send to Stellar Cyber. We recommend choosing all of them.
Click Next. The Review and create page appears.
Click Create trail. The trail is added, and displayed on the Trails page.

Adding a User with the Appropriate Permissions

To add a user with the appropriate permissions:

Log in to your AWS Management Console at https://aws.amazon.com/console. View the services in the Console Home or choose View all services.
Choose IAM. The IAM Dashboard appears.
Choose Policies and then choose Create Policy.
In the Create policy pane, choose the JSON tab.

Using the example below as a guide, edit the JSON policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

Copy

CloudTrail policy

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::stellarcybercloudtrail",
                "arn:aws:s3:::stellarcybercloudtrail/*"
            ]
        }
    ]
}

Choose Next.
Give your policy a name to associate it with Stellar Cyber, then choose Create policy.

The policy can now be attached to a user.
From the IAM navigation pane, choose Users and then choose Create user.
On the Specify user details page for User details, enter a User name for the new user.
Choose Provide user access to the – AWS Management Console optional to produce login credentials for the new user, such as a password.
Choose how you want to create the Console password and then choose Next.
On the Set permissions page, choose Attach policies directly. Then search for the policy you created above.
Select the checkbox to the left of the policy name, then choose Next.
On the Review and create page, verify the information and then choose Create user.

Creating an Access Key

The procedures in this section are for the Access Key / Secret Key Auth Method in Stellar Cyber.

Log in to the IAM Console with your AWS account ID, your IAM user name, and password. You must have the permissions required to create access keys for a user.
Choose Users, then click the user name, and click Security credentials.
In the Access keys section, choose Create access key. Access keys have two parts: an access key and a secret access key. Click Create access key.
On the Access key best practices & alternatives page, choose Other and then choose Next.
(Optional) On the Set description tag page, enter a description.
Click Create access key.
On the Retrieve access keys page, choose Show to reveal the value of the user's secret access key. Save the access key and secret access key in a secure location. You will need them when configuring the connector in Stellar Cyber.
Click Done.

(Optional) Creating an IAM Role in Same AWS Account

The procedures in this section are required for users who want to use the IAM Role Auth Method for the AWS resources, for an IAM role that is created in the same AWS account.

Create an IAM User Without Permissions and Create IAM Policy

Log in to your AWS Management Console at https://aws.amazon.com/console. View the services in the Console Home or choose View all services.
Choose IAM. The IAM Dashboard appears.
From the IAM navigation pane, choose Users and then click Create user.
On the Specify user details page for User details, enter a User name for the new user.
Choose Provide user access to the – AWS Management Console optional to produce login credentials for the new user, such as a password.
Choose how you want to create the Console password and then choose Next.
On the Set permissions page, choose Attach policies directly and click Create policy.
On the Specify permissions page, choose the JSON tab.

Using the example below as a guide, edit the JSON policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

In the following example, aws-cloudtrail-logs-001xxxxxx433-f361378d is the S3 bucket to store the AWS CloudTrail data.

Copy

CloudTrail policy - IAM Role - same AWS account

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::aws-cloudtrail-logs-001xxxxxx433-f361378d",
                "arn:aws:s3:::aws-cloudtrail-logs-001xxxxxx433-f361378d/*"
            ]
        }
    ]
}

Click Next.
Give your policy a name to associate it with Stellar Cyber, for example, Stellar-cloudtrail-policy.
Click Create policy.

Create an IAM Role with Trusted Entities

From the IAM navigation pane, choose Roles and then click Create Role.
Choose Custom trust policy.

Using the example below as a guide, edit the custom trust policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

Copy

Trusted entities - same AWS account

1
2
3
4
5
6
7
8
9
10
11
12
13
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Statement1",
            "Effect": "Allow",
            "Principal": {
                "AWS": "<User ARN>"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}

Click Next.
On the Add permissions page, select the permissions policy created earlier.
Click Next.
On the Name, review, and create page, enter a Role name.
Review the trusted entities and permissions, then click Create Role.
On the Roles page, use the Search box to find your role name.
Click your role name.
Copy your ARN, which you will need when configuring the connector in Stellar Cyber.

(Optional) Creating an IAM Role Across AWS Accounts

The procedures in this section are required for users who want to use the IAM Role Auth Method for the AWS resources, for an IAM role that is created across AWS accounts.

Create an IAM User for Source AWS Account and Create IAM Policy

Create this IAM user if you have a source AWS account like an MSSP AWS account.

When configuring the connector in Stellar Cyber, you will need the source AWS account (MSSP account) and the access key and secret key.

Log in to your AWS Management Console at https://aws.amazon.com/console. View the services in the Console Home or choose View all services.
Choose IAM. The IAM Dashboard appears.
From the IAM navigation pane, choose Users and then click Create user.
On the Specify user details page, enter a User name for the new user.
Choose Provide user access to the – AWS Management Console optional to produce login credentials for the new user, such as a password.
Choose how you want to create the Console password and then choose Next.
Choose Attach policies directly and click Create policy.
On the Specify permissions page, choose the JSON tab.

Using the example below as a guide, edit the JSON policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

Copy

CloudTrail policy - IAM Role - across AWS accounts

1
2
3
4
5
6
7
8
9
10
11
12
13
14
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sts:AssumeRole"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}

(Optional) To only allow the particular destination AWS account IAM role, using the example below as a guide, edit the JSON policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

Copy

CloudTrail policy - IAM Role - allow destination AWS account

1
2
3
4
5
6
7
8
9
10
11
12
13
14
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sts:AssumeRole"
            ],
            "Resource": [
                "arn:aws:iam::001xxxxxx433:role/Stellar-cloudtrail-role"
            ]
        }
    ]
}

Click Next.
Give your policy a name to associate it with Stellar Cyber, then choose Create policy.

(Optional) Create an IAM User for Destination AWS Account and Create IAM Policy

Create this IAM user if you have a destination AWS account like an MSSP's tenant AWS account.

When configuring the connector in Stellar Cyber, you will need the destination AWS account (MSSP's tenant account) and the IAM role ARN.

Log in to your AWS Management Console at https://aws.amazon.com/console. View the services in the Console Home or choose View all services.
Choose IAM. The IAM Dashboard appears.
From the IAM navigation pane, choose Users and then click Create user.
On the Specify user details page, enter a User name for the new user.
Choose Provide user access to the – AWS Management Console optional to produce login credentials for the new user, such as a password.
Choose how you want to create the Console password and then choose Next.
Choose Attach policies directly and click Create policy.
On the Specify permissions page, choose the JSON tab.

Using the example below as a guide, edit the JSON policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

In the following example, aws-cloudtrail-logs-001xxxxxx433-f361378d is the S3 bucket to store the AWS CloudTrail data.

Copy

CloudTrail policy - Stellar-cloudtrail-policy

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::aws-cloudtrail-logs-001xxxxxx433-f361378d",
                "arn:aws:s3:::aws-cloudtrail-logs-001xxxxxx433-f361378d/*"
            ]
        }
    ]
}

Click Next.
Give your policy a name to associate it with Stellar Cyber, then choose Create policy.

Create an IAM Role with Trusted Entities

From the IAM navigation pane, choose Roles and then click Create Role.
Choose Custom trust policy.

Using the example below as a guide, edit the custom trust policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

Copy

Trusted entities - across AWS accounts

1
2
3
4
5
6
7
8
9
10
11
12
13
14

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Statement1",
            "Effect": "Allow",
            "Principal": {
                "AWS": "<User ARN>"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}

Click Next.
On the Add permissions page, select the permissions policy created earlier.
Click Next.
On the Name, review, and create page, enter a Role name.
Review the trusted entities and permissions, then click Create Role.
On the Roles page, use the Search box to find your role name.
Click your role name.
Copy your ARN, which you will need when configuring the connector in Stellar Cyber.

Getting the Required Information

To add the connector in Stellar Cyber you need the following for the Access Key / Secret Key Auth Method:

Access key and Secret Access key—See Creating an Access Key
Bucket—See Creating the AWS CloudTrail Trail
Prefix—See Getting the Prefix

To add the connector in Stellar Cyber you need the following for the IAM Role Auth Method:

Source Account Access Key, Source Account Secret Key, and Bucket—See (Optional) Create an IAM role in same AWS account or (Optional) Create an IAM role across AWS accounts
Prefix—See Getting the Prefix

Getting the Prefix

To get the prefix:

In the CloudTrail Dashboard, click Trails. The existing trails appear.
For the trail you are using, the Bucket is the name in the S3 bucket column.
Click the bucket name. The bucket info appears.
Click the CloudTrail object.

The regional objects appear.
Click your region.

Click Copy S3 URI. The Prefix is the path starting with AWSLogs (the default) and ending with the region.

Do not copy the trailing "/" symbol.

If you're configuring an AWS WAF connector and you have a custom prefix , use your custom prefix. If you are using a date in your custom prefix, you must replace static numbers with variables, converting the prefix to a pattern that Stellar Cyber can recognize. Following are the variables.

Variable	Definition
//YYYY//	4 digit year
//m//	1 or 2 digit month
//mm//	2 digit month
//d//	1 or 2 digit day
//dd//	2 digit day
//H//	1 or 2 digit hour
//HH//	2 digit hour
//M//	1 or 2 digit minute
//MM//	2 digit minute

For example, CustomPrefix/year=/2020/month=/10/day=/27/ becomes CustomPrefix/year=///YYYY///month=///mm///day=///dd//.

For the CloudTrail connector, the supported prefix syntax may also include Organization ID, as shown here:

Without Organization ID:
- optional_prefix_name/AWSLogs/Account ID/<CloudTrail>/region
- optional_prefix_name/AWSLogs/Account ID/<vpcflowlogs>/region
With Organization ID:
- optional_prefix_name/AWSLogs/OU-ID/Account ID/<CloudTrail>/region
- optional_prefix_name/AWSLogs/OU-ID/Account ID/<vpcflowlogs>/region

(Optional) Setting up AWS Control Tower

There are two types of AWS Control Tower: SSE-S3 encryption (default) and SSE-KMS encryption.

To set up the default AWS Control Tower (SSE-S3 encryption), refer to the AWS Control Tower documentation.

To set up the AWS Control Tower with SSE-KMS encryption, follow these procedures:

Create symmetric encryption KMS keys
Set up the AWS Control Tower on your management account
Create an IAM User

Creating Symmetric Encryption KMS Keys

To create symmetric encryption KMS keys:

Log in to your management account (YOUR-MANAGEMENT-ACCOUNT).
Follow the guidance in the AWS documentation to create your KMS key (YOUR-KMS-KEY-ID).

Using the example below as a guide, edit the JSON policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

Copy

Policy

{
    "Version": "2012-10-17",
    "Id": "CustomKMSPolicy",
    "Statement": [
        {
        ... YOUR-EXISTING-POLICIES ...
        },
        {
            "Sid": "Allow Config to use KMS for encryption",
            "Effect": "Allow",
            "Principal": {
                "Service": "config.amazonaws.com"
            },
            "Action": [
                "kms:Decrypt",
                "kms:GenerateDataKey"
            ],
            "Resource": "arn:aws:kms:YOUR-HOME-REGION:YOUR-MANAGEMENT-ACCOUNT-ID:key/YOUR-KMS-KEY-ID"
        },
        {
            "Sid": "Allow CloudTrail to use KMS for encryption",
            "Effect": "Allow",
            "Principal": {
                "Service": "cloudtrail.amazonaws.com"
            },
            "Action": [
                "kms:GenerateDataKey*",
                "kms:Decrypt"
              ],
            "Resource": "arn:aws:kms:YOUR-HOME-REGION:YOUR-MANAGEMENT-ACCOUNT-ID:key/YOUR-KMS-KEY-ID",
            "Condition": {
                "StringEquals": {
                    "aws:SourceArn": "arn:aws:cloudtrail:YOUR-HOME-REGION:YOUR-MANAGEMENT-ACCOUNT-ID:trail/aws-controltower-BaselineCloudTrail"
                },
                "StringLike": {
                    "kms:EncryptionContext:aws:cloudtrail:arn": "arn:aws:cloudtrail:*:YOUR-MANAGEMENT-ACCOUNT-ID:trail/*"
                }
            }
        },
        {
            "Sid": "Allow user to use KMS for encryption",
            "Effect": "Allow",
            "Principal": {
                "AWS": "<user ARN>"
            },
            "Action": "kms:Decrypt",
            "Resource": "arn:aws:kms:YOUR-HOME-REGION:YOUR-MANAGEMENT-ACCOUNT-ID:key/YOUR-KMS-KEY-ID"
        }
    ]
}

In various places in the JSON policy document, provide the following:
- YOUR-HOME-REGION
- YOUR-MANAGEMENT-ACCOUNT-ID
- YOUR-KMS-KEY-ID
- <user ARN> (the user that will be used for the connector)

Setting up the AWS Control Tower on your Management Account

You can now set up the AWS Control Tower on your management account with the KMS key you created earlier.

Log in to AWS CloudTrail with your AWS account (YOUR-MANAGEMENT-ACCOUNT).
Follow the guidance in the following documentation to deploy a landing zone with AWS Control Tower.
In the following graphic, YOUR-MANAGEMENT-ACCOUNT ends in 4429. The CloudTrail S3 bucket is in the 9809 AWS account (the Log-archive account).

Creating an IAM User

Next, create an IAM user. You can refer to Adding a User with the Appropriate Permissions.

Log into the Log-archive account (9809).

Using the example below as a guide, edit the JSON policy document.

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

Copy

Policy for the user

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:ListBucket",
            ],
            "Resource": [
                "<S3 bucket ARN>",
                "<S3 bucket ARN>/*"
            ]
        },
        {
            "Sid": "KMSDecryptionPermission",
            "Effect": "Allow",
            "Action": [
                "kms:Decrypt"
            ],
            "Resource": [
                "arn:aws:kms:YOUR-HOME-REGION:YOUR-MANAGEMENT-ACCOUNT-ID:key/YOUR-KMS-KEY-ID"
            ]
        }
    ]
}

In the JSON policy document, provide the following:
- YOUR-HOME-REGION
- YOUR-MANAGEMENT-ACCOUNT-ID
- YOUR-KMS-KEY-ID
- <S3 bucket ARN>
Generate the access key and security key for this user. You can refer to Creating an Access Key.

Adding the Connector in Stellar Cyber

With the required information handy, you can add the AWS CloudTrail connector in Stellar Cyber:

Log in to Stellar Cyber.
Click System | Connectors (under Integrations). The Connector Overview appears.
Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

The asterisk (*) indicates a required field.
Choose PaaS from the Category drop-down.
Choose AWS Cloudtrail from the Type drop-down.
For this connector, the supported Function is Collect, which is enabled already.
Enter a Name.
Notes:
- This field does not accept multibyte characters.
- It is recommended that you follow a naming convention such as tenantname-connectortype.
Choose a Tenant Name. The Interflow records created by this connector include this tenant name.
Choose the device on which to run the connector.
- Certain connectors can be run on either a Sensor or a Data Processor. The available devices are displayed in the Run On menu. If you want to associate your collector with a sensor, you must have configured that sensor prior to configuring the connector or you will not be able to select it during initial configuration. If you select Data Processor, you will need to associate the connector with a Data Analyzer profile as a separate step. That step is not required for a sensor, which is configured with only one possible profile.
- If the device you're connecting to is on premises, we recommend you run on the local sensor. If you're connecting to a cloud service, we recommend you run on the DP.
(Optional) When the Function is Collect, you can apply Log Filters. For information, see Managing Log Filters.
Click Next. The Configuration tab appears.

The asterisk (*) indicates a required field.
Choose the Auth Method to use Access Key / Secret Key or IAM Role.

For Access Key / Secret Key Auth Method:
1. Enter the Access Key from IAM.
2. Enter the Secret Key from IAM.
For IAM Role Auth Method:

The asterisk (*) indicates a required field.
1. Enter the Source Account Access Key.
2. Enter the Source Account Secret Key.
  The IAM role can be across multiple AWS accounts:
  - For the source account, provide the trusted IAM user's access key and secret key. Refer to Creating an Access Key.
  - For the destination account, provide the AWS IAM role, in which this role is trusting the source account IAM user. Refer to (Optional) Creating an IAM Role Across AWS Accounts.
3. Enter the IAM Role ARN.
Choose a Sub Type.
- cloudtrail—feeds account activity information, including actions taken through the AWS Management Console and various AWS SDKs and command line tools. See the AWS CloudTrail documentation for details.
- vpcflow—provides network-level information. See the AWS VPC documentation for details.
- waf—provides Web Application Firewall information. See the AWS WAF documentation for details.
(Optional) Enter the Proxy URI, if you have one.
Enter the Bucket you noted above.
Enter the Prefix you noted above. Ensure the Prefix does not include a trailing "/" symbol.

The supported prefix syntax is as follows:
- Without Organization ID: optional_prefix_name/AWSLogs/Account ID/<CloudTrail or vpcflowlogs>/region
- With Organization ID: optional_prefix_name/AWSLogs/OU-ID/Account ID/<CloudTrail or vpcflowlogs>/region

With AWS Control Tower: optional_prefix_name/OU-ID/AWSLogs/OU-ID/*/<CloudTrail or vpcflowlogs>/region

The Sub Type must be cloudtrail or vpcflow.

Enter the File Type. The cloudtrail and vpcflow sub types should always be gzip. The waf sub type can be gzip or text.
(Optional) Choose a Region from the available regions in the drop-down.
Click Next. The final confirmation tab appears.
Click Submit.

To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.
If you are adding rather than editing a connector with the Collect function enabled and you specified for it to run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.
- This prompt only occurs during the initial create connector process when Collect is enabled.
- Certain connectors can be run on either a Sensor or a Data Processor, and some are best run on one versus the other. In any case, when the connector is run on a Data Processor, that connector must be included in a Data Analyzer profile. If you leave it out of the default profile, you must add it to another profile. You need the Administrator Root scope to add the connector to the Data Analyzer profile. If you do not have privileges to configure Data Analyzer profiles, a dialog displays recommending you ask your administrator to add it for you.
- The first time you add a Collect connector to a profile, it pulls data immediately and then not again until the scheduled interval has elapsed. If the connector configuration dialog did not offer an option to set a specific interval, it is run every five minutes. Exceptions to this default interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub (continuously pulls data) connectors. The intervals for each connector are listed in the Connector Types & Functions topic.
The Connector Overview appears.

The new connector is immediately active and starts collecting logs.

Testing the Connector

If you have AWS Control Tower, the Test button tests all account IDs.

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates authentication and connectivity).

Click System | Connectors (under Integrations). The Connector Overview appears.
Locate the connector by name that you added, or modified, or that you want to test.
Click Test at the right side of that row. The test runs immediately.

Note that you may run only one test at a time.

Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful test indicates that you entered all of the connector information correctly.

To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the test fails, you can select the button from the same row to review and correct issues.

The connector status is updated every five (5) minutes. A successful test clears the connector status, but if issues persist, the status reverts to failed after a minute.

Repeat the test as needed.

Display sample messages...

If the test fails, the common HTTP status error codes are as follows:

HTTP Error Code	HTTP Standard Error Name	Explanation	Recommendation
400	Bad Request	This error occurs when there is an error in the connector configuration.	Did you configure the connector correctly?
401	Unauthorized	This error occurs when an authentication credential is invalid or when a user does not have sufficient privileges to access a specific API.	Did you enter your credentials correctly? Are your credentials expired? Are your credentials entitled or licensed for that specific resource?
403	Forbidden	This error occurs when the permission or scope is not correct in a valid credential.	Did you enter your credentials correctly? Do you have the required role or permissions for that credential?
404	Not Found	This error occurs when a URL path does not resolve to an entity.	Did you enter your API URL correctly?
429	Too Many Requests	This error occurs when the API server receives too much traffic or if a user’s license or entitlement quota is exceeded.	The server or user license/quota will eventually recover. The connector will periodically retry the query. If this occurs unexpectedly or too often, work with your API provider to investigate the server limits, user licensing, or quotas.

For a full list of codes, refer to HTTP response status codes.

Verifying Ingestion

To verify ingestion:

Click Investigate | Threat Hunting. The Interflow Search tab appears.
Change the Indices to include either or both of AWS Events or Traffic. The table immediately updates to show ingested Interflow records.