View source: R/elbv2_operations.R
elbv2_create_load_balancer | R Documentation |
Creates an Application Load Balancer, Network Load Balancer, or Gateway Load Balancer.
See https://www.paws-r-sdk.com/docs/elbv2_create_load_balancer/ for full documentation.
elbv2_create_load_balancer(
Name,
Subnets = NULL,
SubnetMappings = NULL,
SecurityGroups = NULL,
Scheme = NULL,
Tags = NULL,
Type = NULL,
IpAddressType = NULL,
CustomerOwnedIpv4Pool = NULL
)
Name |
[required] 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-". |
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. |
SubnetMappings |
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. |
SecurityGroups |
[Application Load Balancers and Network Load Balancers] The IDs of the security groups for the load balancer. |
Scheme |
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. |
Tags |
The tags to assign to the load balancer. |
Type |
The type of load balancer. The default is |
IpAddressType |
Note: Internal load balancers must use the [Application Load Balancers] The IP address type. The possible values
are [Network Load Balancers] The IP address type. The possible values are
[Gateway Load Balancers] The IP address type. The possible values are
|
CustomerOwnedIpv4Pool |
[Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). |
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.