No images found for AMI when updating aws_instance

[jeroen-nijssen]

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 other comments that do not add relevant new information or questions, 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

Terraform v0.12.3

• provider.aws v2.44.0
• provider.null v2.1.2

Affected Resource(s)

• aws_instance

Terraform Configuration Files

resource "aws_instance" "ec2_instance" {
  ami = "${var.ami}"
  instance_type = "${var.instance_type}"
  
  ebs_optimized        = false
  monitoring           = true
  key_name             = "${var.key_name}"
  iam_instance_profile = "${var.iam_instance_profile}"

#Networking
  vpc_security_group_ids = "${var.security_group_ids}"
  subnet_id = "${data.aws_subnet.Subnet-Used.id}"
  source_dest_check    = true

#Disks
  root_block_device {
    volume_size           = "${var.os_disk_size}"
    volume_type           = "gp2"
    delete_on_termination = false
    encrypted             = true
    kms_key_id            = "alias/xxx"

  }

  ebs_block_device {
    device_name           = "/dev/xvdz"
    volume_size           = "${var.data_disk_size}"
    volume_type           = "gp2"
    delete_on_termination = false
    encrypted             = true
    kms_key_id            = "alias/xxx"

  }

  lifecycle {
    ignore_changes = ["ami", "user_data", "subnet_id", "key_name", "ebs_optimized", "private_ip", "root_block_device", "ebs_block_device"]
  }
}

Expected Behavior

Run trough the plan and update the instance accourdingly

Actual Behavior

Plan fails with error

Error: No images found for AMI ami-05ded958b37e57xxx

Steps to Reproduce

1. terraform init
2. terraform plan

References

• aws_launch_config fails with instance-store AMIs - new in 2.23.0 #9775

[sfesfizh]

Suggestion commented here has solved my problem:

no error when version
provider "aws" {
version = "<=2.22"

[Criegg]

I was able to fix this issue with the same suggestion, however it introduced a new problem:

Error: Unsupported block type

  on ecs-ec2.tf line 126, in resource "aws_ecs_cluster" "ecs_service_cluster":
 126:   setting {

Blocks of type "setting" are not expected here.

This works in (likely) any version above 2.22 as it works on 2.23 and latest, but both of these reintroduce the AMI error.

[justinretzolk]

Hey y'all 👋 Thank you for taking the time to file this issue and for the continued discussion! Given that there's been a number of AWS provider releases since the last update, can anyone confirm whether you're still experiencing this behavior?

[jeroen-nijssen]

Hey @justinretzolk 👋🏼

From my perspective, we have solved our challenge here.
I don't remember when the issue got solved, but it's somewhere ages ago...

Thanks for following up. 👍🏼

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.