4

We built up a web server, created an AMI from it, then created a launch configuration which launches instances from this AMI, and our ASG uses this launch configuration.

We regularly install Windows updates on the web server. Every time after we do it, we create a new AMI. Then we had to recreate the launch configuration to use the new AMI, then change the ASG to use the new launch configuration.

Is there a way not having to do this?

2
  • Add details to your question about the type of changes that you are making. Amazon and third parties provide lots of tools for just this type of issue. – John Hanley Nov 17 '17 at 4:08
  • Thank you for your suggestion. I have edited my post - we regularly do Windows updates on the server. – Silly Dude Nov 17 '17 at 4:57
4

Windows Updates is one of the areas that I recommend creating new AMIs. You really need to test these updates before rolling them out to a production environment. Except for security patches, I would patch, test and release a new AMI on a fixed schedule (I create a new AMI each month). You want to make sure that the updates are not breaking anything and just waiting to see if an update is recalled is a good idea. I have been bitten by this so many times ... Take a look at Amazon's SSM for Windows patch management.

4

If you create a new AMI, you must create a new launch configuration and update the Auto Scaling group.

The only way to avoid this is to use the same AMI. Instead of baking your updates into the AMI, pull the files on first launch of your EC2 instances.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.