Bronto for AWS
Centralize observability data across your tech stack
AWS teams generate massive observability data across EKS, Lambda, API Gateway, CloudFront, and microservices. By sending logs and metrics from CloudWatch to Bronto, teams can centralize logs, traces, and metrics across their services for 12 months, always hot and instantly searchable.
1. Create a Bronto account
Try Bronto with a 2 week free trial
By signing up, you agree to our Terms of Service and Privacy Policy.
Already have an account? Sign in
2. Connect your AWS account
Run AI investigations on-demand, automatically, or through the AWS DevOps agent via Bronto's MCP server. With all of your AWS data in one place, you can correlate logs across services without jumping between consoles.
Gather logs, traces, and metrics across AWS services


Amazon EKS & Fargate
Unified log visibility across Kubernetes namespaces
Bronto aggregates container logs from EKS clusters without per-node agents - Filebeat or Fluent Bit forward to Bronto's ingestion API. Platform teams get normalised, searchable logs across all services with AI-assisted anomaly detection.
Read more →AWS Lambda
Serverless observability without cold-start overhead
Bronto's OTel Lambda layer captures distributed traces and logs from function invocations, correlating them across upstream API Gateway events and downstream DynamoDB calls. Cold-start impacts are surfaced automatically.
Read more →Edge
Amazon CloudFront & CDN Edge
Normalised CDN log ingestion across multi-cloud edge
Bronto normalises log formats from CloudFront, Akamai, Fastly, and Cloudflare into a unified schema, giving teams a single pane of glass for edge performance, cache behaviour, and origin error rates.
Read more →Amazon CloudWatch & S3
Every log group and bucket, forwarded automatically
An account-level subscription filter streams every CloudWatch log group to Bronto, while S3 access logs and other files are forwarded as new objects arrive. No changes to how your services log.
Read more →Amazon API Gateway
Access and execution logs for every stage
Bronto ingests API Gateway access and execution logs across every stage, so teams can trace slow or failing requests from the edge through to the Lambda functions and services behind them.
Read more →Amazon ECS
Service logs through your existing OpenTelemetry Collector
Send ECS service and task logs to Bronto through the OpenTelemetry Collector or ADOT you already run. Logs are parsed at ingest and searchable alongside the rest of your AWS estate.
Read more →An observability platform agents can actually use
Plug your AWS telemetry into the AWS DevOps agent, Claude, or any MCP-compatible tool without rebuilding your stack.
Works with the AWS DevOps agent
Any MCP-compatible agent can query your AWS logs directly through the Bronto MCP server.
Cost-aware by design
Up to 100x cheaper than legacy hot tiers.
Context enrichment
Statement Patterns group similar logs so agents reason over structure instead of raw text.
Structured, not stringy
Every field parsed at ingest, so agent tool calls return typed JSON.
AI-native parsing
AWS log formats are recognised and parsed automatically.
AWS DevOps agent compared observability MCPs and ranked Bronto #1
We asked the AWS DevOps agent to evaluate Bronto, Elasticsearch and Grafana Loki as the telemetry layer for its investigations. Bronto scored highest for AI agent suitability because it never returned silent failures in the evaluation. This meant the AI agent never was misled by incomplete information.
Read the full evaluation →| System | AI Agent Suitability | Primary Issue |
|---|---|---|
| Bronto | High (9.4/10) | None significant |
| Elasticsearch/Lucene | Medium (5.3/10) | Silent failures from case/mapping issues |
| Grafana Loki | Low (4.6/10) | Limited discovery, minimal context |
Purchase a Bronto plan via the AWS marketplace
You can use your existing AWS procurement and consolidated billing to get started with Bronto easily and start centralizing your observability data in one platform.
How to send AWS data into Bronto
CloudWatch Logs → Bronto
Deploy Bronto's Lambda forwarder with Terraform or CloudFormation, and an account-level subscription filter streams every CloudWatch log group to Bronto automatically. No changes to how your services log.
Read the docs →AWS Distro for OpenTelemetry
Send logs, metrics, and traces from EKS, ECS, EC2, and Lambda to Bronto over standard OTLP using ADOT, AWS's own OpenTelemetry distribution. No proprietary agents, and no CloudWatch ingestion fees for the data you route directly.
Read the docs →AWS CodeBuild: Statement ID plugin
Add Bronto's Statement ID Maven plugin to your build (in CodeBuild or any CI pipeline) and every log line from your Java services links back to the exact file and line that produced it. One click from a log in Bronto to the source in GitHub.
Read the docs →Common questions
Give your AWS logs a better home
In the AI era, it's time to bring together your observability data in one place that is designed for long-term retention, instant search, and agentic workflows.


