AWS OpsWorks supports custom shutdown timeouts and Elastic Load Balancing connection draining
You can now set custom shutdown timeout values with AWS OpsWorks. Previously, OpsWorks would wait 90 seconds for shutdown recipes to run after a stop instance command was issued. Now, you can configure the timeout value to match the execution time of your recipes.
You can now set custom shutdown timeout values with AWS OpsWorks. Previously, OpsWorks would wait 90 seconds for shutdown recipes to run after a stop instance command was issued. Now, you can configure the timeout value to match the execution time of your recipes.
You can now also specify whether you want your load balancer to connection drain. With connection draining enabled, OpsWorks instances that are part of a load balancer will be deregistered from the load balancer after receiving a stop command, but will not execute the shutdown event recipes until all connections are drained from the load balancer.
Please see the documentation for these features to learn more.
For more information on AWS OpsWorks:
• Product Page
• Documentation