hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.63k stars 9.01k forks source link

[Bug]: VPC Interface Endpoint private_dns_enabled is set to true automatically during creation #37783

Closed raghavanrrs closed 1 month ago

raghavanrrs commented 1 month ago

Terraform Core Version

v1.5.6

AWS Provider Version

v5.52.0

Affected Resource(s)

Latest AWS TF provider version setting the attribute private_dns_enabled to true during creation and in the next run it accepts whatever the value we given as part of variable

Not able to configure PHZ with private_dns_enabled set to false.

Expected Behavior

should accept values passed inside the variable

Actual Behavior

Error: creating Route53 Hosted Zone (sns.ap-southeast-1.amazonaws.com): operation error Route 53: CreateHostedZone, https response error StatusCode: 400, RequestID: ae88012e-f855-4b54-94a9-62dc08fd8e72, ConflictingDomainExists: The VPC vpc-xxxxxxxxxxxxxxxxx in region ap-southeast-1 has already been associated with the hosted zone Z1234567890 with the same domain name.

Relevant Error/Panic Output Snippet

Error: creating Route53 Hosted Zone (sns.ap-southeast-1.amazonaws.com): operation error Route 53: CreateHostedZone, https response error StatusCode: 400, RequestID: ae88012e-f855-4b54-94a9-62dc08fd8e72, ConflictingDomainExists: The VPC vpc-xxxxxxxxxxxxxxxxx in region ap-southeast-1 has already been associated with the hosted zone Z1234567890 with the same domain name.

Terraform Configuration Files

module.interface_endpoints.aws_vpc_endpoint.interface_services["sqs"] will be created

Steps to Reproduce

terraform apply

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

github-actions[bot] commented 1 month ago

Community Note

Voting for Prioritization

Volunteering to Work on This Issue

theipster commented 1 month ago

I've already reported this bug in https://github.com/hashicorp/terraform-provider-aws/issues/37694 (and already submitted a fix in PR https://github.com/hashicorp/terraform-provider-aws/pull/37715). Please feel free to upvote that.

ewbankkit commented 1 month ago

@raghavanrrs Thanks for raising this issue. It has already been noticed in #37694. I'm going to close this one as a duplicate so that we can concentrate discussion in the linked issue. Please add any additional comments there.

github-actions[bot] commented 1 month ago

[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

github-actions[bot] commented 2 weeks ago

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.