You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Class: Aws::ElasticLoadBalancingV2::Types::CreateLoadBalancerInput
- Inherits:
-
Struct
- Object
- Struct
- Aws::ElasticLoadBalancingV2::Types::CreateLoadBalancerInput
- Defined in:
- (unknown)
Overview
When passing CreateLoadBalancerInput as input to an Aws::Client method, you can use a vanilla Hash:
{
name: "LoadBalancerName", # required
subnets: ["SubnetId"],
subnet_mappings: [
{
subnet_id: "SubnetId",
allocation_id: "AllocationId",
private_i_pv_4_address: "PrivateIPv4Address",
i_pv_6_address: "IPv6Address",
},
],
security_groups: ["SecurityGroupId"],
scheme: "internet-facing", # accepts internet-facing, internal
tags: [
{
key: "TagKey", # required
value: "TagValue",
},
],
type: "application", # accepts application, network, gateway
ip_address_type: "ipv4", # accepts ipv4, dualstack
customer_owned_ipv_4_pool: "CustomerOwnedIpv4Pool",
}
Instance Attribute Summary collapse
-
#customer_owned_ipv_4_pool ⇒ String
[Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool).
-
#ip_address_type ⇒ String
The type of IP addresses used by the subnets for your load balancer.
-
#name ⇒ String
The name of the load balancer.
-
#scheme ⇒ String
The nodes of an Internet-facing load balancer have public IP addresses.
-
#security_groups ⇒ Array<String>
[Application Load Balancers] The IDs of the security groups for the load balancer.
-
#subnet_mappings ⇒ Array<Types::SubnetMapping>
The IDs of the public subnets.
-
#subnets ⇒ Array<String>
The IDs of the public subnets.
-
#tags ⇒ Array<Types::Tag>
The tags to assign to the load balancer.
-
#type ⇒ String
The type of load balancer.
Instance Attribute Details
#customer_owned_ipv_4_pool ⇒ String
[Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool).
#ip_address_type ⇒ String
The type of IP addresses used by the subnets for your load balancer. The
possible values are ipv4
(for IPv4 addresses) and dualstack
(for
IPv4 and IPv6 addresses). Internal load balancers must use ipv4
.
Possible values:
- ipv4
- dualstack
#name ⇒ String
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-\".
#scheme ⇒ String
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.
Possible values:
- internet-facing
- internal
#security_groups ⇒ Array<String>
[Application Load Balancers] The IDs of the security groups for the load balancer.
#subnet_mappings ⇒ Array<Types::SubnetMapping>
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[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.
#subnets ⇒ Array<String>
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[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.
#tags ⇒ Array<Types::Tag>
The tags to assign to the load balancer.
#type ⇒ String
The type of load balancer. The default is application
.
Possible values:
- application
- network
- gateway