positional arguments:¶

ELB

name of the new load balancer (required)

optional arguments:¶

-s SUBNET1,SUBNET2,..., --subnets SUBNET1,SUBNET2,...

[VPC only] subnets the load balancer should run in (required)

-z ZONE1,ZONE2,..., --availability-zones ZONE1,ZONE2,...

[Non-VPC only] availability zones the load balancer should run in (required)

-l "lb-port=PORT, protocol={HTTP,HTTPS,SSL,TCP}, instance-port=PORT, instance-protocol={HTTP,HTTPS,SSL,TCP}, cert-id=ARN", --listener "lb-port=PORT, protocol={HTTP,HTTPS,SSL,TCP}, instance-port=PORT, instance-protocol={HTTP,HTTPS,SSL,TCP}, cert-id=ARN"

port/protocol settings for the load balancer, where lb-port is the external port number, protocol is the external protocol, instance-port is the back end server port number, instance-protocol is the protocol to use for routing traffic to back end instances, and cert-id is the ARN of the server certificate to use for encrypted connections. lb-port, protocol, and instance-port are required. This option may be used multiple times. (at least 1 required)

-i internal, --scheme internal

[VPC only] "internal" to make the new load balancer private to a VPC

-g GROUP1,GROUP2,..., --security-groups GROUP1,GROUP2,...

[VPC only] IDs of the security groups to assign to the new load balancer

-t KEY=VALUE, --tag KEY=VALUE

key and value of a tag to add to the new load balancer

--show-empty-fields

show empty values as "(nil)"

-U URL, --url URL

load balancing service endpoint URL

--region USER@REGION

region and/or user names to search when looking up config file data

-I KEY_ID, --access-key-id KEY_ID

-S KEY, --secret-key KEY

--security-token TOKEN

--debug

show debugging output

--debugger

launch interactive debugger on error

--version

show the program's version and exit

-h, --help

show this help message and exit