We run our Prefect flows on Amazon ECS using the Prefect agent. Each time we deploy a new version of the code that underlies our flows, we create a new Prefect deployment for each our flows which references: 1) An infrastructure block that represents ECS (

prefect_aws.ecs.ECSTask

) 2) A storage block that represents S3 (

prefect.filesystems.S3

) So when we create each deployment, the deploy process (part of our CI/CD pipeline) copies the entire codebase into the S3 location. When the flow is run, the execution infrastructure (ECS task) downloads the codebase out of S3 and runs the downloaded code. This setup works, but it’s inefficient in that the infrastructure (ECS task) that’s running the flow is itself a Docker image that already has the latest flow code contained in it. So it’s unnecessary to copy that code into S3 at deployment time, and to copy that code out of S3 at flow run time. Our codebase supporting flows is fairly large, so having to push this into and out of S3 significantly slows down both our CI/CD pipeline and flow launching. But as far as we can tell there’s no other workable alternative for running a flow on ECS. Are we missing something? Is there some way to deploy a flow without specifying a storage block? Or by somehow specifying a storage block that represents something like “the flow’s code can be found on the local filesystem of the infrastructure that’s running the flow”. I see that a recent release is replacing the Prefect agent architecture with work pool and workers -- if we made that shift would we be able to do away with these inefficiencies?