Data ingestion mechanisms and intervals in Data Manager
The following table shows the data ingestion mechanisms and intervals in Data Manager. Use this table to verify the timing for how often your data is processed.
Data Sources | Data Ingestion Mechanism | Data Interval |
---|---|---|
Amazon API Gateway | Pushed from Amazon CloudWatch Log Groups to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on CloudWatch. |
AWS CloudHSM | Pushed from Amazon CloudWatch Log Groups to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on CloudWatch. |
Amazon Web Services (AWS) CloudTrail | Pushed from Amazon CloudWatch Log Groups to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on CloudWatch. |
Amazon DocumentDB | Pushed from Amazon CloudWatch Log Groups to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on CloudWatch. |
Amazon Elastic Kubernetes Service (Amazon EKS) | Pushed from Amazon CloudWatch Log Groups to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on CloudWatch. |
Amazon GuardDuty | Pushed from Amazon EventBridge to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on EventBridge. By default, AWS makes the GuardDuty Findings available to EventBridge every 6 hours. These settings can be changed to every 1 hour or every 15 minutes. |
AWS Lambda | Pushed from Amazon CloudWatch Log Groups to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on CloudWatch. |
AWS Metadata - AWS Identity and Access Management (IAM) Users | AWS Lambda makes AWS API calls and ingests to the HTTP Event Collector (HEC) directly. | Polling for existing IAM users on a scheduled rate every 3 hours. |
AWS Metadata - Elastic Compute Cloud (Amazon EC2) Instances | AWS Lambda makes AWS API calls and ingests to the HTTP Event Collector (HEC) directly. | Polling for existing EC2 instances on a scheduled rate every 3 hours. New EC2 Instance creation events are ingested immediately to Splunk. |
AWS Metadata - EC2 Security Groups | AWS Lambda makes AWS API calls and ingests to the HTTP Event Collector (HEC) directly. | Polling for existing EC2 Security Groups on a scheduled rate every 3 hours. New EC2 Security Group creation events are ingested immediately to Splunk. |
AWS Metadata - Network ACLs | AWS Lambda makes AWS API calls and ingests to the HTTP Event Collector (HEC) directly. | Polling for existing Network ACLs on a scheduled rate every 3 hours. New Network ACL creation events are ingested immediately to Splunk. |
AWS IAM Access Analyzer | Pushed from Amazon EventBridge to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on EventBridge. |
AWS IAM Credential Report | AWS Lambda makes AWS API calls and ingests to the HTTP Event Collector (HEC) directly. | Fetches and ingests the IAM Credential Report every 5 hours. |
Amazon Relational Database Service (Amazon RDS) | Pushed from Amazon CloudWatch Log Groups to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC). | Immediately as soon as AWS makes data available on CloudWatch. |
AWS Security Hub | Pushed from Amazon EventBridge to Amazon Kinesis Data Firehose to the HTTP Event Collector (HEC) | Immediately as soon as AWS makes data available on EventBridge. |
Overview of source types for Data Manager | Prerequisites for onboarding AWS data sources |
This documentation applies to the following versions of Data Manager: 1.4.1
Feedback submitted, thanks!