Legacy stacks and lifecycle events
AWS OpsWorks Stacks was an application management service with stacks, layers, instances, apps, and lifecycle recipes. It reached full shutdown in May 2024, so these concepts describe historical systems only.
How it works
- A stack contained application resources, including instances and apps. A layer held recipes for its lifecycle eventsA lifecycle event is an OpsWorks Stacks event for which layer recipes run..
- The service had Setup, Configure, Deploy, Undeploy, and Shutdown events. A recipe is a set of Chef instructions that configures software.
- For each event, standard layer recipes ran first, followed by configured custom recipes.
- Registered EC2 instances could be assigned to custom layers; registered on-premises instances could be assigned to any layer type.
Exam cues
- If the question says a custom OpsWorks layer recipe runs at a lifecycle event, think after the standard recipes, because custom event recipes followed them.
- If the question says a registered EC2 instance must join a legacy OpsWorks layer, think custom layer, because registered EC2 instances could not be assigned to built-in layers.
- If the question says Windows instances in legacy OpsWorks, think time-based scaling, because load-based instances were not supported for Windows stacks.
Remember
- The five events were Setup, Configure, Deploy, Undeploy, and Shutdown.
- Registered instances required a supported Linux operating system.
- OpsWorks Stacks reached end of support on May 1, 2024.
Trap: OpsWorks Stacks is not available for a new deployment, even when a question describes its historical lifecycle recipes.
Da documentação da AWS (9)
- AWS OpsWorks Stacks reached end of support on May 1, 2024 and is in full shutdown.
- OpsWorks Stacks was an application management service for the application lifecycle.
- OpsWorks Stacks had stacks, layers, instances, and apps; an app and an instance belonged to a specified stack.
- OpsWorks Stacks had five lifecycle events named setup, configuration, deploy, undeploy, and shutdown.
- OpsWorks Stacks ran standard recipes for each layer and event, followed by any custom event recipes.
- The Configure list specified custom recipes to run after a configure event.
- OpsWorks Stacks supported load-based and time-based instance scaling; Windows stacks could use only time-based instances.
- Registered OpsWorks Stacks instances had to use a supported Linux operating system.
- Registered on-premises instances could be assigned to any layer type, while registered EC2 instances could be assigned only to custom layers.
Retirement and migration
AWS OpsWorks is retired. A migration must replace the needed configuration or application management capability rather than create another OpsWorks deployment.
How it works
- Identify the configuration that the legacy system applied and the nodes that need it.
- For compatible Chef cookbooks on Linux managed nodes, create a Systems Manager State Manager associationAn association assigns a configuration and schedule to target resources., a configuration assigned to targets on a schedule.
- Select
AWS-ApplyChefRecipesand a cookbook source such as S3. The document can install the Chef client and run recipes that do not require a Chef server. - Use
why-runto preview recipe changes without applying them. Choose other tools for requirements beyond those recipes.
Exam cues
- If the question says to run compatible Chef recipes on managed Linux nodes, think State Manager and
AWS-ApplyChefRecipes, because the association applies the document to its targets. - If the question says an account has never used Application Manager and wants to start in August 2026, think another service, because access for new customers ended on July 30, 2026.
- If the question says organize resources or inspect application dependencies, think Resource Groups or Application Signals, respectively, because AWS lists them as alternatives for those use cases.
Remember
- OpsWorks Stacks, Chef Automate, and Puppet Enterprise reached end of support on May 1, 2024.
AWS-ApplyChefRecipessupports Chef versions 11 through 18 and sources from Git, GitHub, HTTP, and S3.- Existing Application Manager customers can continue using it; accounts that had not used it cannot start after July 30, 2026.
Trap: State Manager can run compatible Chef recipes, but a cookbook that requires a Chef server does not meet the document’s prerequisites.
An association targets the managed node and runs AWS-ApplyChefRecipes.
The document downloads the cookbook from the selected source.
Da documentação da AWS (10)
- OpsWorks Stacks, OpsWorks for Chef Automate, and OpsWorks for Puppet Enterprise reached end of support on May 1, 2024 and are in full shutdown.
- OpsWorks for Chef Automate and OpsWorks for Puppet Enterprise managed configuration management servers.
- Systems Manager State Manager uses associations to apply a defined configuration to managed nodes on a schedule.
- The AWS-ApplyChefRecipes document runs Chef recipes on Linux Systems Manager managed nodes.
- AWS-ApplyChefRecipes can download cookbooks from Git, GitHub, HTTP, or S3.
- AWS-ApplyChefRecipes supports Chef 11 through 18 and can install the Chef client.
- Cookbooks used with AWS-ApplyChefRecipes must be compatible with Chef Infra Client and not require a Chef server.
- AWS-ApplyChefRecipes can run in why-run mode to show potential recipe changes without making them.
- Starting July 30, 2026, accounts that had not previously used Systems Manager Application Manager cannot access it; existing customers can continue to use it.
- AWS suggests Resource Groups for organizing resources and Application Signals for application-level observability as alternatives to Application Manager.
Flashcards
Nada para revisar aqui agora. Escolha outros tópicos ou outro filtro.
·
Todos os 13 flashcards em lista
What were the main resource types in AWS OpsWorks Stacks?
Stacks, layers, instances, and apps. Apps and instances belonged to a stack.
What were the five AWS OpsWorks Stacks lifecycle events?
Setup, Configure, Deploy, Undeploy, and Shutdown. Custom recipes ran after standard recipes for an event.
A legacy OpsWorks Stacks layer has a custom recipe for its Configure event. When did the custom recipe run relative to standard recipes?
After the standard recipes for that event.
Which automatic scaling types did AWS OpsWorks Stacks support, and which was available for Windows stacks?
Load-based and time-based scaling. Windows stacks could use only time-based instances.
Could a registered EC2 instance be assigned to a built-in OpsWorks Stacks layer?
No. Registered EC2 instances could only be assigned to custom layers. Registered on-premises instances could use any layer type.
A historical OpsWorks Stacks layer uses a custom lifecycle recipe. Did that replace the standard recipes?
No. The custom event recipe ran after the standard recipes.
A team finds a legacy OpsWorks Stacks configuration that registered a server. Which operating system family did registered instances require?
A supported Linux operating system.
Can a team create a new AWS OpsWorks Stacks, Chef Automate, or Puppet Enterprise deployment?
No. All three reached end of support on May 1, 2024 and are in full shutdown.
A team replacing an OpsWorks Stacks configuration needs to run existing Chef recipes on managed Linux nodes. What AWS option can it evaluate?
Use a Systems Manager State Manager association with
AWS-ApplyChefRecipes, provided the cookbooks do not require a Chef server.What were AWS OpsWorks for Chef Automate and OpsWorks for Puppet Enterprise?
Managed configuration management servers. Both reached end of support on May 1, 2024.
A team wants to preview changes from Chef recipes on a Systems Manager managed Linux node without applying them. What option fits?
Use
AWS-ApplyChefRecipesinwhy-runmode.Can a new AWS account use Systems Manager Application Manager as an OpsWorks replacement in August 2026?
No. Accounts that had not previously used it lost access starting July 30, 2026. Existing customers can continue to use it.
Where can Systems Manager AWS-ApplyChefRecipes obtain Chef cookbooks?
Git, GitHub, HTTP, or Amazon S3.