@Marvin where can I read about what's actually happening during mapped tasks running on ECS fargate?

To understand what happens during mapped tasks running on ECS Fargate, you should consider two main components: 1. Mapped Tasks: In Prefect, mapped tasks create dynamic parallel pipelines. When you map a task over a list, each item of the list gets processed in an individual task. This means that each task runs independently and can be retried or alerted individually. Task mapping makes it simple to specify parallel execution in your flow and retains all the state-management benefits of Prefect, even in a dynamically created parallel flow. Read more about mapped tasks. 2. ECS Fargate Integration: When using ECS Fargate to run your Prefect flows, you need to have Prefect installed and optionally sign up for Prefect Cloud if you wish to leverage cloud capabilities. Integration involves creating Prefect Blocks for configuration and setting up authentication with Prefect Cloud. Although the document doesn't explicitly detail ECS Fargate execution, it's likely similar to running other Prefect workloads but on the containerized Fargate service. See Prefect and AWS integration. For detailed information on ECS Fargate's handling of Prefect mapped tasks, you should consult the Prefect documentation on ECS Fargate, since the general documentation excerpts don't describe the specifics of the ECS Fargate environment.