1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi there!
I think the only option that might work is to detach the EBS volume, and launch a new instance with it. Per the documentation:
- Ensure that the instance is in the offline state.
- On the Resources page, click Volumes and click volume name.
- On the volume's details page, click Unassign.
I hope this helps.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
Thanks - it turned out OpsWorks was associated with an EBS volume that no longer even existed in my case, so I ended up rebuilding this server from the ground up on a new instance. Hopefully this tip will help someone else though. Not how I wanted to spend the day, but at least it's done now.