AWS OpsWorks CM

Name: AWS OpsWorks CM API
Brand: AWS OpsWorks CM
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdhmac19 EndpointsREST

For Agents

Provision and operate managed Chef Automate or Puppet Enterprise master servers — create servers, register nodes, manage backups, and rotate engine credentials.

Connect the AWS OpsWorks CM to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS OpsWorks CM, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AWS OpsWorks CM API.

Provision a managed Chef Automate or Puppet Enterprise master server with engine version and instance type

Schedule and trigger on-demand backups of the master server with configurable retention

Restore a server from a backup to recover after configuration loss or accidental deletion

GET STARTED

Start building with AWS OpsWorks CM API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS OpsWorks CM, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS OpsWorks CM, keeping it validated and agent-ready. OpsWorks CM is AWS's managed configuration-management service for Chef Automate and Puppet Enterprise — it provisions and operates managed Chef or Puppet master servers, schedules automated backups, registers nodes against the master, and rotates engine credentials. The 19 endpoints cover Server CRUD, Node association/disassociation, Backup management, AccountAttributes for service quotas, and the EngineAttributes flow that returns Chef starter kits or Puppet master credentials.

Use Cases

Patterns agents use AWS OpsWorks CM API for, with concrete tasks.

★ Run a Managed Chef Automate Master

Operations teams that have standardised on Chef but want to offload master server maintenance can use OpsWorks CM. CreateServer provisions a Chef Automate master with a chosen engine version, instance type, backup retention and maintenance window, and returns EngineAttributes including a starter kit and admin credentials. The agent can then call AssociateNode to register EC2 instances against the master so each node pulls cookbooks on a regular schedule.

Call CreateServer with Engine=ChefAutomate, EngineVersion=2, InstanceType=m5.large, ServiceRoleArn and InstanceProfileArn, then poll DescribeServers until Status=HEALTHY

Operate a Puppet Enterprise Estate

Teams running Puppet Enterprise can let OpsWorks CM manage the master server, with daily automated backups and AWS-handled patching. CreateServer with Engine=Puppet returns a master URL and admin password; AssociateNode binds individual EC2 nodes to the master. The agent can pair this with PuppetDB queries running on the same master to manage configuration drift across an estate.

Call CreateServer with Engine=Puppet, then AssociateNode with NodeName, EngineAttributes including PUPPET_NODE_CSR for certificate signing

Disaster Recovery via Server Backups

OpsWorks CM-managed servers store all configuration in S3 backups (cookbook revisions, node certificates, internal config). CreateBackup triggers an on-demand backup; RestoreServer rebuilds a server from a backup id, optionally to a different instance type. An agent can run a scheduled validation that creates a backup, restores it into a sandbox server, and verifies node convergence before retiring the validation server.

Call CreateBackup on the production server, then RestoreServer with the returned BackupId into a non-production server name to verify the backup is usable

AI Agent Integration for Configuration Management Operations

Through Jentic, an SRE agent can manage Chef Automate or Puppet Enterprise masters as a structured tool — provision, attach nodes, back up, restore, rotate credentials. Jentic returns each OpsWorks CM operation's input schema and brokers AWS credentials, so day-2 operations on managed configuration servers can run as LLM tool calls rather than bespoke scripts.

Resolve the intent 'create a Chef Automate server' via Jentic search, load CreateServer, and execute it with Engine=ChefAutomate, InstanceType, ServiceRoleArn and InstanceProfileArn

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for aws opsworks cm, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.CreateServer

Provision a Chef Automate or Puppet Enterprise master server

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.AssociateNode

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.DisassociateNode

Disassociate a node from the master

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.CreateBackup

Trigger an on-demand backup

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.RestoreServer

Restore a server from a backup

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.DeleteServer

Delete a managed server

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.DeleteBackup

Delete a stored backup

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.CreateServer

Provision a Chef Automate or Puppet Enterprise master server

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.AssociateNode

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.DisassociateNode

Disassociate a node from the master

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.CreateBackup

Trigger an on-demand backup

POST

/#X-Amz-Target=OpsWorksCM_V2016_11_01.RestoreServer

Restore a server from a backup

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys are stored encrypted in the Jentic MAXsystem vault. Jentic signs each OpsWorks CM control-plane request with SigV4 on the agent's behalf — engine-specific credentials returned in EngineAttributes can be sent back into the vault rather than the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a Chef Automate server') and Jentic returns the matching OpsWorks CM operation with its input schema, so the agent can call CreateServer, CreateBackup or AssociateNode without browsing the AWS docs.

Time to first call

Direct OpsWorks CM integration: 1-2 days for IAM scoping, server provisioning polling and EngineAttributes wiring. Through Jentic: a few hours — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AWS OpsWorks Stacks

OpsWorks Stacks is the older AWS-managed Chef abstraction at the stack/layer level rather than a managed master server

Choose OpsWorks Stacks when you want AWS to fully manage Chef recipes per layer. Use OpsWorks CM when you bring your own cookbooks/manifests and want a managed Chef Automate or Puppet Enterprise master.

Complementary

Amazon EC2

EC2 hosts the nodes you associate against the OpsWorks CM master server

Use to provision the EC2 instances that are subsequently registered against a Chef Automate or Puppet master.

Alternative

AWS CodeDeploy

CodeDeploy is the AWS-recommended modern alternative for application deployment

Choose CodeDeploy when migrating away from Chef or Puppet for application-deployment workloads. Use OpsWorks CM only when the team is committed to a Chef Automate or Puppet Enterprise control plane.

Complementary

Amazon EC2 Auto Scaling

Auto Scaling adjusts the node count that connects to the OpsWorks CM master

Use to scale the fleet of nodes managed by Chef or Puppet, then call AssociateNode/DisassociateNode through OpsWorks CM as instances come and go.

FAQs

Specific to using AWS OpsWorks CM API through Jentic.

Why is there no official OpenAPI spec for AWS OpsWorks CM?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS OpsWorks CM via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS OpsWorks CM API use?

The control plane is signed with AWS Signature Version 4 using IAM access keys. The Chef Automate or Puppet Enterprise master itself uses engine-specific credentials (pivotal key for Chef, admin password for Puppet) returned in the EngineAttributes of CreateServer. Through Jentic, AWS credentials live in the MAXsystem vault and sign each control-plane call on the agent's behalf.

Can I run both Chef Automate and Puppet Enterprise with this API?

Yes. CreateServer accepts an Engine of ChefAutomate or Puppet, with engine-specific EngineAttributes for each. The same Backup, Restore, AssociateNode and DisassociateNode endpoints work across both engines, with the engine-specific node bootstrapping handled via the EngineAttributes payload.

What are the rate limits for OpsWorks CM?

AWS applies per-account control-plane throttling. Server provisioning takes several minutes; DescribeServers returns Status=CREATING, HEALTHY, FAILED, etc. and should be polled rather than retrying the create call. Service quotas are surfaced via DescribeAccountAttributes.

How do I trigger a backup through Jentic?

Use the Jentic search query 'create an OpsWorks CM backup', load CreateBackup, and execute it with the ServerName and an optional Description. Jentic signs the request with SigV4 against your stored AWS credentials and returns the BackupId, which the agent can later pass to RestoreServer if needed.

How do I retrieve the Chef starter kit after creating a server?

The starter kit URL is returned in the EngineAttributes of the CreateServer response and can be re-fetched with DescribeServers. The kit contains the pivotal key, knife configuration and a sample cookbook so an operator can begin uploading cookbooks immediately.