Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support PrivateDnsNameOptions field in EC2 launch templates #22199

Closed
drakedevel opened this issue Dec 14, 2021 · 2 comments · Fixed by #23365
Closed

Support PrivateDnsNameOptions field in EC2 launch templates #22199

drakedevel opened this issue Dec 14, 2021 · 2 comments · Fixed by #23365
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.
Milestone

Comments

@drakedevel
Copy link
Contributor

drakedevel commented Dec 14, 2021

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

Amazon recently launched support for IPv6-only subnets. Instances on these hosts use their instance ID for their private hostname, instead of the (non-existent) private IPv4 address. In this same announcement, they added support for opting-in to this behavior for other instances, via a new PrivateDnsNameOptions parameter passed to RunInstances, etc.

This issue is intended to be specifically about that new field in launch templates, but I'm happy to edit this issue to cover that field more broadly if desired.

New or Affected Resource(s)

  • aws_launch_template (both resource and data source)

Potential Terraform Configuration

Mirroring the existing metadata_options approach:

resource "aws_launch_template" "my_template" {
  // ... existing fields
  private_dns_name_options {
    enable_resource_name_dns_aaaa_record = true
    enable_resource_name_dns_a_record    = true
    hostname_type                        = "resource-name" // Or "ip-name"
  }
}

For data "aws_launch_template" the same field can be exposed with the same structure.

References

@drakedevel drakedevel added the enhancement Requests to existing resources that expand the functionality or scope. label Dec 14, 2021
@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/ec2 Issues and PRs that pertain to the ec2 service. labels Dec 14, 2021
@anGie44 anGie44 removed the needs-triage Waiting for first response or review from a maintainer. label Dec 14, 2021
@github-actions github-actions bot added this to the v4.6.0 milestone Mar 18, 2022
@github-actions
Copy link

This functionality has been released in v4.6.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
Copy link

github-actions bot commented May 7, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
2 participants