CodePipeline with ECS Fargate using Graviton2 is failing

Question

I migrated my ECS Fargate workloads to Graviton2, however when I am using CodePipeline to release new code, it removes
```
"runtimePlatform": {
        "operatingSystemFamily": "LINUX",
        "cpuArchitecture": "ARM64"
    }, 
```
from the task definition and then the task fails due to architecture mismatch. 
I am using Amazon ECS as the deploy provider, so it only suppose to update the imageUri in the task definition. If I manually add the removed part, it works just fine.

Answer

Have you modified your CI to build multi-architecture images as highlighted in [this](https://aws.amazon.com/blogs/devops/creating-multi-architecture-docker-images-to-support-graviton2-using-aws-codebuild-and-aws-codepipeline/) blog post?

Answer

Hi Mark,

Received this from AWS Support!

> I just received an update from the CodePipeline service team. They mentioned that this is a known issue. The service team are busy working on a fix for this issue. I will be monitoring the ticket for an update and as soon as I receive an update, I will communicate the details with you. For now, I will be placing this case in the "Pending Amazon Action" state.

Hopefully it won't be long for a fix, have a good day.

Ben

Answer

Hey, 
As the fails message says, you have mismatch configuration in your cpu Arch, look at your configuration files if everything is in order. Based on this [aws doc](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-taskdefinition-runtimeplatform.html), runtime is not required. Sometimes, providing this will trigger further checks and fails.

CodePipeline with ECS Fargate using Graviton2 is failing

Relevant content