-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: #31117
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v5.3.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! |
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. |
Terraform Core Version
1.4.2
AWS Provider Version
v4.64.0
Affected Resource(s)
aws_vpc_endpoint
Expected Behavior
When you create VPC Interface type S3 Endpoint in AWS Console, the "Enable private DNS names" section has two checkboxes:
The second checkbox can only be checked if the first one is checked. And, the second checkbox is the one that actually requires the presence of S3 Gateway type Endpoint in the VPC.
The first checkbox by itself can be checked in AWS Console without the presence of the S3 Gateway type Endpoint.
"aws_vpc_endpoint" resource in Terraform only has one attribute for enabling private DNS, which is called "private_dns_enabled". When you set that attribute to "true", it actually attempts to enable both of the options mentioned above, and hence, causes the error captured in the debug output section if Gateway type S3 Endpoint is not present in the VPC.
So, the expected behavior here should be is there should be secondary attribute available for enabling on the "aws_vpc_endpoint" resource so same API calling behavior can be achieved via terraform as it is through AWS Console or CLI.
Actual Behavior
As stated above, "private_dns_enabled" attribute on the "aws_vpc_endpoint" resource toggles both underlying settings at once:
There needs to be two separate boolean attributes on the "aws_vpc_endpoint" resource available to be able to toggle the two settings independently (although, the second setting is only allowed to be toggled if the first one is checked).
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: