👀 Views: 51 💬 Answers: 1 📅 Created: 2025-06-05

terraform aws ec2 ebs HCL

I've been struggling with this for a few days now and could really use some help. I'm trying to create multiple AWS EC2 instances along with their respective EBS volumes using Terraform, but I'm running into a frustrating scenario. Despite specifying valid snapshot IDs for the EBS volumes, Terraform throws an behavior during the apply phase. The behavior message I'm receiving is: ``` behavior: behavior creating EBS Volume: InvalidSnapshot.InUse: The snapshot 'snap-0abcd1234efgh5678' is currently in use ``` I've double-checked the snapshot IDs, and they appear to be valid and not in use by any other volume. Here's a snippet of my Terraform configuration: ```hcl resource "aws_instance" "web" { count = 3 ami = "ami-0123456789abcdef0" instance_type = "t2.micro" ebs_block_device { device_name = "/dev/sdh" snapshot_id = "snap-0abcd1234efgh5678" volume_size = 30 volume_type = "gp2" } } ``` I've also tried running `terraform plan` to see if there are any issues with the resource dependencies, but it looks fine. To troubleshoot, I confirmed that the snapshot is indeed available in the correct region and account. I've tried recreating the snapshot and even using a different one, but the scenario continues. I suspect there might be a dependency scenario or a timing question based on how Terraform is creating these resources. Has anyone encountered a similar scenario, or does anyone have any insights on how to resolve this? Any help would be greatly appreciated! Has anyone else encountered this? I'm working on a service that needs to handle this. What's the best practice here?