Hi everyone, Our team is moving from prefect deployment with EC2 to using ECS, and wondering whether to go with ECS Push workpool or ECS Hybrid model with a worker. From what I gather, the only difference is the hybrid model needs to set up a worker up front and has more maintenance overhead, but it allows for more custom configurations. I'm not clear on what these custom configs could mean, can anyone please shed more light? In which instances would we want to use hybrid model with worker instead of the Push? And as follow up question, if I already have an ECS cluster set up along with the worker (ecs service), can this same cluster be used to create both a Hybrid workpool and a Push workpool?

hi @Moe > the hybrid model needs to set up a worker up front and has more maintenance overhead, but it allows for more custom configurations I think this is accurate at a high level I'd say that if you're not sure what custom config you'd need from a hybrid worker setup, the push pool will probably cover your use cases, because you can still • write a custom

pull

step to pull in whatever you need at runtime, e.g.

run_shell_script

to load secrets from a vault (bc you're already in your own ECS cluster) • configure your flow run environment via work pool / deployment / flow run overrides in all the same ways