Error with AWS ECS Deployment Pipe

[Manoj Kinage]

'volumes': []}
DEBUG: Event before-parameter-build.ecs.RegisterTaskDefinition: calling handler <function generate_idempotent_uuid at 0x7f72873eb343>
✖ ECS task definition parameter validation error:
Parameter validation failed:


{'key': 'Environment', 'value': 'dev'},
{'key': 'DCIO', 'value': 'Customer'},
{'key': 'Name', 'value': 'ECS_TASK_NAME'}],
'taskDefinitionArn': 'arn:aws:ecs:us-west-2:1111111111111:task-definition/ECS_TASK_NAME:4',
'volumes': []}
DEBUG: Calling endpoint provider with parameters: {'Region': 'us-west-2', 'UseDualStack': False, 'UseFIPS': False}
DEBUG: Endpoint provider result: https://ecs.us-west-2.amazonaws.com
DEBUG: Event before-parameter-build.ecs.RegisterTaskDefinition: calling handler <function generate_idempotent_uuid at 0x7f62b73bf010>
✖ ECS task definition parameter validation error:
Parameter validation failed:
Unknown parameter in input: "taskDefinitionArn", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators, ephemeralStorage, runtimePlatform
Unknown parameter in input: "revision", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators, ephemeralStorage, runtimePlatform
Unknown parameter in input: "status", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators, ephemeralStorage, runtimePlatform
Unknown parameter in input: "requiresAttributes", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators, ephemeralStorage, runtimePlatform
Unknown parameter in input: "compatibilities", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators, ephemeralStorage, runtimePlatform
Unknown parameter in input: "registeredAt", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators, ephemeralStorage, runtimePlatform
Unknown parameter in input: "registeredBy", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators, ephemeralStorage, runtimePlatform

[Igor Stoyanov]

@Manoj Kinage hi. This pipe based on boto3 1.26 version. According to docs there is no request parameter `taskDefinitionArn`. That's why your task-definition failed validation.

Regards, Igor

[Manoj Kinage]

@Igor Stoyanov there is TaskARN and it is also printed in error. As I mentioned with same json file I am able to deploy using AWS CLI.

[Igor Stoyanov]

@Manoj Kinage  AWS CLI and boto3 are not the same tools. Boto3 does not support `taskDefinitionArn` request parameter in register-task-definition

Regards, Igor

[Oday Rafeh]

@Manoj Kinage 

The error message indicates that there is a parameter validation failure related to the ECS task definition. Specifically, the error messages show that there are unknown parameters being used.

One thing you can try is to check the parameters you are using in your code and compare them to the parameters listed in the AWS ECS documentation to make sure you are using the correct syntax.

You may also want to check the version of the AWS ECS Deployment Pipe you are using to see if there are any known issues or bugs that could be causing this error.

[Manoj Kinage]

I don't think there is any invalid parameter in task definition because I am able to deploy using same task definition using aws-cli and also from bitbucket using aws cli image.

[Oday Rafeh]

May be an issue with the AWS ECS Deployment Pipe itself. You could try reaching out to the support team for the pipe to see if they can provide any insights or solutions for this error