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

Could anyone please explain why Prefect is attempting to register task definitions?  `18:51:43.512 | INFO    | prefect.infrastructure.ecs-task - ECSTask 'tasteful-ringtail': Registering task definition...` Is it possible to avoid this?

are you using the `ECSTask` class from prefect-aws? <https://github.com/PrefectHQ/prefect-aws/blob/9c82cf3592e45244387225144aabda82e8a4a86f/prefect_aws/ecs.py#L204>

AFAIK the behavior is, when you run ECSTask without specifying an existing task definition ARN

1. require task definition. register that in ECS
2. run task
3. dergister task def

Hey Alex thanks for your quick reply, I have provided the task_arn but it is still registering.

If the task settings requires changes to the task definition, we need to register a new one. This can be caused by a few things, cc <@U02H1A95XDW>

Generally this requires setting the `image=None`  since we do not know if you have defined an image in a linked task definition.

it's most likely because you enabled logging to cloud watch - disabling that will avoid reregistration

image.png

I trying it by removing task_customizations attribute

this must be False
```configure_cloudwatch_logs: bool = Field(
    default=None,
    description=(
        "If `True`, the Prefect container will be configured to send its output "
        "to the AWS CloudWatch logs service. This functionality requires an "
        "execution role with logs:CreateLogStream, logs:CreateLogGroup, and "
        "logs:PutLogEvents permissions. The default for this field is `False` "
        "unless `stream_output` is set. "
    ),
)```


Hm `task_customizations` does not apply to the task definition, just the task run.

Working on some debugging help for this at <https://github.com/PrefectHQ/prefect-aws/pull/166>