[ECS] [request]: Seperate LoadBalancer traffic distribution from lifecycle mgmt.

**Tell us about your request**
Separate load balancer health check to serve traffic but not killing the tasks and the let the container health checks kill the tasks if required. This should help to not kill tasks that are currently under load. On ECS side, you would need to configure the behavior of how tasks are killed. We experienced issues where the ECS containers where under heavy load and could not serve LB health checks temporary, which resulted in LB to kill tasks because it considered them unhealthy.

**Which service(s) is this request for?**
Fargate, ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Today it is not possible to separate the idea of "is a task able to receive traffic" and "is a task alive and working". First this needs to be separated and second managed by different parties. While the LB only would be responsible to serve traffic, the ECS system should decide if a tasks needs restarting.

**Are you currently working around this issue?**
no solution

**Additional context**
K8S has a similar concept.

**Attachments**
-

Start by reviewing the ECS and Fargate behavior described in the request, including the Kubernetes comparison. Define how load balancer health should control traffic without restarting tasks, and how ECS or container health checks should determine task replacement; done means these responsibilities are separated without killing overloaded but otherwise healthy tasks.

Written by the indexing model from the issue text.