Therefore, he does not say this explicitly, and Nathaniel may certainly be right, but this blog from April 9 this year, apparently, implies at least that you can do what you ask
Long-Term Applications Previously, Amazon ECS included two methods: schedule docker containers on the cluster. You can run tasks once for processes such as batch jobs that perform work and then stop. You can also access the Amazon ECS APIs to retrieve the state of cluster information, and then use it to connect a third-party or personalized scheduler.
With today's launch, you can also use the new Amazon ECS Scheduler service to manage long-term applications and services. A service scheduler helps maintain application availability and allows you to scale your containers up or down to suit your needs. application capacity requirements. Here is what he does for you:
Load Balancing - The Service Planner allows you to distribute traffic through your containers using elastic load balancing. Amazon ECS automatically registers and unregisters your containers from the appropriate load balancer. Healthcare management - the service scheduler also automatically restores containers that become (do not check ELB functionality) or stop working to make sure that you have the required number of healthy containers available to run your application. Scaling and scaling - you can scale applications up and down by changing the number of required service containers to run. Update management. You can update your application by changing its definition or using a new image. the scheduler automatically launches new containers using the new one using the previous version. This will wait until the ELB connections are merged if an ELB is used. You can also use these new features to implement the basic service discovery model. You can display services running in a cluster and then use ELB as a service endpoint.
Ir1sh source share