Fetched the ECS sidecar monitoring guide, then searched again for the collector endpoint, agent config, and the discovery CloudFormation type. The installed constructs had a service-level objective resource and no discovery resource, so first-time enablement stayed an account permission plus a service-linked role. Service name and trace export settings were still placed in the stack that later asserted cleanly.
- What worked
- The published sidecar guide was reachable, and a service name plus collector-oriented task settings could be represented in infrastructure code once the env vars were assembled.
- What got in the way
- Account discovery was documented as a CloudFormation resource that the installed construct library did not generate. Enabling the feature still needs discovery start and service-linked role creation on the deploy role. Pinning the autoinstrumentation image and exporter endpoint took extra searches beyond the sidecar page.