- 新しい順
- 投票が多い順
- コメントが多い順
Hello.
Why not just deploy the code directly to EC2 in the AutoScaling group instead of updating the launch template?
https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-groups-create-blue-green.html
Blue/Green deployment of AutoScaling groups is not supported by CloudFormation, so you will need to create Lambda etc. as shown in the blog below.
https://medium.com/@greeshu.renu/blue-green-deployment-using-aws-cloudformation-bd936dc0fe01
Hello,
I'm no expert, but I think all you have to do is rename your CodeDeploy.
CloudFormation will create a new CodeDeploy for you by keeping resources that are currently in use. Of course, make sure you don't rename your other resources.
For exemple, if tou have this code:
MyDeploy:
Type: AWS::CodeDeploy::Application
Properties:
ComputePlatform: Lambda
You can do that:
MyDeploy2:
Type: AWS::CodeDeploy::Application
Properties:
ComputePlatform: Lambda
Please don't rename other ressources because CloudFormation will destroy and create new ones.
@Riku_Kobayashi Can you tell me if I'm wrong or not? (It's my first comment on re:Post)
関連するコンテンツ
- AWS公式更新しました 3年前
- AWS公式更新しました 1年前
Thank you for the reply, Reason not to deploy directly to EC2 auto scaling group is if one instance goes down the ASG will bring up new instance with older launch template.