> ## 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.

# Amazon ECS and AWS Fargate Logs and Traces

> Choose the right ingestion path for container stdout/stderr logs and distributed traces from Amazon ECS tasks and AWS Fargate workloads.

Amazon ECS and AWS Fargate emit container `stdout` / `stderr` logs from your tasks, plus distributed traces when your applications are instrumented with OpenTelemetry.

## Recommended method

[**ADOT**](./aws-adot) — the OpenTelemetry Collector running as a sidecar in your task definition (the same pattern on both EC2 launch type and Fargate) sends logs and traces directly to Bronto over OTLP. It bypasses CloudWatch and gives you consistent `service.name` / `service.namespace` routing across [Lambda](./aws-lambda), ECS, and [EKS](./aws-eks) workloads (see [Data Organization](/Search-and-Visualize/Partitions)).

## Alternatives

* [**ECS FireLens**](./aws-firelens) — Fluent Bit sidecar that ships logs from your task; lighter operational footprint than a full collector.
* [**CloudWatch Log Forwarder**](./aws-client-cloudwatch) — for tasks that already write to CloudWatch Log Groups via the `awslogs` driver.

See [Ingesting AWS Data into Bronto](./aws-overview) for the full service-to-method mapping.

## References

* [Amazon ECS — using FireLens for log routing](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_firelens.html)