Hi! i have a prefect (v2) server (instance not pre...
# ask-community
m
Hi! i have a prefect (v2) server (instance not prefect cloud) and have been using it with process workers. it works great! i am trying to set up an ecs work pool. i have a worker image in ecs and i can run a task manually. if i run the task manually the worker will register itself with the prefect server and create a process worker queue (if one did not already exist). now if i kill the worker / task and add an ecs work pool in prefect i cant get it out of a 'not ready' state. i thought i had set it up correctly but i cant see any logs or any queries that will tell me why the work pool is 'not ready'. also looking at this https://prefecthq.github.io/prefect-aws/ecs_guide/ has me confused! it seems to say that we need to create a worker in the ecs cluster and run it. perhaps i am fundamentally misunderstanding but why would we need to have a worker running all the time in the cluster? i thought the prefect server would submit the task that would run the container?
b
Hi Michael! It looks like you're using an ECS hybrid work pool. Hybrid work pools require a Prefect worker to be present in your execution environment.
If you kill the worker process that is polling the work pool, that will prompt the work pool to go in a
NotReady
state.
> i thought the prefect server would submit the task that would run the container? In the case of the hybrid ECS work pool, the worker is responsible for spinning up new ECS tasks to run your flows. However , if you are not a fan of hosting a worker process in your cluster, there is an alternative work pool type that you can use. The push work pool (and yes there is an ECS push work pool)!