Amazon OpsWorks Custom Cookbooks not updating when using Load-based instances
I've deployed a stack in Amazon OpsWorks, and I extensively use custom
cookbooks to deploy my application. I have a number of instances in my
stack that are load-based (they only boot up when needed).
Anytime I make changes to my custom cookbooks, I have to manually update
the cookbooks on any running instances (by navigating to Deployments > Run
Command). The problem is that any non-booted instances are not updated,
and they don't automatically update at their next boot.
I've figured out that I can delete and then recreate all my load-based
instances, forcing them to be completely re-setup when they're next
needed, but there must be a better way to deploy updated custom cookbooks.
How can I force my offline load-based instances to update their cookbooks
at the next boot (even every boot would be fine)?
No comments:
Post a Comment