Allow private_dns_name to be set via aws_vpc_endpoint_service resource

[breathingdust]

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

private_dns_name is currently an exported attribute, but the API does allow it to be set when creating a VPC Endpoint Service Configuration.

New or Affected Resource(s)

• aws_vpc_endpoint_service

Potential Terraform Configuration

resource "aws_vpc_endpoint_service" "test" {
  acceptance_required = false
  network_load_balancer_arns = [
    aws_lb.test1.arn,
  ]
  private_dns_name = ""
}

References

• https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVpcEndpointServiceConfiguration.html
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc_endpoint_service#private_dns_name

[ewbankkit]

Addressed via #16495.

[bflad]

Support for configurable private_dns_name and adding a private_dns_name_configuration attribute in the aws_vpc_endpoint_service resource has been merged and will release with version 3.23.0 of the Terraform AWS Provider. Thanks to @craigedmunds and @stijndehaes for their efforts here. 👍

[ghost]

This has been released in version 3.23.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 for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!