API archive entry · source-reported
AWS OpsWorks CM
AWS OpsWorks CM AWS OpsWorks for configuration management (CM) is a service that runs and manages configuration management servers. You can use AWS OpsWorks CM to create and manage AWS OpsWorks for Chef Automate and AWS OpsWorks for Puppet Enterprise servers, and add or remove nodes for the servers to manage. Glossary of terms Server : A configuration management server that can be highly-available. The configuration management server runs on an Amazon Elastic Compute Cloud (EC2) instance, and may use various other AWS services, such as Amazon Relational Database Service (RDS) and Elastic Load Balancing. A server is a generic abstraction over the configuration manager that you want to use, much like Amazon RDS. In AWS OpsWorks CM, you do not start or stop servers. After you create servers, they continue to run until they are deleted. Engine : The engine is the specific configuration manager that you want to use. Valid values in this release include ChefAutomate and Puppet . Backup : This is an application-level backup of the data that the configuration manager stores. AWS OpsWorks CM creates an S3 bucket for backups when you launch the first server. A backup maintains a snapshot of
Archive history
This history reflects directory observations and owner review, not a provider release log.
- First observed: Sep 20, 2026
- Last directory-field change: Sep 20, 2026
- Current source observation: Sep 20, 2026
Published source events
added
Sep 20, 2026 · Added from an approved API directory.
Where to check product changes
Use the provider documentation and status channels for releases, breaking changes, and outages.
Source reference
This page separates source-reported facts from questions that need live provider verification.