


 Resolution
-----------



Generally, Amazon EBS volumes are immediately deleted when you use the Amazon Elastic Compute Cloud (Amazon EC2) console or AWS Command Line Interface (AWS CLI). However, the volume can get stuck in the "deleting" state when there's an active snapshot that's associated with your volume.


If you make a **CreateSnapshot** API call immediately before making a **DeleteVolume** request, then volume deletion is postponed until snapshot creation completes. Before deleting a volume, check for any snapshot creations that are still in progress. For instructions on how to access snapshot information, see [View Amazon EBS snapshot information](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-describing-snapshots.html).


**Note:** Even after a snapshot creation is complete, volume deletion might still be delayed because volume workflows are asynchronous.





---








So if my volume is still stuck in "Deleting" state after 24h, what am I supposed to do?

My basic AWS plan does not allow me to open a support ticket...

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

My Amazon Elastic Block Store (Amazon EBS) volume is stuck in the "deleting" state, and I don't know why.

Resolve an EBS volume that’s stuck in the deleting state

Why is my Amazon EBS volume stuck in the "deleting" state?

Storage

AWS re:Post Live - Using Amazon Elastic Block Store (EBS) Optimally

Why is my Amazon EBS volume stuck in the Optimizing state when I modify the volume?

Why is my Amazon EBS volume stuck in the "deleting" state?

Resolution

Relevant content