@Marvin Flow run could not be submitted to infrastructure: Failed to find the default VPC. Network configuration cannot be inferred. Pass an explicit

vpc_id

or configure a default VPC.

The error you're encountering, "Failed to find the default VPC. Network configuration cannot be inferred," typically arises when Prefect is unable to automatically determine the network configuration for a flow run. This often occurs in cloud environments, such as AWS, where a Virtual Private Cloud (VPC) is required for network operations. Here are some steps to resolve the issue: 1. Set a Default VPC: Ensure that your AWS account has a default VPC set up. Prefect requires network configurations to run flows, and a default VPC simplifies this requirement. 2. Specify a VPC ID: If a default VPC is not available or you wish to use a specific VPC, you can explicitly pass the

vpc_id

when configuring your infrastructure. This can be done in your Prefect deployment configuration. 3. AWS CLI Configuration: Make sure the AWS CLI is installed and configured properly on your machine. This includes setting a default region and ensuring you have the necessary permissions. You can follow the instructions here for setting up AWS CLI and permissions. 4. Check Permissions: Ensure that your AWS IAM user has the necessary permissions to create and manage network resources. This includes permissions like

iam:CreatePolicy

,

iam:AttachUserPolicy

, and others as mentioned in the Prefect documentation. For more information, you can refer to the Prefect documentation on serverless infrastructure. If these steps do not resolve your issue, consider checking for any open issues or discussions on the Prefect GitHub repository that might relate to your specific situation.