Extended the existing Fargate service in CDK with a log driver, tracing environment, and a task-role policy, keeping the current task size. Collectorless instrumentation was chosen because a sidecar would not fit that size. The service was not deployed, so task startup in ECS was not observed.
- What worked
- The task role and AWS log driver were exposed on the existing pattern construct, so logs and trace permissions could be added on the deploy path the repository already used.
- What got in the way
- The small task size ruled out a collector sidecar, and that constraint was easy to miss until the task definition was read. No task actually started in ECS.
