When I set up Prefect in ECS, I went ahead and created the prefect worker task definition, but I noticed that there is also a prefect task definition for the Prefect flow run execution. Was that created by Prefect?

Apologies if I'm misunderstanding but the

ECSWorker

will create a task definition for flow run execution if a Task Definition ARN is not provided via the work pool ordeployment

Then does the ecsworker also create new revisions of the task definition when configs are updated?

yes it does 👍

Ah I see. I manually added stuff to my task definition (logging and whatnot), but it seems that I should figure out how to push that back in the prefect level and let the Ecsworker handle it instead of trying to manage two different configs levels

Really up to you where you'd prefer to handle. FWIW I also find it easier to manage it inside prefect instead of bouncing between AWS and Prefect if I can avoid it

Is there an example of how I can add cloudwatch logging configs at the Prefect level instead of adding it at the task definition level?

I don't have an example unfortunately but you can set it on the work pool by toggling this on and then passing any additional options in the field below: