aws_launch_template not configuring metadata_options

[phzietsman]

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 CLI and Terraform AWS Provider Version

$ terraform -v
Terraform v0.14.11
+ provider registry.terraform.io/hashicorp/aws v4.22.0
+ provider registry.terraform.io/hashicorp/helm v2.6.0
+ provider registry.terraform.io/hashicorp/kubernetes v2.12.1
+ provider registry.terraform.io/hashicorp/template v2.2.0
+ provider registry.terraform.io/hashicorp/tls v3.4.0

Your version of Terraform is out of date! The latest version
is 1.2.5. You can update by downloading from https://www.terraform.io/downloads.html

Affected Resource(s)

• aws_launch_template

Terraform Configuration Files

resource "aws_launch_template" "node_group_launch_template" {
  for_each               = var.eks_node_subnet_map
  name                   = "${local.cluster_base_name}-${each.key}-lt"
  user_data              = data.template_cloudinit_config.cluster_node_group_user_data.rendered
  key_name               = aws_key_pair.node_group_key_pair.key_name
  vpc_security_group_ids = [aws_security_group.cluster_sg.id]
  update_default_version = true

  block_device_mappings {
    device_name = "/dev/xvda"
    ebs {
      delete_on_termination = "true"
      volume_size           = each.value["disk_size"]
      volume_type           = "gp2"
    }
  }

  metadata_options {
    http_tokens                 = "required"
    http_put_response_hop_limit = 2
    instance_metadata_tags      = "disabled"
  }

  # lifecycle {
  #   ignore_changes = [metadata_options]
  # }

  tag_specifications {
    resource_type = "instance"
    tags          = local.deployment_tags
  }
}

Expected Behavior

The metadata options are set on the launch template after apply.

Actual Behavior

The metadata options are NOT set on the launch template after apply. On a new plan TF detects that options are not set and want to make the required changes, but it has not effect.

Steps to Reproduce

1. terraform apply

[ewbankkit]

Similar: #25896.

[bevanbennett]

To be more specific, it appears that aws_instance supports instance_metadata_tags as part of metadata_options, but aws_launch_configuration does not. This is a huge blocker for a project of ours.

[kruftmeister]

To be more specific, it appears that aws_instance supports instance_metadata_tags as part of metadata_options, but aws_launch_configuration does not. This is a huge blocker for a project of ours.

Launch Configuration != Launch Template, especially AWS phasing LC out in favour of LT.

[amille44420]

I confirm meeting such issue as well ; since we are providing configurations for metadata_options every deployment will create new versions for our launch templates which sadly trigger updates on our EKS node pools.

We met this issue as soon as we added metadata_options to our definitions.

[seanamos]

For those running into this, it seems to be as a result of a terraform bug when http_endpoint isn't explicitly set.

Setting http_endpoint = "enabled" makes things work as expected.

[ohookins]

The documentation says that http_endpoint defaults to enabled, but this doesn't seem to be the reality of what is implemented.

[good92]

#29024

[good92]

#24774

[good92]

terraform-aws-modules/terraform-aws-eks#1785
"Yes, the problems seem to be related to the instance_metadata_tags = "enabled". Once disabled the problem disapears"

ok, we've changed the default behavior to disabled - disappointing that AWS has different tag requirements but we will leave it up to users to manage for now

[github-actions]

This functionality has been released in v4.61.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[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.