AWS OpsWorks, a configuration management service, helps you configure and manage applications in a cloud enterprise using Chef
OpsWorks Stacks allows you to use Chef cookbooks and solutions in configuration managementOpsWorks StacksOpsWorks Stacks offers a simple and flexible method to create and manage stacks, groups or resources such as load balancers, web, database, and server servers, and applications deployed on them
OpsWorks Stacks assists with monitoring and deployment of applications within the stacks.
OpsWorks for Chef Automate does not require or create Chef servers. OpsWorks Stacks performs some of its own work, but is not required to create them.
OpsWorks Stacks monitors instances health and provides new instances when necessary by using Auto Healing or Auto Scaling
OpsWorks Stacks integrates into IAM to control how users interact with stacks. It can determine what stacks can do for the user’s behalf and what AWS resources can be accessed by an app.
OpsWorks Stacks is integrated with CloudWatch, CloudTrail and CloudWatch to allow monitoring and logging
OpsWorks Stacks are accessible globally and can be used globally to create and manage instances.
Stack is the core AWS OpsWorks Stacks component.
Stack is a container that holds AWS resources such as EC2, RDS instances, and other resources. They all have a common purpose and should therefore be logically managed together
Stack helps to manage resources as a group. It also defines default configuration settings such as the OS and AWS region of instances.
VPC can also be used to run stacks, allowing them to be isolated from user interaction.
You can create separate Stacks for different environments such as Dev, QA, etcLayers
Stacks are used to manage cloud resources within specialized groups called layers.
A layer is a collection of EC2 instances that are used to serve a specific purpose, such hosting a database server or serving applications.
Layers rely on Chef recipes to manage tasks such as installing packages on instances, deploying apps, or running scripts
You can store custom recipes and other files in one or more cookbooks.
Layers rely on Chef recipes to manage tasks such as installing packages on init instances, deploying apps, and running scripts.
OpsWorks Stacks runs each layer’s recipes, even if an instance is part of multiple layers, e.g. instance hosting both the application as well as the mysql database server
AWS OpsWorks stacks features is a series of lifecycle events – Setup, Configure Deploy and Undeploy – which automatically runs a specified set of recipes at each instanceSetupOnce an instance has started, OpsWorks triggers Setup. This runs recipes to set the instance up according to the layer configuration, e.g. Installation of apache and PHP packages
Once setup is complete AWS OpsWorks triggers the Deploy event. This triggers recipes to deploy your application on the new instance.
ConfigureWhen an instance enters or exits the online state, AWS OpsWorks triggers the Configure event for all instances in the stack.
Event runs each layer’s configure recipes to modify configuration to reflect current online instances, e.g. The Configure recipes for HAProxy layers can modify the load balancer configuration to reflect added or removed application server instances.
DeployOpsWorks triggers the Deploy event when a Deploy command executes, to deploy the application on a set of servers.
Event runs recipes on the server application servers to deploy the application and any files related to it to the layer’s instances.
UndeployOpsWorks triggers an Undeploy event if an app is deleted, or an Undeploy command executed to remove an application from a set.
Event runs recipes to remove all versions of the application and perform any other cleanup tasks.
ShutdownOpsWorks triggers an Shutdown event when an instance has been shut down.