nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pipeline failing: Unknown parameter in input: "registeredAt"

Anuj_wuv64w

Urgent help required. Production Pipeline failing

Using atlassian/aws-ecs-deploy:1.3.0

The pipelines to ECS are failing with the following error

<span>Parameter validation failed:<br><br></span><span>Unknown parameter in input: "registeredAt", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators<br></span><span>Unknown parameter in input: "registeredBy", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators</span><span>&#10006; ECS task definition parameter validation error: </span>

Earlier it was working fine.

Following is the task definition

<span>],</span><span> <br>  'executionRoleArn': 'arn:aws:iam::<user>:role/ProdECSRole',</span><span> <br>  'family': 'backend-task-def',<br>&nbsp;</span><span> 'networkMode': 'bridge',<br>&nbsp;</span><span> 'placementConstraints': [],<br>&nbsp;</span><span> 'registeredAt': 1610533632.651,<br>&nbsp;</span><span> 'registeredBy': 'arn:aws:iam::<user>:user/bitbucket-prod',</span><span> <br>  'requiresCompatibilities': ['EC2'],<br>&nbsp;</span><span> 'taskRoleArn': 'arn:aws:iam::<user>:role/ProdECSRole',</span><span><br>  'volumes': []<br>}</span><span>{<br>  'containerDefinitions': [</span>

Accepted answers

Oleksandr Kyrdan

Hi @Anuj ,

Thank you for your question.

It looks like it's AWS issue relates to the latest AWS API update.

We're investigating the issue and will notify you of any updates.

It would be nice if you provide us with more details: how long have you used aws-esd-deploy pipe with "registeredAt" and "registeredBy" params?

All comments

Halyna Berezovska

@Anuj

I have not found registeredAt, registeredBy parameters in Request syntax of https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ecs.html#ECS.Client.register_task_definition.

These parameters are only in Response syntax, I believe they cannot exist in request syntax, because they are like update_at, created_at paramters, that can persist only AFTER the request processing.

Check out this doc and ensure that you have right parameters , but pay attention only to Request Syntax. At the first glance to fix this, you have to remove these two params.

Regards, Galyna

Oleksandr Kyrdan

Hi @Anuj ,

Thank you for your question.

It looks like it's AWS issue relates to the latest AWS API update.

We're investigating the issue and will notify you of any updates.

It would be nice if you provide us with more details: how long have you used aws-esd-deploy pipe with "registeredAt" and "registeredBy" params?

Anuj_wuv64w

The last successful deployment was on January 13, 2021

Halyna Berezovska

@Anuj is it necessary for you to keep these arguments in task definition? Looks like they are not provided anymore in documentation and I don't know if they've been ever provided. AWS respond with these parameters, but does not take into task definition (or they have updated documentation).

Have you tried to remove these fields, if you don't really need it?

It is because these are actually not allowed fields in task definition, these are post-processing fields, that aws cli creates after registering your task definition - it is like general createdAt fields.

Since we did not upgrade any version of aws libraries, neither botocore, no boto3 and not awscli , this looks like really aws documentation or aws server problem referring to the issue that @Oleksandr Kyrdan has mentioned.

Regards, Galyna

Anuj_wuv64w

I don't think I'm adding these values.

I use the following script to update the existing task definition, so the definition is retrieved from the AWS and replaced the required values only

TASK_DEFINITION=$(aws ecs describe-task-definition --task-definition "$AWS_ECS_TASK_FAMILY")
NEW_TASK_DEFINITION=$(echo "$TASK_DEFINITION" | jq --arg IMAGE "$ECR_IMAGE_TAG" '.taskDefinition | .containerDefinitions[0].image = $IMAGE | del(.taskDefinitionArn) | del(.revision) | del(.status) | del(.requiresAttributes) | del(.compatibilities)')

And using the NEW_TASK_DEFINITION in the pipeline

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket-pipelines

aws