Menu
AWS OpsWorks
User Guide (API Version 2013-02-18)

Delete an AWS OpsWorks for Puppet Enterprise Server

This section describes how to delete an AWS OpsWorks for Puppet Enterprise server. Deleting a server also deletes its events, logs, and any modules 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 Puppet master. In this release, you can disassociate nodes by running an AWS CLI command.

Step 1: Disassociate Managed Nodes

Disassociate nodes from the Puppet master 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 Puppet master from which you want to disassociate the node. The value of --node-name can be an instance ID.

    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.

    
                  AWS OpsWorks for Puppet Enterprise Delete Server command
  2. Choose Delete Puppet Enterprise server.

  3. When you are prompted to confirm the deletion, fill in the check box to delete associated roles and resources, and then choose Yes, Delete.

See Also