Stack stuck on deletion - Understanding long-running destroy operations

Last updated: December 19, 2025

If your Terraform stack appears to be stuck during deletion with messages like "Still destroying..." for extended periods, this is typically normal behavior caused by AWS dependency cleanup rather than a platform issue.

Why this happens

When you see messages like:

Still destroying... aws_iam_role.ec2_role
Still destroying... aws_ebs_volume.data

This indicates that AWS is still holding onto one or more dependent resources, and Terraform is waiting for AWS to finish cleaning things up. This process can take 40-90 minutes in some cases.

Common causes

The most frequent reasons for extended deletion times include:

  • IAM roles still attached to EC2 instance profiles or other services

  • EBS volumes marked as "in-use" or stuck on zombie ENIs (Elastic Network Interfaces)

  • AWS internally retrying dependency cleanup processes

AWS won't delete these resources until all dependencies are fully detached, which can take considerable time.

What to expect

During this process:

  • Terraform will continue polling AWS for status updates

  • You'll see repeated "Still destroying..." messages in the logs

  • The destroy operation will complete once AWS finishes its cleanup

  • AWS doesn't provide detailed progress information during this stage

Important note about completion

Sometimes the destroy operation may appear to "fail" even though the resources were successfully removed. This can happen when Terraform continues polling AWS until it receives final confirmation, but AWS is slow to update the resource status even after the underlying deletion has completed. The logs may show "Still destroying..." messages even though the resources are already gone on the AWS side.

This behavior is normal when AWS is slow to finalize state transitions.

When to contact support

If your stack has been stuck in deletion for an unusually long time (over 2 hours) or if you need to interrupt the process for urgent reasons, contact support. We can manually stop the run, though this will interrupt the destroy process.