When defining an ECSTask if the provided task definition arn has a container named prefect (as prefect expects) the system will override the image in the task definition with the base prefect 2.0 one unless an image parameter is also supplier to the ECSTask. This is counterintuitive.

At first glance, this looks like a bug -- could you explain it a bit more in a GitHub issue on the prefect-aws repo? https://github.com/PrefectHQ/prefect-aws