Cannot remove aws_instance source for created AMI

[cadavre]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Any.

Affected Resource(s)

• aws_ami_from_instance
• aws_ami_copy

Terraform Configuration Files

resource "aws_instance" "ami_source" {
  ami           = "ami-0e9e6ba6d3d38faa8"
  instance_type = "t2.micro"
}

resource "aws_ami_from_instance" "my_ami" {
  name               = "my-ami"
  source_instance_id = aws_instance.ami_source.id

  lifecycle {
    prevent_destroy = true # does not prevent destruction
    ignore_changes = ["source_instance_id"] # does not prevent destruction
  }
}

Steps to Reproduce

1. terraform apply
2. terraform destroy -target=aws_instance.ami-source

Expected Behavior

Source EC2 instance should be destroyed, but AMI should be kept as after creation it becomes independent resource.

Actual Behavior

Error: Instance cannot be destroyed

  on resources.tf line 144:
 144: resource "aws_ami_from_instance" "my_ami" {

Resource aws_ami_from_instance.my_ami has lifecycle.prevent_destroy set,
but the plan calls for this resource to be destroyed. To avoid this error and
continue with the plan, either disable lifecycle.prevent_destroy or reduce the
scope of the plan using the -target flag.

Removing lifecycle.prevent_destroy produces:

Terraform will perform the following actions:

  # aws_ami_from_instance.my_ami will be destroyed

  # aws_instance.ami_source will be destroyed

[Broundon]

Team,

Is there any update on this issue? i am running into the same problem

[justinretzolk]

Hey y'all 👋 Thank you for taking the time to file this issue. In looking over the configuration, it looks like there's an implicit dependency in the form of the aws_instance.ami_source.id interpolation for source_instance_id that I suspect is the cause of Terraform attempting to destroy the aws_ami_from_instance. I suspect that if you instead hardcoded the source_instance_id value, you wouldn't run into this issue. Can anyone who has experienced this behavior test this to confirm?