Disassociate a Node from an AWS OpsWorks for Chef Automate Server
This section describes how to disassociate, or remove, a managed node from management by an AWS OpsWorks for Chef Automate server. This operation is performed on the command line; you cannot disassociate nodes in the AWS OpsWorks for Chef Automate management console. Currently, the AWS OpsWorks for Chef Automate API does not allow for batch removal of multiple nodes. The command in this section disassociates one node at a time.
We recommend that you disassociate nodes from a Chef server before you delete the
server, so that the nodes continue to operate without trying to reconnect with the server. To
do this, run the
disassociate-node AWS CLI command.
To disassociate nodes
In the AWS CLI, run the following command to disassociate nodes.
Node_nameis the name of the node that you want to disassociate; for Amazon EC2 instances, this is the instance ID.
Server_nameis the name of the Chef server from which you want to disassociate the node. Both parameters are required. The
--regionparameter is not required unless you want to disassociate a node from a Chef server that is not in your default region.
aws opsworks-cm --region
The following command is an example.
aws opsworks-cm --region us-west-2 disassociate-node --node-name i-0010zzz00d66zzz90 --server-name opsworkstest
Wait until a response message indicates that the disassociation is finished.
For more information about how to delete an AWS OpsWorks for Chef Automate server, see Delete an AWS OpsWorks for Chef Automate Server.