v1

latestOpenAPI 3.0.0Apache 2.0 License2026-07-14198892.8 KB

Associates a new node with the server. For more information about how to disassociate a node, see DisassociateNode.

On a Chef server: This command is an alternative to knife bootstrap.

Example (Chef): aws opsworks-cm associate-node --server-name _MyServer_ --node-name _MyManagedNode_ --engine-attributes "Name=_CHEF_ORGANIZATION_,Value=default" "Name=_CHEF_NODE_PUBLIC_KEY_,Value=_public-key-pem_"

On a Puppet server, this command is an alternative to the puppet cert sign command that signs a Puppet node CSR.

Example (Puppet): aws opsworks-cm associate-node --server-name _MyServer_ --node-name _MyManagedNode_ --engine-attributes "Name=_PUPPET_NODE_CSR_,Value=_csr-pem_"

A node can can only be associated with servers that are in a HEALTHY state. Otherwise, an InvalidStateException is thrown. A ResourceNotFoundException is thrown when the server does not exist. A ValidationException is raised when parameters of the request are not valid. The AssociateNode API call can be integrated into Auto Scaling configurations, AWS Cloudformation templates, or the user data of a server's instance.

post/#X-Amz-Target=OpsWorksCM_V2016_11_01.AssociateNode

Headers

X-Amz-Target'OpsWorksCM_V2016_11_01.AssociateNode' required

Request body

ServerNamestring required

The name of the server with which to associate the node.

NodeNamestring required

The name of the node.

Response

Success

NodeAssociationStatusTokenstring

Contains a token which can be passed to the <code>DescribeNodeAssociationStatus</code> API call to get the status of the association request.

All 19 operations