You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result, I end up creating egress rules that just whitelist all traffic in my VPC, simply to allow them to hit the (unknown to Terraform) internal IP of the VPC endpoint.
Describe the solution you'd like.
Just expose the CIDR of the resource, pls :)
Describe alternatives you've considered.
Hardcoding the IP as a variable :(
Additional context
This would probably require modifying the way the associated subnets of the resource are exposed, since an IP is assigned for each subnet the endpoint is deployed in.
The text was updated successfully, but these errors were encountered:
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.
Is your request related to a problem? Please describe.
I want to dynamically create security group egress rules that exclusively permit access to the CIDR of a VPC endpoint. However, the CIDR of the VPC endpoint is not exposed on the Terraform resource: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc_endpoint#argument-reference
As a result, I end up creating egress rules that just whitelist all traffic in my VPC, simply to allow them to hit the (unknown to Terraform) internal IP of the VPC endpoint.
Describe the solution you'd like.
Just expose the CIDR of the resource, pls :)
Describe alternatives you've considered.
Hardcoding the IP as a variable :(
Additional context
This would probably require modifying the way the associated subnets of the resource are exposed, since an IP is assigned for each subnet the endpoint is deployed in.
The text was updated successfully, but these errors were encountered: