Overview
Bronto supports several methods for ingesting data from AWS environments. The right choice depends on where your logs originate, whether you need trace data, your infrastructure preferences, and cost constraints.Service-to-Method Mapping
Different AWS services suit different ingestion methods. The recommended method is the simplest path that gets the data into Bronto; alternatives may be preferable depending on your existing infrastructure or cost constraints. Each service name in the table below links to a per-source landing page with a short summary of what the service emits and the configuration entry points for that data.Ingestion Methods
Bronto supports the following AWS ingestion methods:- S3 Log Forwarder — Lambda subscribes to S3 events and forwards new log objects.
- CloudWatch Log Forwarder — Lambda subscribes to CloudWatch log groups and streams events.
- ECS FireLens — Fluent Bit sidecar in your ECS task definitions; no Lambda required.
- Fluent Bit on EKS — Fluent Bit DaemonSet that collects container logs from every EKS node.
- ADOT — ECS / EKS — AWS-managed OpenTelemetry Collector distribution for ECS and EKS workloads.
- ADOT Lambda Layer — OpenTelemetry instrumentation layer for AWS Lambda functions.
- Self-Managed OTel Collector — Your own OpenTelemetry Collector deployment for full control.
- EventBridge API Destinations — Native EventBridge rule that POSTs events directly to Bronto.
- AWS Kinesis Firehose — Direct delivery from a Kinesis Firehose stream.