Detaching Resources - AWS OpsWorks

Detaching Resources

Important

The AWS OpsWorks Stacks service reached end of life on May 26, 2024 and has been disabled for both new and existing customers. We strongly recommend customers migrate their workloads to other solutions as soon as possible. If you have questions about migration, reach out to the AWS Support Team on AWS re:Post or through AWS Premium Support.

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.

    Volume details page showing settings for PHP-LB-PIOPs, including EC2 Volume ID and mount point.

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.

    Elastic IP details page showing settings for PHP-Vol2 with IP address and instance information.

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.