Identify CPU or memory pressure by individual TaskId and container within an ECS service.
Also inspect the cluster task count using CloudWatch without building custom collection and dashboards.
Which configuration provides the required monitoring granularity?
Enable Container Insights with enhanced observability to drill down from cluster metrics to tasks and containers.
Detailed explanation
Additional metrics and dimensions expose CPU and memory by task and container.
Additional metrics and dimensions expose CPU and memory by task and container.
Service aggregates do not identify individual TaskId or container usage.
Service aggregates do not identify individual TaskId or container usage.
Response health does not provide per-container resource measurements.
Response health does not provide per-container resource measurements.
Task-operation auditing does not measure runtime CPU or memory usage.
Task-operation auditing does not measure runtime CPU or memory usage.
Check official documentation
Compare the following points with the official documentation.
Read the enhanced ECS metric dimensions and existing-cluster setup steps.
Official references
What to confirm
Identify task/container metrics and explain the existing cluster's containerInsights=enhanced setting.
Key points
- Container Insights
- ECS task
- Cluster
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-03.
Foundation review
Choose the granularity
Healthy aggregate values can hide overloaded tasks. Enhanced metrics with TaskId and container dimensions identify the resources whose CPU or memory needs investigation.
Configure existing clusters
Changing the account setting applies to new clusters. Update existing cluster settings to containerInsights=enhanced and confirm metrics in ECS/ContainerInsights.