ECS Deployment Controller - code_deploy

Question

ECS 서비스를 blue/green 배포로 생성하고 나서 codepipeline을 사용하려고 확인하였더니 기존의 codedeploy는 ecs deployment controller가 code_deploy 로 구성된 것을 확인하였습니다. 그러나 ECS 내장 blue/green 배포로 바뀐 뒤로는 ecs deployment controller가 ecs로 변경된 것을 확인했습니다. AWS CLI나 Terraform AWS 코드에서는 여전히 ecs deployment controller로 code_deploy를 이용할 수 있지만 AWS ECS 콘솔에서는 ecs 만을 배포 컨트롤러로 사용할 수 있었습니다. 앞으로는 cli나 terraform을 통해 구축해야하나요? 콘솔에서는 영원히 지원하지 않을 예정인가요? 아니면 추후 codedeploy 를 이용한 blue/green 배포와 deployment controller 방식은 서비스 종료 예정인가요?

re:Post Agent · Answer

Amazon ECS offers two different approaches for blue/green deployments: one using AWS CodeDeploy (deployment controller type: CODE_DEPLOY) and another using the native ECS blue/green deployment feature (deployment controller type: ECS with BLUE_GREEN strategy).

Based on your observation, it appears that the AWS ECS console now primarily promotes the native ECS blue/green deployment approach rather than the CodeDeploy integration. This reflects AWS's direction toward simplifying the deployment experience by incorporating blue/green capabilities directly into ECS.

However, the CodeDeploy integration for blue/green deployments (CODE_DEPLOY controller type) is still fully supported and available through AWS CLI, CloudFormation, and infrastructure as code tools like Terraform. There has been no announcement about deprecating or ending support for the CodeDeploy-based blue/green deployment approach.

Both approaches have their own advantages:

- The native ECS blue/green deployment (ECS controller with BLUE_GREEN strategy) provides a simpler, more integrated experience within ECS.
- The CodeDeploy-based approach (CODE_DEPLOY controller) offers more advanced deployment options and integrates well with existing CodeDeploy workflows.

You can continue using either approach based on your requirements. If you prefer the CodeDeploy integration, you can continue implementing it through CLI, CloudFormation, or Terraform. If you need console-based management, you may want to consider migrating to the native ECS blue/green deployment approach.

AWS often evolves its services to provide simpler, more integrated experiences, but typically maintains backward compatibility and support for existing approaches for extended periods.  
**Sources**  
[DeploymentController - Amazon Elastic Container Service](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeploymentController.html)  
[AwsEcsServiceDeploymentControllerDetails - AWS Security Hub](https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_AwsEcsServiceDeploymentControllerDetails.html)  
[Questions about CodeDeploy and ECS | AWS re:Post](https://repost.aws/questions/QUP5BwHW2SQ42_AhiNkAO3xA/questions-about-codedeploy-and-ecs)  
[Migrating an AWS CloudFormation CodeDeploy blue/green deployment template to an Amazon ECS blue/green AWS CloudFormation template - Amazon Elastic Container Service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/migrate-codedeploy-to-ecs-bluegreen-cloudformation-template.html)

ECS Deployment Controller - code_deploy

답변 추가

관련 콘텐츠