Hi @Marvin ! I recently had this issue this worning, when my worker try to create the flow run in a cluster. It tries to run it in the cluster "default", which does not exist :

RuntimeError: Failed to run ECS task, cluster 'default' not found. Confirm that the cluster is configured in your region.

I didn't change anything in my configuration, you know what can imapct ?

It seems like your issue with the ECS task and the missing 'default' cluster might be related to the configuration of your ECS cluster or Prefect's ECS integration. Here are some insights: 1. Cluster Configuration: The error indicates that the 'default' cluster does not exist in your specified AWS region. It's crucial to ensure that the ECS cluster specified in your configuration is available and correctly set up. You might want to verify the cluster's existence and its region settings. 2. Prefect ECS Worker Setup: Prefect's ECS integration allows you to execute flow runs using ECS tasks. If no specific cluster is mentioned in your configuration, Prefect might default to using a cluster named 'default'. Ensure that your ECS cluster is correctly configured and accessible. You can refer to Prefect's ECS guide for more details on setting up ECS for Prefect. 3. AWS Configuration: Make sure your AWS CLI is configured correctly with the proper permissions to interact with ECS. This includes having the necessary IAM roles and policies to create and manage ECS clusters and tasks. If these steps don't resolve your issue, you might want to check recent changes in your AWS environment or Prefect configuration that could have impacted the cluster setup. If you need more detailed guidance, reviewing the Prefect ECS guide might be helpful.

But I don't know where to tell on which cluster to run the task

To specify which ECS cluster your Prefect tasks should run on, you need to configure the ECS work pool or task definition with the appropriate cluster name. Here's a general outline of what you need to do: 1. ECS Work Pool Configuration: When setting up your ECS work pool in Prefect, you can specify the ECS cluster you want to use. This is typically done by providing the cluster name in your work pool configuration. 2. Task Definition ARN: If you have a specific task definition ARN, you can include this in your work pool configuration. This ensures that Prefect uses the correct task definition when creating ECS tasks. 3. Prefect Configuration: In your Prefect configuration, make sure that the ECS cluster name is explicitly set. If you're using infrastructure as code, you might want to refer to Prefect's ECS guide for detailed setup instructions. 4. AWS CLI and IAM: Ensure that your AWS CLI is configured correctly and that you have the necessary IAM roles and policies to access and manage the specified ECS cluster. By following these steps, you should be able to direct Prefect to use the correct ECS cluster for your flow runs. If you're using Prefect's UI, you might find options to configure these settings directly within the work pool management interface.