AWS GWLB Endpoint Set
This module creates a set of VPC GWLB Endpoints over a range of one or more Availability Zones. All the Endpoints transfer the traffic to the same Gateway Load Balancer (GWLB).
|terraform||>= 1.0.0, < 2.0.0|
|act_as_next_hop_for||The map of edge routes to create to pass network traffic to this Endpoint Set.|
This input is not intended for typical routes - use instead the
This input only handles routes which have subnet CIDRs destination (AZ-specific), usually the ingress traffic coming from an Internet Gateway.
AWS docs call this special kind of route the "edge route".
The keys of the map are arbitrary strings. Example:
In this example, traffic from IGW destined to the ALB is instead routed to the GWLBE (for inspection by an appliance).
|custom_names||Optional map of readable names of the VPC Endpoints, used to override the default naming generated from the input ||no|
|gwlb_service_name||The name of the VPC Endpoint Service to connect to, which may reside in a different VPC. Usually an output ||n/a||yes|
|gwlb_service_type||The type of the Endpoint to create for ||no|
|name||Name of the VPC Endpoint Set, for example: "my-gwlbe-". Each individual endpoint is named by appending an AZ letter, such as "my-set-a" and "my-set-b". These names can be overriden using ||no|
|subnets||Map of Subnets where to create the Endpoints. Each map's key is the availability zone name and each map's object has an attribute|
The keys of this input map are used for the output map
Example for users of module
|tags||AWS Tags for the VPC Endpoints.||no|
|vpc_id||AWS identifier of a VPC containing the Endpoint.||n/a||yes|
|endpoints||Map of the created endpoints. The keys are the same as the keys of the input |
|next_hop_set||The Next Hop Set object, useful as an input to the |
be to route traffic from subnets to endpoints while preventing cross-AZ traffic (so
that a subnet in AZ-a only routes to an endpoint in AZ-a). Example: