Basically you just need to create a new launch configuration and then update it in the autoscaling group. Any new instances created in the autoscaling group will then use the new launch configuration.
Regards, -scott On Friday, August 15, 2014 7:32:36 AM UTC-4, Arangel Angov wrote: > > Hi, > > I've been playing with EC2 autoscaling for a while and my goal is to > start an instance update it and then save it to an AMI or use the > instance AMI id in a launch configuration tied to an auto scaling group > so that I have my instance up to date all the time and ready for scaling. > > So I wanted to update the launch configuration using ec2_lc so that I > either use the newly generated AMI image or the image_id of the running > instance. The first doesn't work cause if I want to update the lc I > actually need to delete both autoscaling group and lc (and this is not > acceptable cause I have production instances running in the auto scaling > group, so deleting it will terminate those instances). The second > approach doesn't really work also cause I guess the ec2_lc module > doesn't support updating the lc or using the instance_id of my updated > instance in the lc, which is something that ec2 supports > ( > http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/create-lc-with-instanceID.html). > > > > I could use the ec2 tools inside ansible but just wanted to see if > anyone had this issue before and how you solved it - without using Tower > of course. :) > > Thanks. > > -Arangel > > -- > *Disclaimer* > > This email is really important (well, most of them are.). Also, hopefully > the message has been sent to the person it’s intended for. If we stuffed > up > by entering the wrong email address, we’re very sorry for cluttering up > your inbox. But if we have done that, then please do us a favour and let > us > know…and if you could keep the juicy bits to yourself, that would be great > too. > > Also…stuff that’s said in this message are the views of the person writing > the email and do not actually represent the views of Gramble World > (although they might, but we’re just hedging our bets here). Don’t think > for one minute that anything in this message should be construed as > creating a contract. > > Gramble World owns the email infrastructure, including the contents. > > Finally…do the right thing by the environment and “think before you ink”! > > ********************************************************************** > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1b5356d1-3ed7-4418-b2d7-051644b2942d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
