Delete an AWS OpsWorks for Chef Automate Server - AWS OpsWorks
Step 1: Disassociate Managed NodesStep 2: Delete the Server

Delete an AWS OpsWorks for Chef Automate Server

Important

AWS OpsWorks for Chef Automate reached end of life on May 5, 2024 and has been disabled for both new and existing customers. We recommend that existing customers migrate to Chef SaaS or an alternative solution. If you have questions, you can reach out to the AWS Support Team on AWS re:Post or through AWS Premium Support.

This section describes how to delete an AWS OpsWorks for Chef Automate server. Deleting a server also deletes its events, logs, and any cookbooks that were stored on the server. Supporting resources (Amazon Elastic Compute Cloud instance, Amazon Elastic Block Store volume, etc.) are deleted also, along with all automated backups.

Although deleting a server does not delete nodes, they are no longer managed by the deleted server, and will continuously attempt to reconnect. For this reason, we recommend disassociating managed nodes before you delete a Chef server. In this release, you can disassociate nodes by running an AWS CLI command.

Step 1: Disassociate Managed Nodes

Disassociate nodes from the 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

  1. In the AWS CLI, run the following command to disassociate nodes. Server_name is the name of the Chef server from which you want to disassociate the node.

    aws opsworks-cm --region Region_name disassociate-node --node-name Node_name --server-name Server_name

  2. Wait until a response message indicates that the disassociation is finished.

Step 2: Delete the Server

  1. On the server’s tile on the dashboard, expand the Actions menu.

  2. Choose Delete server.

  3. When you are prompted to confirm the deletion, choose Yes.