Stephen Herron
09/21/2022, 10:53 AMnetworkConfiguration
and thus awsvpcConfiguration
, to allow the flow to run under specific subnets/security groups but this doesn’t seem possible in prefect2 using this task at the moment?Anna Geller
09/21/2022, 12:39 PMnetworkConfiguration
since in 90% it's always awsvpc and that's what we already use as default (and if you use EC2 launch type, the default is bridge);
and awsvpcConfiguration
was cumbersome because usually you only care about to which VPC your ECS task gets deployed (custom or default VPC) and you don't want to worry about which subnet to pick -- in the current setup, we automatically query all available subnets in the VPC ID you provided and ECS decides to which one it's best to run a specific ECS task with your flow run
so all use cases from 1.0 are possible, but way easier - feel free to open a GitHub issue on the prefect-aws
repo if you struggle to configure something - given that this block is still experimental, we are open to feedback to adjust this block if neededStephen Herron
09/21/2022, 12:59 PMbotocore.errorfactory.InvalidParameterException: An error occurred (InvalidParameterException) when calling the RunTask operation: At least one security group must be supplied when specifying subnets that are owned by a different account.
created this for reference - https://github.com/PrefectHQ/prefect-aws/issues/112Anna Geller
09/21/2022, 3:12 PM