Get Load Balancer Result
Constructors
Properties
The ID of the Amazon Route 53 hosted zone associated with the load balancer. For example, Z2P70J7EXAMPLE
.
Network Load Balancers with UDP listeners Indicates whether to use an IPv6 prefix from each subnet for source NAT. The IP address type must be `dualstack`
. The default value is `off`
.
Indicates whether to evaluate inbound security group rules for traffic sent to a Network Load Balancer through privatelink. The default is `on`
.
The IP address type. Internal load balancers must use `ipv4`
. Application Load Balancers The possible values are `ipv4`
(IPv4 addresses), `dualstack`
(IPv4 and IPv6 addresses), and `dualstack-without-public-ipv4`
(public IPv6 addresses and private IPv4 and IPv6 addresses). Application Load Balancer authentication supports IPv4 addresses only when connecting to an Identity Provider (IdP) or Amazon Cognito endpoint. Without a public IPv4 address the load balancer can't complete the authentication process, resulting in HTTP 500 errors. Network Load Balancers and Gateway Load Balancers The possible values are `ipv4`
(IPv4 addresses) and `dualstack`
(IPv4 and IPv6 addresses).
The Amazon Resource Name (ARN) of the load balancer.
The load balancer attributes.
The full name of the load balancer. For example, app/my-load-balancer/50dc6c495c0c9188
.
The name of the load balancer. For example, my-load-balancer
.
The minimum capacity for a load balancer.
Application Load Balancers and Network Load Balancers The IDs of the security groups for the load balancer.
The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both. Application Load Balancers You must specify subnets from at least two Availability Zones. You can't specify Elastic IP addresses for your subnets. Application Load Balancers on Outposts You must specify one Outpost subnet. Application Load Balancers on Local Zones You can specify subnets from one or more Local Zones. Network Load Balancers You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. For internet-facing load balancer, you can specify one IPv6 address per subnet. Gateway Load Balancers You can specify subnets from one or more Availability Zones. You can't specify Elastic IP addresses for your subnets.
The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both. To specify an Elastic IP address, specify subnet mappings instead of subnets. Application Load Balancers You must specify subnets from at least two Availability Zones. Application Load Balancers on Outposts You must specify one Outpost subnet. Application Load Balancers on Local Zones You can specify subnets from one or more Local Zones. Network Load Balancers and Gateway Load Balancers You can specify subnets from one or more Availability Zones.