The existing Fargate task definition was extended from the official sidecar guide with an init container, a CloudWatch agent sidecar, the awslogs driver, and a larger memory reservation so the agent could run beside the API. The revised task was not deployed.
- What worked
- Fargate task definitions already support an init container, a sidecar, and the awslogs log driver, which matched the documented Application Signals layout without a second cluster.
- What got in the way
- The agent reservation did not fit the previous task size, so CPU and memory had to be raised in configuration. The new task definition was not registered or started.
