Detaching Resources - AWS OpsWorks

Detaching Resources

Important

AWS OpsWorks Stacks is no longer accepting new customers. Existing customers will be able to use the OpsWorks console, API, CLI, and CloudFormation resources as normal until May 26, 2024, at which time they will be discontinued. To prepare for this transition, we recommend you transition your stacks to AWS Systems Manager as soon as possible. For more information, see AWS OpsWorks Stacks End of Life FAQs and Migrating your AWS OpsWorks Stacks applications to AWS Systems Manager Application Manager.

When you no longer need an attached resource, you can detach it. This resource remains registered with the stack and can be attached elsewhere.

Unassigning Amazon EBS Volumes

Use the following procedure to unassign an Amazon EBS volume from its instance.

To unassign an Amazon EBS volume
  1. Ensure that the instance is in the offline state.

  2. On the Resources page, click Volumes and click volume name.

  3. On the volume's details page, click Unassign.

Disassociating Elastic IP Addresses

Use the following procedure to disassociate an Elastic IP address from its instance.

To disassociate an Elastic IP address
  1. On the Resources page, click Elastic IPs and click edit in the address's Actions column.

  2. On the address's details page, click Disassociate.

After you disassociate an address, AWS OpsWorks Stacks triggers a Configure lifecycle event to notify the stack's instances of the change.

Detaching Amazon RDS Instances

Use the following procedure to detach an Amazon RDS from an app.

To detach an Amazon RDS instance
  1. On the Resources page, click RDS and click the appropriate app in the Apps column.

  2. Click Edit and edit the app configuration to detach the instance. For more information, see Editing Apps.

Note

This procedure detaches an Amazon RDS from a single app. If the instance is attached to multiple apps, you must repeat this procedure for each app.