AWS OpsWorks AWS Systems Manager (OpsWorks Migration)
Legacy names AWS OpsWorks, AWS OpsWorks Stacks, AWS OpsWorks for Chef Automate, AWS OpsWorks for Puppet Enterprise
Cloud configuration management and application lifecycle automation using AWS Systems Manager State Manager, Application Manager, and AWS CloudFormation.
Naming timeline
- AWS OpsWorks (AWS OpsWorks Stacks)
Launched on February 18, 2013 as a Chef-based application and server configuration management service on Amazon EC2.
- AWS OpsWorks for Chef Automate & AWS OpsWorks for Puppet Enterprise
Expanded into managed configuration management servers with AWS OpsWorks for Chef Automate (December 2016) and AWS OpsWorks for Puppet Enterprise (November 16, 2017) on the opsworkscm API.
- AWS Systems Manager (OpsWorks Migration)Current name
AWS OpsWorks Stacks reached End of Life on May 26, 2024; workloads migrated to AWS Systems Manager State Manager, Application Manager, and Automation alongside AWS CloudFormation.
What replaced AWS OpsWorks?
AWS OpsWorks has been superseded by AWS Systems Manager (OpsWorks Migration), with the latest change on 26 May 2024 (AWS OpsWorks Stacks End of Life). Earlier names covered by this entry also include AWS OpsWorks Stacks, AWS OpsWorks for Chef Automate, AWS OpsWorks for Puppet Enterprise. Cloud configuration management and application lifecycle automation using AWS Systems Manager State Manager, Application Manager, and AWS CloudFormation. The underlying legacy API or CLI surface is deprecated, so a technical migration is required.
Also known as
- Systems Manager State Manager
- Systems Manager Application Manager
Technical identifiers
Legacy identifiers deprecated. The underlying API or CLI surface for the legacy name is officially deprecated, so this change requires a technical migration rather than a label update.
| AWS Service APIs / SDKs | opsworks opsworkscm ssm |
|---|---|
| AWS CLI Commands | aws opsworks aws opsworks-cm aws ssm |
| IAM Actions & Policies | opsworks:* opsworks-cm:* ssm:* |
| Terraform Resources (aws_*) | aws_opsworks_stack aws_opsworks_application aws_opsworks_instance aws_ssm_association aws_ssm_document |
The opsworks and opsworkscm APIs, CLI commands (aws opsworks, aws opsworks-cm), and Terraform aws_opsworks_* resources are retired following the May 26, 2024 End of Life; migrate to aws_ssm_association and aws_ssm_document.
Notes & disambiguation
- AWS OpsWorks Stacks reached End of Life on May 26, 2024, following the earlier retirement of AWS OpsWorks for Chef Automate and AWS OpsWorks for Puppet Enterprise.
- AWS provided official migration and stack-detachment tooling to transition OpsWorks Stacks layers, lifecycle events, and Chef recipes to AWS Systems Manager (Application Manager, State Manager, and Automation runbooks) and AWS CloudFormation.
- The legacy opsworks and opsworkscm APIs, CLI commands, and Terraform aws_opsworks_* resources are retired and replaced by ssm and cloudformation primitives.
Sources & official documentation
- Official documentation ↗
- Product page ↗
- Seamlessly off-board from AWS OpsWorks Stacks by detaching resources — AWS Cloud Operations Blog (Apr 11, 2024)
- Migrate your AWS OpsWorks Stacks to AWS Systems Manager — AWS Cloud Operations Blog (Jan 1, 2023)
- Announcing AWS OpsWorks — AWS What's New (Feb 18, 2013)
Catalog last updated . Spotted an error? Suggest an edit