break out s3 endpoint service into tag based calls for interface and … #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…gateway endpoints
Currently, when querying for a list of services to create VPC endpoints for, due to a recent change in AWS, we now get
back in the service name list which causes the
data "aws_vpc_endpoint_service"
data source to fail on finding duplicate items. The duplicate items comes from AWS creating endpoints for the s3 service for both interface and gateway types.This approach requires manually tagging the VPC endpoints to work properly.
The consumers of this module don't require any updates to their interface or the list of services they are passing in. This module will break off the s3 service and handle it separately.
The long term approach is upgrading the AWS terraform provider to > 3.1 and utilizing the
service_type
terraform filter