AWS OpsWorks supports five lifecycle events, setup,
configuration, deploy, undeploy, and
shutdown. For each layer, AWS OpsWorks runs a set of standard
recipes for each event. In addition, you can provide custom recipes
for any or all layers and events. AWS OpsWorks runs custom event
recipes after the standard recipes. LayerCustomRecipes
specifies the custom recipes for a particular layer to be run in
response to each of the five events.

To specify a recipe, use the
cookbook's directory name in the repository followed by two colons and
the recipe name, which is the recipe's file name without the .rb
extension. For example: phpapp2::dbsetup specifies the dbsetup.rb
recipe in the repository's phpapp2 folder.

Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>

AWS OpsWorks supports five lifecycle events, setup,
configuration, deploy, undeploy, and
shutdown. For each layer, AWS OpsWorks runs a set of standard
recipes for each event. In addition, you can provide custom recipes
for any or all layers and events. AWS OpsWorks runs custom event
recipes after the standard recipes. LayerCustomRecipes
specifies the custom recipes for a particular layer to be run in
response to each of the five events.

To specify a recipe, use the
cookbook's directory name in the repository followed by two colons and
the recipe name, which is the recipe's file name without the .rb
extension. For example: phpapp2::dbsetup specifies the dbsetup.rb
recipe in the repository's phpapp2 folder.

Returns:

AWS OpsWorks supports five lifecycle events, setup,
configuration, deploy, undeploy, and
shutdown. For each layer, AWS OpsWorks runs a set of standard
recipes for each event. In addition, you can provide custom recipes
for any or all layers and events. AWS OpsWorks runs custom event
recipes after the standard recipes. LayerCustomRecipes
specifies the custom recipes for a particular layer to be run in
response to each of the five events.

To specify a recipe, use the
cookbook's directory name in the repository followed by two colons and
the recipe name, which is the recipe's file name without the .rb
extension. For example: phpapp2::dbsetup specifies the dbsetup.rb
recipe in the repository's phpapp2 folder.

AWS OpsWorks supports five lifecycle events, setup,
configuration, deploy, undeploy, and
shutdown. For each layer, AWS OpsWorks runs a set of standard
recipes for each event. In addition, you can provide custom recipes
for any or all layers and events. AWS OpsWorks runs custom event
recipes after the standard recipes. LayerCustomRecipes
specifies the custom recipes for a particular layer to be run in
response to each of the five events.

To specify a recipe, use the
cookbook's directory name in the repository followed by two colons and
the recipe name, which is the recipe's file name without the .rb
extension. For example: phpapp2::dbsetup specifies the dbsetup.rb
recipe in the repository's phpapp2 folder.

Parameters:

defaultRecipes AWS OpsWorks supports five lifecycle events, setup,
configuration, deploy, undeploy, and
shutdown. For each layer, AWS OpsWorks runs a set of standard
recipes for each event. In addition, you can provide custom recipes
for any or all layers and events. AWS OpsWorks runs custom event
recipes after the standard recipes. LayerCustomRecipes
specifies the custom recipes for a particular layer to be run in
response to each of the five events.

To specify a recipe, use the
cookbook's directory name in the repository followed by two colons and
the recipe name, which is the recipe's file name without the .rb
extension. For example: phpapp2::dbsetup specifies the dbsetup.rb
recipe in the repository's phpapp2 folder.

AWS OpsWorks supports five lifecycle events, setup,
configuration, deploy, undeploy, and
shutdown. For each layer, AWS OpsWorks runs a set of standard
recipes for each event. In addition, you can provide custom recipes
for any or all layers and events. AWS OpsWorks runs custom event
recipes after the standard recipes. LayerCustomRecipes
specifies the custom recipes for a particular layer to be run in
response to each of the five events.

To specify a recipe, use the
cookbook's directory name in the repository followed by two colons and
the recipe name, which is the recipe's file name without the .rb
extension. For example: phpapp2::dbsetup specifies the dbsetup.rb
recipe in the repository's phpapp2 folder.

Returns a reference to this object so that method calls can be chained together.

Parameters:

defaultRecipes AWS OpsWorks supports five lifecycle events, setup,
configuration, deploy, undeploy, and
shutdown. For each layer, AWS OpsWorks runs a set of standard
recipes for each event. In addition, you can provide custom recipes
for any or all layers and events. AWS OpsWorks runs custom event
recipes after the standard recipes. LayerCustomRecipes
specifies the custom recipes for a particular layer to be run in
response to each of the five events.

To specify a recipe, use the
cookbook's directory name in the repository followed by two colons and
the recipe name, which is the recipe's file name without the .rb
extension. For example: phpapp2::dbsetup specifies the dbsetup.rb
recipe in the repository's phpapp2 folder.

Returns:

A reference to this updated object so that method calls can be chained
together.

Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>

Returns:

Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>

Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>

Parameters:

installUpdatesOnBoot Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>

Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>

Returns a reference to this object so that method calls can be chained together.

Parameters:

installUpdatesOnBoot Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>

Returns:

A reference to this updated object so that method calls can be chained
together.

Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>

Returns:

Whether to install operating system and package updates when the
instance boots. The default value is true. If this value
is set to false, you must then update your instances
manually by using CreateDeployment to run the
update_dependencies stack command or manually running
yum (Amazon Linux) or apt-get (Ubuntu) on
the instances. <note>

We strongly recommend using the default value
of true, to ensure that your instances have the latest
security updates. </note>