tag support in vpc_endpoint datasource

[kimor79]

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 "me too" comments, 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

The current vpc_endpoint datasource only accepts an id, service name, state, or VPC id. If there are multiple endpoints for the same service (ie with different policies), this resource can't be used to select the desired one. Nor can it work properly when there are multiple endpoints for the same service: multiple VPC Endpoints matched; use additional constraints to reduce matches to a single VPC Endpoint

It would be nice if we could pass tags to filter on to identify which endpoint we want.

New or Affected Resource(s)

• aws_vpc_endpoint datasource

Potential Terraform Configuration

data "aws_vpc_endpoint" "bar" {
  service_name = "com.amazonaws.${data.aws_region.current.name}.execute-api"
  tags {
    Name = "bar"
  }
}

data "aws_vpc_endpoint" "foo" {
  service_name = "com.amazonaws.${data.aws_region.current.name}.execute-api"
  tags {
    Name = "foo"
  }
}

References

[ewbankkit]

When the initial support for VPC Endpoint tagging was implemented I don't think the DescribeVpcEndpoints API method supported tag filters.
It looks like tag filters are now supported.
I can implement.

[bflad]

Support for filtering by filter and tags arguments has been merged and will release with version 2.35.0 of the Terraform AWS Provider, Thursday next week. Thanks to @ewbankkit for the implementation. 👍

[ghost]

This has been released in version 2.35.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!