Load
Specifies an Application Load Balancer, a Network Load Balancer, or a Gateway Load Balancer.
Properties
The ID of the Amazon Route 53 hosted zone associated with the load balancer. For example, Z2P70J7EXAMPLE .
Indicates whether to evaluate inbound security group rules for traffic sent to a Network Load Balancer through privatelink.
Note: Internal load balancers must use the `ipv4` IP address type. Application Load Balancers The IP address type. The possible values are `ipv4` (for only IPv4 addresses), `dualstack` (for IPv4 and IPv6 addresses), and `dualstack-without-public-ipv4` (for IPv6 only public addresses, with private IPv4 and IPv6 addresses). Note: Application Load Balancer authentication only supports IPv4 addresses when connecting to an Identity Provider (IdP) or Amazon Cognito endpoint. Without a public IPv4 address the load balancer cannot complete the authentication process, resulting in HTTP 500 errors. Network Load Balancers The IP address type. The possible values are `ipv4` (for only IPv4 addresses) and `dualstack` (for IPv4 and IPv6 addresses). You can’t specify `dualstack` for a load balancer with a UDP or TCP_UDP listener. Gateway Load Balancers The IP address type. The possible values are `ipv4` (for only IPv4 addresses) and `dualstack` (for 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 name of the load balancer. This name must be unique per region per account, can have a maximum of 32 characters, must contain only alphanumeric characters or hyphens, must not begin or end with a hyphen, and must not begin with "internal-". If you don't specify a name, AWS CloudFormation generates a unique physical ID for the load balancer. If you specify a name, you cannot perform updates that require replacement of this resource, but you can perform other updates. To replace the resource, specify a new name.
The nodes of an Internet-facing load balancer have public IP addresses. The DNS name of an Internet-facing load balancer is publicly resolvable to the public IP addresses of the nodes. Therefore, Internet-facing load balancers can route requests from clients over the internet. The nodes of an internal load balancer have only private IP addresses. The DNS name of an internal load balancer is publicly resolvable to the private IP addresses of the nodes. Therefore, internal load balancers can route requests only from clients with access to the VPC for the load balancer. The default is an Internet-facing load balancer. You cannot specify a scheme for a Gateway 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 cannot 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 cannot 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 You can specify subnets from one or more Availability Zones. Gateway Load Balancers You can specify subnets from one or more Availability Zones.