The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to specify runtimePlatform in task definition file for BitBucket pipeline

Roman Lymar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 8, 2022

I use BitBucket pipelines with pipe:

- pipe: atlassian/aws-ecs-deploy:1.6.1
  variables:
    AWS_ACCESS_KEY_ID: '<string>'
    AWS_SECRET_ACCESS_KEY: '<string>'
    AWS_DEFAULT_REGION: '<string>'
    CLUSTER_NAME: '<string>'
    SERVICE_NAME: '<string>'
    TASK_DEFINITION: task-definition.json

The file "task-definition.json" contains element:

"runtimePlatform": {
"operatingSystemFamily": "LINUX",
"cpuArchitecture": "X86_64"
}


When the pipeline performs a step that contains mentioned pipe I can see the exception:

✖ ECS task definition parameter validation error:
Parameter validation failed:
Unknown parameter in input: "runtimePlatform", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode, proxyConfiguration, inferenceAccelerators


How to configure pipe: atlassian/aws-ecs-deploy:1.6.1 to resolve the issue: sometimes AWS requires to specify runtimePlatform?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 11, 2022

@Roman Lymar hi. Thanks for your question.
Maybe you can remove runtimePlatform element from task definition because provided values in this element are default values. 
One of the possible reason of this error is that current version  1.13.13 of boto3 in the pipe does not support this element.

Regards, Igor

TAGS
AUG Leaders

Atlassian Community Events