Question

A team runs a containerized order-processing service on Amazon ECS (Fargate) behind an Application Load Balancer. They use AWS CodeDeploy with a blue/green deployment configuration triggered from CodePipeline. During a recent release, the pipeline's Deploy stage failed immediately with an error indicating the deployment could not be created because the required specification was invalid. The team confirms the new container image was pushed to ECR and the ECS service is healthy. Which action correctly resolves the failure so CodeDeploy can perform the blue/green ECS deployment?

Accepted Answer

Provide an AppSpec file that specifies the ECS TaskDefinition ARN, the container name, and the container port for the replacement task set.

Answer

Add BeforeInstall and AfterInstall lifecycle hooks referencing EC2 shell scripts in the AppSpec file so CodeDeploy can copy files to the tasks.

Answer

Set the ECS service deployment controller to ECS (rolling update) so CodeDeploy can manage the task set transitions automatically.

Answer

Configure the CodeDeploy deployment group to use the AllAtOnce EC2/on-premises deployment configuration to bypass the invalid specification.