AWS AmazonECS documentation change
Summary
Added section about high-resolution service metrics, enabling 20-second monitoring resolution for faster auto scaling detection.
Security assessment
The change documents performance monitoring enhancements without any security context. It describes operational improvements for auto scaling responsiveness but doesn't address vulnerabilities or security features.
Diff
diff --git a/AmazonECS/latest/developerguide/service_utilization.md b/AmazonECS/latest/developerguide/service_utilization.md index 35eabf439..675c2f266 100644 --- a//AmazonECS/latest/developerguide/service_utilization.md +++ b//AmazonECS/latest/developerguide/service_utilization.md @@ -7 +7 @@ -Service level CPU and memory utilizationService level EBS filesystem utilizationService RUNNING task count +Service level CPU and memory utilizationService level EBS filesystem utilizationService RUNNING task countHigh-resolution service metrics @@ -73,0 +74,6 @@ To view this metric, see [Amazon ECS Container Insights Metrics](https://docs.aw +## High-resolution service metrics + +By default, Amazon ECS publishes `CPUUtilization` and `MemoryUtilization` service metrics to CloudWatch at 60-second resolution. You can configure 20-second resolution by setting a monitoring configuration on your service. This enables faster detection of resource utilization changes and can be used to drive faster service auto scaling. + +To enable high-resolution metrics, specify a monitoring configuration with `resolutionSeconds` set to `20` when creating or updating your service. For the full setup instructions including how to configure a high-resolution scaling policy, see [Faster auto scaling with high-resolution metrics](./target-tracking-faster-auto-scaling.html). +