- Asked By
- Asked At
- 2018-03-10 15:42:07
Found 15 possible answers.
right @nocode, so I should be getting a port assigned, and then setup my target group's port to 80 (to let the ALB route to it), and configure the target to be whatever port was assigned to my container?
@gavin.hardy i got it all sorted in the end
my nginx container gets assigned a random port and added to the target group automatically
Is there a way i can remove the port 80 target on my load balancer target group?
Two problems: one of my ECS ASG instances became unresponsive. I terminated the instance and let the ASG create a new instance. Unfortunately, the task wasn't rerun once the instance was up again, is there a way to automate that? Also the new ASG instance didn't register with the load balancer, how do I automate that as well? :anguished:
@geekman2 ASG will not replace if just the launch config updated … you must be changing something else pretty radical.
And just to confirm: the _name_ of the ASG actually changed?
@geekman2 Are you able to share the output from a CFN update where the ASG was replaced?
I do this all the time, it works great from CFN.
I have 2 listeners : HTTP and HTTPS, both pointing at a single target group on the port 80
I probably should add a second target group with port 443 ?
launch config ?
Hi all. I've started using Packer to create immutable images for deployments. I also have a script to update the new AMI into a launch-config and ASG. I now need a way to trigger a recycle in the ASG so it brings down old machines and brings up new ones with the new AMI. What is the best approach to do this?
We are doing ASGs in Terraform, When we create a new launch config, we want the old instances using the old launch config to terminate, and spin up new instances with the new launch config, at the moment. I have to manually terminate the instances, then they get span up with the new one, anyone have any ideas how to automate this?
Is anyone using code_deploy in AWS created with terraform?
Question: What is wrong on this approach or what is the best approach to roll out an launch configuration change with terraform assuming I am using codedeploy too?
3 - Now I had to change the launch configuration (change the AMI), but when I apply it, terraform will create another ASG (as the on that was previously created is not there), but he will not be able to remove the old launch configuration as it is now part of the ASG automatically created by code deploy.
2 - After some deploys the CodeDeploy creates a copy of the ASG that terraform created
1 - I create an infrastructure with CodeDeploy (BlueGreen), ASG and Launch configuration in terraform
I am having the following problem:
I am looking at this
I am guessing I don't have to add any rule for egress as that is allow all by default
what should a rule for allowing port 43342 look like?
@tasdikrahman uploaded a file: Screen Shot 2017-08-17 at 9.45.44 PM.png https://devopschat.slack.com/files/tasdikrahman/F6Q5VFSE9/screen_shot_2017-08-17_at_9.45.44_pm.png