Getting a strange new error during flow submission `Submissi

Question

Getting a strange new error during flow submission `Submission failed botocore exceptions ParamValidationError Parameter validation failed Unknown parameter in input deregisteredAt must be one of family taskRoleArn executionRoleArn networkMode containerDefinitions volumes placementConstraints requiresCompatibilities cpu memory tags pidMode ipcMode proxyConfiguration inferenceAccelerators ephemeralStorage runtimePlatform` I don t get this error if I deploy the flows locally but when the flows are deployed from circleci this error is generated

Rob Freedy · Answer

Is this for Prefect 1 or 2 Do you have the ECS configuration that you can share

Nikhil Jain · Answer

Prefect 2

Nikhil Jain · Answer

``` Get the revision of the task definition arn result = ecs client list task definitions familyPrefix= prefect2 artemis ecs task status= active maxResults=1 sort= DESC task def arn = result taskDefinitionArns 0 ecs task block = ECSTask task definition arn=task def arn cluster=f env prefect cluster vpc id=vpcs env task customizations= op add path networkConfiguration value awsvpcConfiguration subnets subnets env securityGroups security groups env assignPublicIp DISABLED configure cloudwatch logs=True stream output=True ecs task block save f env artemis ecs block overwrite=True ``` ECS block

Nikhil Jain · Answer

```boto3==1 26 66 botocore==1 29 66 prefect==2 7 0 prefect aws==0 2 1```

Rob Freedy · Answer

Are the ECSTask and AWSCredentials blocks being registered in the CircleCI environment the third bullet point in <https docs prefect io concepts infrastructure h=ecstask ecstask|this doc>

Nikhil Jain · Answer

Yes for ECSTask block Not using AWSCredentials block I don t think that s required

Nikhil Jain · Answer

I have a similar circleci setup for another project using prefect2 and that has been working fine

Nikhil Jain · Answer

I just realized that it s possible that `PREFECT API URL` is missing in this project s setup I ll try setting that

Nikhil Jain · Answer

It worked after setting `PREFECT API URL` Difficult to get there from the error message above slightly smiling face Thanks a lot for your help

Rob Freedy · Answer

Glad you got it working