aws_launch_template: add the option to tag network-interfaces

[AlexisJackson]

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

Description

The LaunchTemplateTagSpecificationRequest API docs show that network-interface is an option. Can this be added to the list of supported types? We pair ECS Clusters with AutoScaling Groups and it would be helpful if the network-interfaces/enis attached to the EC2 Instances were tagged along with the instances and volumes.

https://github.com/hashicorp/terraform-provider-aws/blob/main/aws/resource_aws_launch_template.go#L588-L591

New or Affected Resource(s)

• aws_launch_template

Potential Terraform Configuration

tag_specifications {
    resource_type = "network-interface"

    tags = {
      Name = "test"
    }
}

References

• AWS LaunchTemplateTagSpecificationRequest API docs

[Aym3nTN]

Really appreciate adding this feature, we're building several EKS clusters with severals nodes for our different environments and we need to efficiently track our spending.

[alexmnyc]

same here. it is a problem! why not allow the entire list of tag specification allowed enum?

[gordonbondon]

Should be fixed by #20409

[github-actions]

This functionality has been released in v3.53.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.