Charles Lariviere
01/04/2021, 6:16 PMprefect agent ecs start
); but for Prefect to be able to run flows on a schedule, it requires an agent to be always running (since Prefect Cloud doesn’t spin up agents). How does one actually do this without spending days experimenting?Kyle Moon-Wright
01/04/2021, 6:23 PMCharles Lariviere
01/04/2021, 6:29 PMprefect agent kubernetes start
which spins up an agent tied to the local terminal session. There does not appear to be an equivalent command for ECS in the CLI. Is there a straightforward way we could deploy an ever-running agent in ECS?Kyle Moon-Wright
01/04/2021, 7:04 PMprefect agent ecs start
on their ECS instances to pick up work from their Cloud tenant and finding success there - as long as you provide a RUNNER token to the agent, it can be left in that instance to pick up work. It is a relatively lightweight process that can be left polling, while the actual work will delegated as a FlowRun for compute as a separate process.Charles Lariviere
01/05/2021, 5:26 PMERROR - agent | Failed to infer default networkConfiguration, please explicitly configure using `--run-task-kwargs`
This agent is deployed in ECS through a task that pulls the <http://docker.io/prefecthq/prefect:latest|docker.io/prefecthq/prefect:latest>
image, and executes prefect agent ecs start -t <TOKEN> --cluster prefect
.
It’s unclear to me which network configuration the agent expects?Sagun Garg
01/21/2021, 7:48 AMCharles Lariviere
01/21/2021, 2:35 PMSagun Garg
01/22/2021, 9:50 AM