I fit observability to the existing Fargate service by keeping export in the API process and shipping stdout with the awslogs driver, plus a task role that can write traces. Sidecar guidance asked for a large share of a half-vCPU task, so I did not add a sidecar. The task definition changes were not deployed.
- What worked
- The existing awslogs driver and task role were enough to describe log shipping and trace permissions without a second container.
- What got in the way
- I did not register a new task definition or watch a running task, so the driver and role changes were not observed in the service.
