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

from storage - if you don't explicitly attach it, Prefect uses local storage and attaches the hostname as a label so that related flow runs will only be picked up by agents that can access this local file

I would recommend attaching S3 storage when using ECSRun - if you need some examples, check out those that have S3 and ECS names in them <https://github.com/anna-geller/packaging-prefect-flows/tree/master/flows|here>

I remember. This only reinforces my recommendation to switch to S3 storage though :slightly_smiling_face:

Yes prefect will push the Flow to S3 for you and that shouldn’t have the default label.

If you use local storage with ECSRun to point to the file inside the container, you can do:

```storage = Local(.., stored_as_script=True, add_default_labels=False)```
or you can do:
```flow.storage.add_default_labels=False```


Not sure whether relying on env variables for that is a good approach. You mentioned you need some pointers - <https://discourse.prefect.io/t/how-to-distinguish-between-various-environments-development-staging-production-in-prefect-flows/179|this Discourse topic> is dedicated to this problem in its entirety.

specifically, <https://github.com/anna-geller/prefect-dbt-k8s-snowflake/blob/master/flow_utilities/prefect_configs.py|this code snippet> may help build such logic via a simple function