Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.bronto.io/llms.txt

Use this file to discover all available pages before exploring further.

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. Before choosing a method, familiarise yourself with Bronto’s two endpoint types — the base endpoint accepts any format while the OTLP endpoints require protobuf via an agent. See Ingestion Endpoints for the full reference.

Ingestion Methods

Bronto supports the following AWS ingestion methods:

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.
Where the OpenTelemetry SDK supports your runtime, prefer OTel-based instrumentation — it sends logs and traces through one pipeline, gives you consistent service.name / service.namespace routing, and avoids CloudWatch ingestion fees. The ADOT Lambda Layer covers Lambda; ADOT or a Self-Managed OTel Collector cover ECS, EKS, and EC2 workloads.
AWS ServiceRecommended MethodAlternatives
AWS Lambda (logs + traces)ADOT Lambda Layer (OTel-supported runtimes)CloudWatch Log Forwarder (for stdout/stderr capture or unsupported runtimes), Self-Managed OTel Collector
Amazon ECS / FargateADOT (OTel)ECS FireLens, CloudWatch Log Forwarder
Amazon EKSADOT (OTel)Fluent Bit on EKS, Self-Managed OTel Collector
Amazon RDS / Aurora (PostgreSQL)CloudWatch Log ForwarderKinesis Firehose (high-volume)
Amazon RDS / Aurora (MySQL)CloudWatch Log ForwarderKinesis Firehose (high-volume)
AWS CloudTrailEventBridge API DestinationsS3 Log Forwarder, Kinesis Firehose (high-volume)
Amazon API GatewayCloudWatch Log ForwarderKinesis Firehose (high-volume access logs)
ALB / NLB access logsS3 Log Forwarder
VPC Flow LogsS3 Log ForwarderCloudWatch Log Forwarder, Kinesis Firehose
AWS WAFS3 Log ForwarderKinesis Firehose, CloudWatch Log Forwarder
Amazon DynamoDBEventBridge API Destinations (via CloudTrail)CloudWatch Log Forwarder
Amazon ElastiCacheCloudWatch Log ForwarderKinesis Firehose (high-volume)
Amazon CloudFront (real-time logs)Kinesis FirehoseS3 Log Forwarder (standard logs)
Amazon Route 53CloudWatch Log ForwarderS3 Log Forwarder (resolver query logs), Kinesis Firehose
AWS GuardDutyEventBridge API DestinationsS3 Log Forwarder
Amazon SESCloudWatch Log ForwarderKinesis Firehose
AWS Step FunctionsCloudWatch Log ForwarderEventBridge API Destinations
Amazon CognitoCloudWatch Log Forwarder

Bronto can be connected via an AWS VPC Private Link, keeping all traffic within the AWS network and avoiding public internet egress. This is available on request — contact support@bronto.io to set this up.