AWS AmazonECS documentation change
Summary
Updated terminology and added reference to managed instance patching documentation
Security assessment
The change adds documentation linking to managed instance patching processes, which relates to security maintenance. However, it's an operational documentation update without evidence of addressing a specific security vulnerability.
Diff
diff --git a/AmazonECS/latest/developerguide/container-instance-draining.md b/AmazonECS/latest/developerguide/container-instance-draining.md index 4aeb7576c..5fd1efe2d 100644 --- a//AmazonECS/latest/developerguide/container-instance-draining.md +++ b//AmazonECS/latest/developerguide/container-instance-draining.md @@ -38 +38 @@ Any standalone tasks in the `PENDING` or `RUNNING` state are unaffected; you mus -Amazon ECS Managed Instances termination processes ensure graceful workload transitions while optimizing costs and maintaining system health. The termination system provides three distinct decision paths for instance termination, each with different timing characteristics and customer impact profiles. +Amazon ECS Managed Instances termination ensures graceful workload transitions while optimizing costs and maintaining system health. The termination system provides three distinct decision paths for instance termination, each with different timing characteristics and customer impact profiles. @@ -43 +43 @@ Customer-initiated termination -Provides direct control over instance removal when you need to remove container instances from service immediately. You run `deregister-container-instance` with the `force` request parameter set to true, This means that immediate termination is required despite any running workloads. +Provides direct control over instance removal when you need to remove container instances from service immediately. You run `deregister-container-instance` with the `force` request parameter set to true. This means that immediate termination is required despite any running workloads. @@ -48 +48 @@ System-initiated idle termination -Implements cost optimization through intelligent idle detection that identifies instances no longer serving workloads. The Elastic Workload Service (EWS) implements sophisticated idle detection algorithms that monitor instance utilization and initiate termination for instances that remain idle for configurable periods. +Amazon ECS Managed Instances continuously monitors and proactively optimizes costs by terminating idle Amazon ECS container instances not running any tasks. ECS uses a heuristic delay to give container instances a chance to acquire newly launched tasks before being terminated. This can be customized with the `scaleInAfter` Amazon ECS Managed Instances capacity provider configuration parameter. @@ -53 +53 @@ Infrastructure refresh termination -Implements proactive infrastructure management through Node Manager's natural decay policy, where instances are periodically refreshed to ensure they run on the latest platform versions and maintain security posture. Node Manager implements time-to-live (TTL) policies that initiate graceful termination for instances that have reached their maximum operational lifetime. +Amazon ECS Managed Instances automatically manages and updates software on managed container instances to ensure security and compliance while maintaining workload availability. For more information, see [patching in Amazon ECS Managed Instances](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/managed-instances-patching.html).