1 Answer
- Newest
- Most votes
- Most comments
1
I recommend using an ALB with code deploy. Therefore you will not have the issue with elastic IPs. Your EC2s can live in a private subnet and your deployment issue will go away. Also this also enables you to scale without needing multiple elastic IPs on the EC2s.
Rerouting instance traffic behind an Elastic Load Balancing load balancer is fundamental to CodeDeploy blue/green deployments.
Relevant content
- Accepted Answerasked 4 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
+1 to this main concept, but just wanted to point out that ALB IPs will change over time. So if for some reason you can't use DNS and have to use static IPs, you need a Network Load Balancer
ALB is used, but the purpose of using elastic IP addresses is to facilitate connection to servers with various databases and other functions. The elastic IP addresses are added to the security groups of other servers in advance, and then the blue-green deployment directly associates the elastic IP addresses when starting the machine.