AWS AmazonECS documentation change
Summary
Added task IDs to error messages related to unhealthy instances and target group health checks to improve troubleshooting specificity
Security assessment
The changes add task identifiers to error messages to help pinpoint issues, but there is no evidence this addresses a security vulnerability or introduces security features. This is an operational improvement for diagnostics.
Diff
diff --git a/AmazonECS/latest/developerguide/service-event-messages-list.md b/AmazonECS/latest/developerguide/service-event-messages-list.md index fc58abacd..0cb7b3a33 100644 --- a//AmazonECS/latest/developerguide/service-event-messages-list.md +++ b//AmazonECS/latest/developerguide/service-event-messages-list.md @@ -5 +5 @@ -service (service-name) has reached a steady state.service (service-name) was unable to place a task because no container instance met all of its requirements.service (service-name) was unable to place a task because no container instance met all of its requirements. The closest matching container-instance container-instance-id has insufficient CPU units available.service (service-name) was unable to place a task because no container instance met all of its requirements. The closest matching container-instance container-instance-id encountered error "AGENT".service (service-name) (instance instance-id) is unhealthy in (elb elb-name) due to (reason Instance has failed at least the UnhealthyThreshold number of health checks consecutively.)service (service-name) is unable to consistently start tasks successfully.service (service-name) operations are being throttled. Will try again later.service (service-name) was unable to stop or start tasks during a deployment because of the service deployment configuration. Update the minimumHealthyPercent or maximumPercent value and try again.service (service-name) was unable to place a task. Reason: You've reached the limit on the number of tasks you can run concurrentlyservice (service-name) was unable to place a task. Reason: Internal error.service (service-name) was unable to place a task. Reason: The requested CPU configuration is above your limit.service (service-name) was unable to place a task. Reason: The requested MEMORY configuration is above your limit.service (service-name) was unable to place a task. Reason: You’ve reached the limit on the number of vCPUs you can run concurrentlyservice (service-name) was unable to reach steady state because task set (taskSet-ID) was unable to scale in. Reason: The number of protected tasks are more than the desired count of tasksservice (service-name) was unable to reach steady state. Reason: No Container Instances were found in your capacity provider.service (service-name) was unable to place a task. Reason: Capacity is unavailable at this time. Please try again later or in a different availability zone.service (service-name) deployment failed: tasks failed to start.service (service-name) Timed out waiting for Amazon ECS Agent to start. Please check logs at /var/log/ecs/ecs-agent.log".service (service-name) task set (taskSet-ID) is not healthy in target-group (targetGroup-ARN)) due to TARGET GROUP IS NOT FOUND. service (service-name) task set (taskSet-ID) is not healthy in target-group (targetGroup-ARN)) due to TARGET IS NOT FOUND. +service (service-name) has reached a steady state.service (service-name) was unable to place a task because no container instance met all of its requirements.service (service-name) was unable to place a task because no container instance met all of its requirements. The closest matching container-instance container-instance-id has insufficient CPU units available.service (service-name) was unable to place a task because no container instance met all of its requirements. The closest matching container-instance container-instance-id encountered error "AGENT".service (service-name) (task task-id) (instance instance-id) is unhealthy in (elb elb-name) due to (reason Instance has failed at least the UnhealthyThreshold number of health checks consecutively.)service (service-name) is unable to consistently start tasks successfully.service (service-name) operations are being throttled. Will try again later.service (service-name) was unable to stop or start tasks during a deployment because of the service deployment configuration. Update the minimumHealthyPercent or maximumPercent value and try again.service (service-name) was unable to place a task. Reason: You've reached the limit on the number of tasks you can run concurrentlyservice (service-name) was unable to place a task. Reason: Internal error.service (service-name) was unable to place a task. Reason: The requested CPU configuration is above your limit.service (service-name) was unable to place a task. Reason: The requested MEMORY configuration is above your limit.service (service-name) was unable to place a task. Reason: You’ve reached the limit on the number of vCPUs you can run concurrentlyservice (service-name) was unable to reach steady state because task set (taskSet-ID) was unable to scale in. Reason: The number of protected tasks are more than the desired count of tasksservice (service-name) was unable to reach steady state. Reason: No Container Instances were found in your capacity provider.service (service-name) was unable to place a task. Reason: Capacity is unavailable at this time. Please try again later or in a different availability zone.service (service-name) deployment failed: tasks failed to start.service (service-name) Timed out waiting for Amazon ECS Agent to start. Please check logs at /var/log/ecs/ecs-agent.log".service (service-name) task set (taskSet-ID) (task task-id) is not healthy in target-group (targetGroup-ARN)) due to TARGET GROUP IS NOT FOUND. service (service-name) task set (taskSet-ID) (task task-id) is not healthy in target-group (targetGroup-ARN)) due to TARGET IS NOT FOUND. @@ -113 +113 @@ The Amazon ECS container agent on the closest matching container instance for ta -## service (`service-name`) (instance `instance-id`) is unhealthy in (elb `elb-name`) due to (reason Instance has failed at least the UnhealthyThreshold number of health checks consecutively.) +## service (`service-name`) (task `task-id`) (instance `instance-id`) is unhealthy in (elb `elb-name`) due to (reason Instance has failed at least the UnhealthyThreshold number of health checks consecutively.) @@ -115 +115 @@ The Amazon ECS container agent on the closest matching container instance for ta -This service is registered with a load balancer and the load balancer health checks are failing. For more information, see [Troubleshooting service load balancers in Amazon ECS](./troubleshoot-service-load-balancers.html). +This service is registered with a load balancer and the load balancer health checks are failing. The message includes the task ID to help identify which specific task is failing health checks. For more information, see [Troubleshooting service load balancers in Amazon ECS](./troubleshoot-service-load-balancers.html). @@ -288 +288 @@ The Amazon ECS container agent on the closest matching container instance for ta -## service (`service-name`) task set (`taskSet-ID`) is not healthy in target-group (`targetGroup-ARN)`) due to `TARGET GROUP IS NOT FOUND`. +## service (`service-name`) task set (`taskSet-ID`) (task `task-id`) is not healthy in target-group (`targetGroup-ARN)`) due to `TARGET GROUP IS NOT FOUND`. @@ -290 +290 @@ The Amazon ECS container agent on the closest matching container instance for ta -The task set for the service is failing health checks because the target group isn't found. You should delete and recreate the service. Don't delete any Elastic Load Balancing target group unless the corresponding Amazon ECS service is already deleted. +The task set for the service is failing health checks because the target group isn't found. The message includes the task ID to help identify which specific task is failing health checks. You should delete and recreate the service. Don't delete any Elastic Load Balancing target group unless the corresponding Amazon ECS service is already deleted. @@ -292 +292 @@ The task set for the service is failing health checks because the target group i -## service (`service-name`) task set (`taskSet-ID`) is not healthy in target-group (`targetGroup-ARN)`) due to `TARGET IS NOT FOUND`. +## service (`service-name`) task set (`taskSet-ID`) (task `task-id`) is not healthy in target-group (`targetGroup-ARN)`) due to `TARGET IS NOT FOUND`. @@ -294 +294 @@ The task set for the service is failing health checks because the target group i -The task set for the service is failing health checks because the target isn't found. +The task set for the service is failing health checks because the target isn't found. The message includes the task ID to help identify which specific task is failing health checks. @@ -304 +304 @@ Viewing service event messages -Amazon ECS Availability Zone service rebalancing service event messages +Amazon ECS service unhealthy event messages