Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hello, Prefect community!
I have a question. I’m considering using ECSTasks for my execution layer setup, but wanted to verify something first.

From <https://www.prefect.io/guide/blog/prefect-2-3-0-adds-support-for-flows-defined-in-docker-images-and-github/#NewDockerdeploymentexperience|www.prefect.io/guide...#NewDockerdeploymentexperience>
&gt; If your deployment defines `-ib docker-container/prod` and doesn’t specify any remote storage block, Prefect will assume that the flow code is baked into the image.
Does this hold true for `-ib ecs-task/prod` as well?

Hi <@U04DH5Z7ZME> I don't believe that is true for the ecs-task. I think you need to specify a storage location for the ecs infrastructure block. <https://docs.prefect.io/concepts/infrastructure/#ecstask>

And what about K8sJob, does it hold true for those? :slightly_smiling_face:

Hi Kristian, Emil wrote a tutorial in Prefect recipes that explains a few image storage options that you have in ECS or k8s jobs :slightly_smiling_face: I wonder if this would help?
<https://github.com/PrefectHQ/prefect-recipes/tree/main/devops/deployments/docker>