- Cloud Collectors Overview
- Administration
- Administrative Access
- Shareable Service Accounts
- Add Accounts for AWS Cloud Collectors
- Add Accounts for Cisco Duo Cloud Collector
- Add Accounts for Google Cloud Collectors
- Add Accounts for Microsoft Cloud Collectors
- Add Accounts for Okta Cloud Collectors
- Add Accounts for Salesforce Cloud Collectors
- Add Accounts for Splunk Cloud Collectors
- Add Accounts for Trend Micro Cloud Collectors
- Add Accounts for Wiz
- Define a Unique Site Name
- Sign Up for the Early Access Program
- Onboard Cloud Collectors
- Abnormal Security Cloud Collector
- AWS CloudTrail Cloud Collectors
- AWS CloudWatch Cloud Collector
- AWS S3 Cloud Collector
- AWS SQS Cloud Collector
- Azure Activity Logs Cloud Collector
- Azure Log Analytics Cloud Collector
- Azure Event Hub Cloud Collector
- Azure Storage Analytics Cloud Collector
- Box Cloud Collector
- Cato Networks Cloud Collector
- Cisco Duo Cloud Collector
- Cisco Umbrella Cloud Collector
- Cribl Cloud Collector
- CrowdStrike Cloud Collectors
- GCP Pub/Sub Cloud Collector
- Microsoft Defender XDR (via Azure Event Hub) Cloud Collector
- Microsoft Entra ID Context Cloud Collector
- Microsoft Entra ID Logs Cloud Collector
- Microsoft 365 Exchange Admin Reports Cloud Collector
- Supported Sources from Microsoft 365 Exchange Admin Reports
- Migrate to the Microsoft 365 Exchange Admin Reports Cloud Collector
- Prerequisites to Configure the Microsoft 365 Exchange Admin Reports Cloud Collector
- Configure the Microsoft 365 Exchange Admin Reports Cloud Collector
- Troubleshooting the Microsoft 365 Exchange Admin Reports Cloud Collector
- Microsoft 365 Management Activity Cloud Collector
- Microsoft Security Alerts Cloud Collector
- Microsoft Sentinel (via Event Hub) Cloud Collector
- Netskope Alerts Cloud Collector
- Netskope Events Cloud Collector
- Okta Cloud Collector
- Okta Context Cloud Collector
- Palo Alto Networks Cortex Data Lake Cloud Collector
- Proofpoint On-Demand Cloud Collector
- Proofpoint Targeted Attack Protection Cloud Collector
- Recorded Future Cloud Collector
- Salesforce Cloud Collector
- SentinelOne Alerts Cloud Collector
- SentinelOne Cloud Funnel Cloud Collector
- SentinelOne Threats Cloud Collector
- SentinelOne Cloud Collector
- Splunk Cloud Collector
- Symantec Endpoint Security Cloud Collector
- Trend Vision One Cloud Collector
- Zscaler ZIA Cloud Collector
- Webhook Cloud Collectors
- Wiz Issues Cloud Collector
- Wiz API Cloud Collector
- Troubleshooting Cloud Collectors
Migrate the AWS S3 Cloud Collector
The AWS S3 Cloud Collector was first introduced for early access on the SaaS Cloud Connectors platform.
With Exabeam Cloud Collectors, the AWS S3 Cloud Collector is now available for the Exabeam Security Operations Platform. The new cloud collector enables you to ingest logs into the Exabeam Security Operations Platform and use the Search app to find specific events in those logs. Migration to the new app is recommended.
License Requirements: No additional license is required. The Cloud Collectors app is included with your existing license.
SaaS Cloud Connectors Support: Both the SaaS Cloud Connectors and the new Cloud Collectors environments can run in parallel.
The following table displays the Custom Cloud Connector endpoints that are mapped to the new Cloud Collector AWS S3.
Legacy Connector | Legacy Endpoint | Legacy Configuration | New Collector | New Account |
|---|---|---|---|---|
Custom Application | endpoint-sqs | SQS Message Origin = S3_TO_SQS | AWS S3 | AWS |
If you use the authentication type s3-sqs-authn, you must migrate to the AWS account using the basic authentication method. If you use the authentication type stsassumerole, you must migrate to the AWS account using the STSAssumeRole authentication method.
When you are ready to migrate:
Stop the Custom Application Cloud Connector in the Cloud Connectors platform.
Verify the account status. If the account status displays the status as running, wait until the tasks that are running are complete, and the status changes to complete.
Follow the steps to Configure the AWS S3 Cloud Collector.
The AWS S3 Cloud Collector does not rely on any file naming or folder structure and instead verifies that:
The files are uncompressed or compressed in either ZIP or GZIP format.
Each line in the file equals one event (no support for multiline events).
Note
Preconfigured content support is not guaranteed with generic ingestion mechanisms such as AWS S3.