AWS AmazonECS documentation change
Summary
Clarified instance replacement process and security practices for Managed Instances
Security assessment
Changes emphasize security compliance through automatic instance rotation (14-day lifecycle) and patching practices. While security-related, this documents existing security features rather than addressing new vulnerabilities.
Diff
diff --git a/AmazonECS/latest/developerguide/ManagedInstances.md b/AmazonECS/latest/developerguide/ManagedInstances.md index 6f36fdd7d..cd2fa1683 100644 --- a//AmazonECS/latest/developerguide/ManagedInstances.md +++ b//AmazonECS/latest/developerguide/ManagedInstances.md @@ -107 +107 @@ The following are key features of Amazon ECS Managed Instances: - * Ensure security compliance and regular patching with a maximum instance lifetime of 14 days, after which tasks are automatically migrated to new instances. + * Ensure security compliance and regular instance patching. ECS Managed Instances initiates instance draining after 14 days and automatically replaces service-based tasks to new instances. @@ -139 +139 @@ Amazon ECS Managed Instances implements multiple layers of security to protect y - * **Limited instance lifetime** \- The maximum lifetime of a running instance is 14 days, ensuring your applications run on appropriately configured instances with up-to-date security patches. + * **Limited instance lifetime** \- ECS automatically initiates instance draining after 14 days, ensuring your applications run on appropriately configured instances with up-to-date security patches. @@ -254 +254 @@ Consider the following when planning your migration: - * Applications should tolerate the 14-day maximum instance lifetime and planned maintenance windows. + * Applications should tolerate the 14-day instance lifetime and planned maintenance windows.