Readonly
accountThe friendly name of the account to deploy the endpoint to.
This is the account
property of the VPC referenced in the vpc
property.
For VPC templates, ensure the account referenced is included in deploymentTargets
.
Readonly
nameThe friendly name of the Gateway Load Balancer endpoint.
CAUTION: Changing this property value after initial deployment causes the endpoint to be recreated. Please be aware that any downstream dependencies may cause this property update to fail.
Readonly
subnetThe friendly name of the subnet to deploy the Gateway Load Balancer endpoint to.
This is the friendly name of the subnet as defined in network-config.yaml.
The subnet must be defined in the subnets
property of the VPC referenced in the vpc
property.
Readonly
vpcThe friendly name of the VPC to deploy the Gateway Load Balancer endpoint to.
CAUTION: Changing this property value after initial deployment causes the endpoint to be recreated. Please be aware that any downstream dependencies may cause this property update to fail.
This is the logical name
property of the VPC as defined in network-config.yaml.
Generated using TypeDoc
NetworkConfig / CentralNetworkServicesConfig / GwlbConfig / GwlbEndpointConfig
Gateway Load Balancer endpoint configuration. Use this configuration to define endpoints for your Gateway Load Balancer. Gateway Load Balancers use Gateway Load Balancer endpoints to securely exchange traffic across VPC boundaries. A Gateway Load Balancer endpoint is a VPC endpoint that provides private connectivity between virtual appliances in the service provider VPC and application servers in the service consumer VPC.
The following example creates two Gateway Load Balancer endpoints,
Endpoint-A
andEndpoint-B
. The endpoints are created in subnets namedNetwork-Inspection-A
andNetwork-Inspection-B
, respectively, in the VPC namedNetwork-Inspection
.Example