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

Based on <https://docs.prefect.io/orchestration/agents/ecs.html#running-ecs-agent-in-production|this> page, it looks like you can use environment variables to set values for agent options. Is there any documentation on which environment variables map to which agent options? The only page I can find is <https://docs.prefect.io/api/latest/cli/agent.html#ecs-start|here> which doesn’t mention the environment variable option. So far we’ve been creating our own image with a custom entrypoint for the agent to set all the option but it would be super neat if we could avoid that.

Hi <@U01Q4NB74UA> We go through agent configuration options and the different options for setting them here: <https://docs.prefect.io/orchestration/agents/overview.html#usage>

Thanks Jenny! So looking in the <https://docs.prefect.io/orchestration/agents/overview.html#health-checks|bottom> I see that the `--agent-address` option corresponds to `PREFECT__CLOUD__AGENT__AGENT_ADDRESS`. Is that true for all config options when starting the agent? Can I use `PREFECT__CLOUD__AGENT__RUN_TASK_KWARGS`  instead of `--run-task-kwargs`  for example, or is it only a chosen few of the options?

That is a really good question.  I suspect it's only the options that are available in the config.toml but I'm double checking that with the team.  You can see more about config.toml and config options here: <https://docs.prefect.io/orchestration/faq/config.html>

Yeah that makes sense, thanks for checking though!

FWIW, for anyone looking in this thread while history is kept.
I actually realised that we can invoke the agent with a custom command in our task definition, and also realised why we didn’t think that was possible in the beginning which sent us on the custom image with custom entrypoint. I.e., just define your flags you can’t use env vars for using the command in the agent’s task definition.
Great simplification of our setup, good day in prefect land.

It has taken me quite a long time to stumble over this thread. It would be useful to add how to do this in <https://docs.prefect.io/orchestration/agents/ecs.html#running-ecs-agent-in-production>.