load_balancers

Creates, updates, deletes, gets or lists a load_balancers resource.

Overview

Name	load_balancers
Type	Resource
Id	aws.elb.load_balancers

Fields

The following fields are returned by SELECT queries:

describe_load_balancers

Name	Datatype	Description
availability_zones	string	The Availability Zones for the load balancer.
backend_server_descriptions	string	Information about your EC2 instances.
canonical_hosted_zone_name	string	The DNS name of the load balancer. For more information, see Configure a Custom Domain Name in the Classic Load Balancers Guide.
canonical_hosted_zone_name_id	string	The ID of the Amazon Route 53 hosted zone for the load balancer.
created_time	string	The date and time the load balancer was created.
dns_name	string	The DNS name of the load balancer.
health_check	string	Information about the health checks conducted on the load balancer.
instances	string	The IDs of the instances for the load balancer.
listener_descriptions	string	The listeners for the load balancer.
load_balancer_name	string	The name of the load balancer.
policies	string	The policies defined for the load balancer.
scheme	string	The type of load balancer. Valid only for load balancers in a VPC. If Scheme is internet-facing, the load balancer has a public DNS name that resolves to a public IP address. If Scheme is internal, the load balancer has a public DNS name that resolves to a private IP address.
security_groups	string	The security groups for the load balancer. Valid only for load balancers in a VPC.
source_security_group	string	The security group for the load balancer, which you can use as part of your inbound rules for your registered instances. To only allow traffic from load balancers, add a security group rule that specifies this source security group as the inbound source.
subnets	string	The IDs of the subnets for the load balancer.
vpc_id	string	The ID of the VPC for the load balancer.

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
describe_load_balancers	select	region	LoadBalancerNames, Marker, PageSize	Describes the specified the load balancers. If no load balancers are specified, the call describes all of your load balancers.
create_app_cookie_stickiness_policy	insert	LoadBalancerName, PolicyName, CookieName, region		Generates a stickiness policy with sticky session lifetimes that follow that of an application-generated cookie. This policy can be associated only with HTTP/HTTPS listeners. This policy is similar to the policy created by CreateLBCookieStickinessPolicy, except that the lifetime of the special Elastic Load Balancing cookie, AWSELB, follows the lifetime of the application-generated cookie specified in the policy configuration. The load balancer only inserts a new stickiness cookie when the application response includes a new application cookie. If the application cookie is explicitly removed or expires, the session stops being sticky until a new application cookie is issued. For more information, see Application-Controlled Session Stickiness in the Classic Load Balancers Guide.
create_lb_cookie_stickiness_policy	insert	LoadBalancerName, PolicyName, region	CookieExpirationPeriod	Generates a stickiness policy with sticky session lifetimes controlled by the lifetime of the browser (user-agent) or a specified expiration period. This policy can be associated only with HTTP/HTTPS listeners. When a load balancer implements this policy, the load balancer uses a special cookie to track the instance for each request. When the load balancer receives a request, it first checks to see if this cookie is present in the request. If so, the load balancer sends the request to the application server specified in the cookie. If not, the load balancer sends the request to a server that is chosen based on the existing load-balancing algorithm. A cookie is inserted into the response for binding subsequent requests from the same user to that server. The validity of the cookie is based on the cookie expiration time, which is specified in the policy configuration. For more information, see Duration-Based Session Stickiness in the Classic Load Balancers Guide.
create_load_balancer	insert	LoadBalancerName, Listeners, region	AvailabilityZones, Subnets, SecurityGroups, Scheme, Tags	Creates a Classic Load Balancer. You can add listeners, security groups, subnets, and tags when you create your load balancer, or you can add them later using CreateLoadBalancerListeners, ApplySecurityGroupsToLoadBalancer, AttachLoadBalancerToSubnets, and AddTags. To describe your current load balancers, see DescribeLoadBalancers. When you are finished with a load balancer, you can delete it using DeleteLoadBalancer. You can create up to 20 load balancers per region per account. You can request an increase for the number of load balancers for your account. For more information, see Limits for Your Classic Load Balancer in the Classic Load Balancers Guide.
register_instances_with_load_balancer	insert	LoadBalancerName, region	Instances	Adds the specified instances to the specified load balancer. The instance must be a running instance in the same network as the load balancer (EC2-Classic or the same VPC). If you have EC2-Classic instances and a load balancer in a VPC with ClassicLink enabled, you can link the EC2-Classic instances to that VPC and then register the linked EC2-Classic instances with the load balancer in the VPC. Note that RegisterInstanceWithLoadBalancer completes when the request has been registered. Instance registration takes a little time to complete. To check the state of the registered instances, use DescribeLoadBalancers or DescribeInstanceHealth. After the instance is registered, it starts receiving traffic and requests from the load balancer. Any instance that is not in one of the Availability Zones registered for the load balancer is moved to the OutOfService state. If an Availability Zone is added to the load balancer later, any instances registered with the load balancer move to the InService state. To deregister instances from a load balancer, use DeregisterInstancesFromLoadBalancer. For more information, see Register or De-Register EC2 Instances in the Classic Load Balancers Guide.
set_load_balancer_listener_ssl_certificate	update	LoadBalancerName, LoadBalancerPort, SSLCertificateId, region		Sets the certificate that terminates the specified listener's SSL connections. The specified certificate replaces any prior certificate that was used on the same load balancer and port. For more information about updating your SSL certificate, see Replace the SSL Certificate for Your Load Balancer in the Classic Load Balancers Guide.
attach_load_balancer_to_subnets	update	LoadBalancerName, region	Subnets	Adds one or more subnets to the set of configured subnets for the specified load balancer. The load balancer evenly distributes requests across all registered subnets. For more information, see Add or Remove Subnets for Your Load Balancer in a VPC in the Classic Load Balancers Guide.
delete_load_balancer_listeners	delete	LoadBalancerName, LoadBalancerPorts, region		Deletes the specified listeners from the specified load balancer.
delete_load_balancer	delete	LoadBalancerName, region		Deletes the specified load balancer. If you are attempting to recreate a load balancer, you must reconfigure all settings. The DNS name associated with a deleted load balancer are no longer usable. The name and associated DNS record of the deleted load balancer no longer exist and traffic sent to any of its IP addresses is no longer delivered to your instances. If the load balancer does not exist or has already been deleted, the call to DeleteLoadBalancer still succeeds.
apply_security_groups_to_load_balancer	exec	LoadBalancerName, SecurityGroups, region		Associates one or more security groups with your load balancer in a virtual private cloud (VPC). The specified security groups override the previously associated security groups. For more information, see Security Groups for Load Balancers in a VPC in the Classic Load Balancers Guide.
configure_health_check	exec	LoadBalancerName, HealthCheck, region		Specifies the health check settings to use when evaluating the health state of your EC2 instances. For more information, see Configure Health Checks for Your Load Balancer in the Classic Load Balancers Guide.
create_load_balancer_listeners	exec	LoadBalancerName, Listeners, region		Creates one or more listeners for the specified load balancer. If a listener with the specified port does not already exist, it is created; otherwise, the properties of the new listener must match the properties of the existing listener. For more information, see Listeners for Your Classic Load Balancer in the Classic Load Balancers Guide.
deregister_instances_from_load_balancer	exec	LoadBalancerName, region	Instances	Deregisters the specified instances from the specified load balancer. After the instance is deregistered, it no longer receives traffic from the load balancer. You can use DescribeLoadBalancers to verify that the instance is deregistered from the load balancer. For more information, see Register or De-Register EC2 Instances in the Classic Load Balancers Guide.
detach_load_balancer_from_subnets	exec	LoadBalancerName, region	Subnets	Removes the specified subnets from the set of configured subnets for the load balancer. After a subnet is removed, all EC2 instances registered with the load balancer in the removed subnet go into the OutOfService state. Then, the load balancer balances the traffic among the remaining routable subnets.
disable_availability_zones_for_load_balancer	exec	LoadBalancerName, AvailabilityZones, region		Removes the specified Availability Zones from the set of Availability Zones for the specified load balancer in EC2-Classic or a default VPC. For load balancers in a non-default VPC, use DetachLoadBalancerFromSubnets. There must be at least one Availability Zone registered with a load balancer at all times. After an Availability Zone is removed, all instances registered with the load balancer that are in the removed Availability Zone go into the OutOfService state. Then, the load balancer attempts to equally balance the traffic among its remaining Availability Zones. For more information, see Add or Remove Availability Zones in the Classic Load Balancers Guide.
enable_availability_zones_for_load_balancer	exec	LoadBalancerName, AvailabilityZones, region		Adds the specified Availability Zones to the set of Availability Zones for the specified load balancer in EC2-Classic or a default VPC. For load balancers in a non-default VPC, use AttachLoadBalancerToSubnets. The load balancer evenly distributes requests across all its registered Availability Zones that contain instances. For more information, see Add or Remove Availability Zones in the Classic Load Balancers Guide.

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

Name	Datatype	Description
AvailabilityZones	array	The Availability Zones. These must be in the same region as the load balancer.
CookieName	string	The name of the application cookie used for stickiness.
HealthCheck	object	The configuration information.
Listeners	array	The listeners.
LoadBalancerName	string	The name of the load balancer.
LoadBalancerPort	integer	The port that uses the specified SSL certificate.
LoadBalancerPorts	array	The client port numbers of the listeners.
PolicyName	string	The name of the policy being created. Policy names must consist of alphanumeric characters and dashes (-). This name must be unique within the set of policies for this load balancer.
SSLCertificateId	string	The Amazon Resource Name (ARN) of the SSL certificate.
SecurityGroups	array	The IDs of the security groups to associate with the load balancer. Note that you cannot specify the name of the security group.
region	string	AWS region (default: us-east-1)
AvailabilityZones	array	One or more Availability Zones from the same region as the load balancer. You must specify at least one Availability Zone. You can add more Availability Zones after you create the load balancer using EnableAvailabilityZonesForLoadBalancer.
CookieExpirationPeriod	integer (int64)	The time period, in seconds, after which the cookie should be considered stale. If you do not specify this parameter, the default value is 0, which indicates that the sticky session should last for the duration of the browser session.
Instances	array	The IDs of the instances.
LoadBalancerNames	array	The names of the load balancers.
Marker	string	The marker for the next set of results. (You received this marker from a previous call.)
PageSize	integer	The maximum number of results to return with this call (a number from 1 to 400). The default is 400.
Scheme	string	The type of a load balancer. Valid only for load balancers in a VPC. By default, Elastic Load Balancing creates an Internet-facing load balancer with a DNS name that resolves to public IP addresses. For more information about Internet-facing and Internal load balancers, see Load Balancer Scheme in the Elastic Load Balancing User Guide. Specify internal to create a load balancer with a DNS name that resolves to private IP addresses.
SecurityGroups	array	The IDs of the security groups to assign to the load balancer.
Subnets	array	The IDs of the subnets.
Tags	array	A list of tags to assign to the load balancer. For more information about tagging your load balancer, see Tag Your Classic Load Balancer in the Classic Load Balancers Guide.

SELECT examples

describe_load_balancers

Describes the specified the load balancers. If no load balancers are specified, the call describes all of your load balancers.

SELECT
availability_zones,
backend_server_descriptions,
canonical_hosted_zone_name,
canonical_hosted_zone_name_id,
created_time,
dns_name,
health_check,
instances,
listener_descriptions,
load_balancer_name,
policies,
scheme,
security_groups,
source_security_group,
subnets,
vpc_id
FROM aws.elb.load_balancers
WHERE region = '{{ region }}' -- required
AND LoadBalancerNames = '{{ LoadBalancerNames }}'
AND Marker = '{{ Marker }}'
AND PageSize = '{{ PageSize }}'
;

INSERT examples

create_app_cookie_stickiness_policy

Generates a stickiness policy with sticky session lifetimes that follow that of an application-generated cookie. This policy can be associated only with HTTP/HTTPS listeners. This policy is similar to the policy created by CreateLBCookieStickinessPolicy, except that the lifetime of the special Elastic Load Balancing cookie, AWSELB, follows the lifetime of the application-generated cookie specified in the policy configuration. The load balancer only inserts a new stickiness cookie when the application response includes a new application cookie. If the application cookie is explicitly removed or expires, the session stops being sticky until a new application cookie is issued. For more information, see Application-Controlled Session Stickiness in the Classic Load Balancers Guide.

INSERT INTO aws.elb.load_balancers (
LoadBalancerName,
PolicyName,
CookieName,
region
)
SELECT 
'{{ LoadBalancerName }}',
'{{ PolicyName }}',
'{{ CookieName }}',
'{{ region }}'
RETURNING
line_items
;

create_lb_cookie_stickiness_policy

Generates a stickiness policy with sticky session lifetimes controlled by the lifetime of the browser (user-agent) or a specified expiration period. This policy can be associated only with HTTP/HTTPS listeners. When a load balancer implements this policy, the load balancer uses a special cookie to track the instance for each request. When the load balancer receives a request, it first checks to see if this cookie is present in the request. If so, the load balancer sends the request to the application server specified in the cookie. If not, the load balancer sends the request to a server that is chosen based on the existing load-balancing algorithm. A cookie is inserted into the response for binding subsequent requests from the same user to that server. The validity of the cookie is based on the cookie expiration time, which is specified in the policy configuration. For more information, see Duration-Based Session Stickiness in the Classic Load Balancers Guide.

INSERT INTO aws.elb.load_balancers (
LoadBalancerName,
PolicyName,
region,
CookieExpirationPeriod
)
SELECT 
'{{ LoadBalancerName }}',
'{{ PolicyName }}',
'{{ region }}',
'{{ CookieExpirationPeriod }}'
RETURNING
line_items
;

create_load_balancer

Creates a Classic Load Balancer. You can add listeners, security groups, subnets, and tags when you create your load balancer, or you can add them later using CreateLoadBalancerListeners, ApplySecurityGroupsToLoadBalancer, AttachLoadBalancerToSubnets, and AddTags. To describe your current load balancers, see DescribeLoadBalancers. When you are finished with a load balancer, you can delete it using DeleteLoadBalancer. You can create up to 20 load balancers per region per account. You can request an increase for the number of load balancers for your account. For more information, see Limits for Your Classic Load Balancer in the Classic Load Balancers Guide.

INSERT INTO aws.elb.load_balancers (
LoadBalancerName,
Listeners,
region,
AvailabilityZones,
Subnets,
SecurityGroups,
Scheme,
Tags
)
SELECT 
'{{ LoadBalancerName }}',
'{{ Listeners }}',
'{{ region }}',
'{{ AvailabilityZones }}',
'{{ Subnets }}',
'{{ SecurityGroups }}',
'{{ Scheme }}',
'{{ Tags }}'
RETURNING
dns_name
;

register_instances_with_load_balancer

Adds the specified instances to the specified load balancer. The instance must be a running instance in the same network as the load balancer (EC2-Classic or the same VPC). If you have EC2-Classic instances and a load balancer in a VPC with ClassicLink enabled, you can link the EC2-Classic instances to that VPC and then register the linked EC2-Classic instances with the load balancer in the VPC. Note that RegisterInstanceWithLoadBalancer completes when the request has been registered. Instance registration takes a little time to complete. To check the state of the registered instances, use DescribeLoadBalancers or DescribeInstanceHealth. After the instance is registered, it starts receiving traffic and requests from the load balancer. Any instance that is not in one of the Availability Zones registered for the load balancer is moved to the OutOfService state. If an Availability Zone is added to the load balancer later, any instances registered with the load balancer move to the InService state. To deregister instances from a load balancer, use DeregisterInstancesFromLoadBalancer. For more information, see Register or De-Register EC2 Instances in the Classic Load Balancers Guide.

INSERT INTO aws.elb.load_balancers (
LoadBalancerName,
region,
Instances
)
SELECT 
'{{ LoadBalancerName }}',
'{{ region }}',
'{{ Instances }}'
RETURNING
instances
;

Manifest

# Description fields are for documentation purposes
- name: load_balancers
props:
  - name: LoadBalancerName
    value: "{{ LoadBalancerName }}"
    description: Required parameter for the load_balancers resource.
  - name: PolicyName
    value: "{{ PolicyName }}"
    description: Required parameter for the load_balancers resource.
  - name: CookieName
    value: "{{ CookieName }}"
    description: Required parameter for the load_balancers resource.
  - name: region
    value: "{{ region }}"
    description: Required parameter for the load_balancers resource.
  - name: Listeners
    value: "{{ Listeners }}"
    description: Required parameter for the load_balancers resource.
  - name: CookieExpirationPeriod
    value: "{{ CookieExpirationPeriod }}"
    description: The time period, in seconds, after which the cookie should be considered stale. If you do not specify this parameter, the default value is 0, which indicates that the sticky session should last for the duration of the browser session.
    description: The time period, in seconds, after which the cookie should be considered stale. If you do not specify this parameter, the default value is 0, which indicates that the sticky session should last for the duration of the browser session.
  - name: AvailabilityZones
    value: "{{ AvailabilityZones }}"
    description: One or more Availability Zones from the same region as the load balancer. You must specify at least one Availability Zone. You can add more Availability Zones after you create the load balancer using EnableAvailabilityZonesForLoadBalancer.
    description: One or more Availability Zones from the same region as the load balancer. You must specify at least one Availability Zone. You can add more Availability Zones after you create the load balancer using EnableAvailabilityZonesForLoadBalancer.
  - name: Subnets
    value: "{{ Subnets }}"
    description: The IDs of the subnets in your VPC to attach to the load balancer. Specify one subnet per Availability Zone specified in AvailabilityZones.
    description: The IDs of the subnets in your VPC to attach to the load balancer. Specify one subnet per Availability Zone specified in AvailabilityZones.
  - name: SecurityGroups
    value: "{{ SecurityGroups }}"
    description: The IDs of the security groups to assign to the load balancer.
    description: The IDs of the security groups to assign to the load balancer.
  - name: Scheme
    value: "{{ Scheme }}"
    description: The type of a load balancer. Valid only for load balancers in a VPC. By default, Elastic Load Balancing creates an Internet-facing load balancer with a DNS name that resolves to public IP addresses. For more information about Internet-facing and Internal load balancers, see Load Balancer Scheme in the Elastic Load Balancing User Guide. Specify internal to create a load balancer with a DNS name that resolves to private IP addresses.
    description: The type of a load balancer. Valid only for load balancers in a VPC. By default, Elastic Load Balancing creates an Internet-facing load balancer with a DNS name that resolves to public IP addresses. For more information about Internet-facing and Internal load balancers, see Load Balancer Scheme in the Elastic Load Balancing User Guide. Specify internal to create a load balancer with a DNS name that resolves to private IP addresses.
  - name: Tags
    value: "{{ Tags }}"
    description: A list of tags to assign to the load balancer. For more information about tagging your load balancer, see Tag Your Classic Load Balancer in the Classic Load Balancers Guide.
    description: A list of tags to assign to the load balancer. For more information about tagging your load balancer, see Tag Your Classic Load Balancer in the Classic Load Balancers Guide.
  - name: Instances
    value: "{{ Instances }}"
    description: The IDs of the instances.
    description: The IDs of the instances.

UPDATE examples

set_load_balancer_listener_ssl_certificate

Sets the certificate that terminates the specified listener's SSL connections. The specified certificate replaces any prior certificate that was used on the same load balancer and port. For more information about updating your SSL certificate, see Replace the SSL Certificate for Your Load Balancer in the Classic Load Balancers Guide.

UPDATE aws.elb.load_balancers
SET 
-- No updatable properties
WHERE 
LoadBalancerName = '{{ LoadBalancerName }}' --required
AND LoadBalancerPort = '{{ LoadBalancerPort }}' --required
AND SSLCertificateId = '{{ SSLCertificateId }}' --required
AND region = '{{ region }}' --required
RETURNING
line_items;

attach_load_balancer_to_subnets

Adds one or more subnets to the set of configured subnets for the specified load balancer. The load balancer evenly distributes requests across all registered subnets. For more information, see Add or Remove Subnets for Your Load Balancer in a VPC in the Classic Load Balancers Guide.

UPDATE aws.elb.load_balancers
SET 
-- No updatable properties
WHERE 
LoadBalancerName = '{{ LoadBalancerName }}' --required
AND region = '{{ region }}' --required
AND Subnets = '{{ Subnets}}'
RETURNING
line_items;

DELETE examples

delete_load_balancer_listeners

Deletes the specified listeners from the specified load balancer.

DELETE FROM aws.elb.load_balancers
WHERE LoadBalancerName = '{{ LoadBalancerName }}' --required
AND LoadBalancerPorts = '{{ LoadBalancerPorts }}' --required
AND region = '{{ region }}' --required
;

delete_load_balancer

Deletes the specified load balancer. If you are attempting to recreate a load balancer, you must reconfigure all settings. The DNS name associated with a deleted load balancer are no longer usable. The name and associated DNS record of the deleted load balancer no longer exist and traffic sent to any of its IP addresses is no longer delivered to your instances. If the load balancer does not exist or has already been deleted, the call to DeleteLoadBalancer still succeeds.

DELETE FROM aws.elb.load_balancers
WHERE LoadBalancerName = '{{ LoadBalancerName }}' --required
AND region = '{{ region }}' --required
;

Lifecycle Methods

apply_security_groups_to_load_balancer

Associates one or more security groups with your load balancer in a virtual private cloud (VPC). The specified security groups override the previously associated security groups. For more information, see Security Groups for Load Balancers in a VPC in the Classic Load Balancers Guide.

EXEC aws.elb.load_balancers.apply_security_groups_to_load_balancer 
@LoadBalancerName='{{ LoadBalancerName }}' --required, 
@SecurityGroups='{{ SecurityGroups }}' --required, 
@region='{{ region }}' --required
;

configure_health_check

Specifies the health check settings to use when evaluating the health state of your EC2 instances. For more information, see Configure Health Checks for Your Load Balancer in the Classic Load Balancers Guide.

EXEC aws.elb.load_balancers.configure_health_check 
@LoadBalancerName='{{ LoadBalancerName }}' --required, 
@HealthCheck='{{ HealthCheck }}' --required, 
@region='{{ region }}' --required
;

create_load_balancer_listeners

Creates one or more listeners for the specified load balancer. If a listener with the specified port does not already exist, it is created; otherwise, the properties of the new listener must match the properties of the existing listener. For more information, see Listeners for Your Classic Load Balancer in the Classic Load Balancers Guide.

EXEC aws.elb.load_balancers.create_load_balancer_listeners 
@LoadBalancerName='{{ LoadBalancerName }}' --required, 
@Listeners='{{ Listeners }}' --required, 
@region='{{ region }}' --required
;

deregister_instances_from_load_balancer

Deregisters the specified instances from the specified load balancer. After the instance is deregistered, it no longer receives traffic from the load balancer. You can use DescribeLoadBalancers to verify that the instance is deregistered from the load balancer. For more information, see Register or De-Register EC2 Instances in the Classic Load Balancers Guide.

EXEC aws.elb.load_balancers.deregister_instances_from_load_balancer 
@LoadBalancerName='{{ LoadBalancerName }}' --required, 
@region='{{ region }}' --required, 
@Instances='{{ Instances }}'
;

detach_load_balancer_from_subnets

Removes the specified subnets from the set of configured subnets for the load balancer. After a subnet is removed, all EC2 instances registered with the load balancer in the removed subnet go into the OutOfService state. Then, the load balancer balances the traffic among the remaining routable subnets.

EXEC aws.elb.load_balancers.detach_load_balancer_from_subnets 
@LoadBalancerName='{{ LoadBalancerName }}' --required, 
@region='{{ region }}' --required, 
@Subnets='{{ Subnets }}'
;

disable_availability_zones_for_load_balancer

Removes the specified Availability Zones from the set of Availability Zones for the specified load balancer in EC2-Classic or a default VPC. For load balancers in a non-default VPC, use DetachLoadBalancerFromSubnets. There must be at least one Availability Zone registered with a load balancer at all times. After an Availability Zone is removed, all instances registered with the load balancer that are in the removed Availability Zone go into the OutOfService state. Then, the load balancer attempts to equally balance the traffic among its remaining Availability Zones. For more information, see Add or Remove Availability Zones in the Classic Load Balancers Guide.

EXEC aws.elb.load_balancers.disable_availability_zones_for_load_balancer 
@LoadBalancerName='{{ LoadBalancerName }}' --required, 
@AvailabilityZones='{{ AvailabilityZones }}' --required, 
@region='{{ region }}' --required
;

enable_availability_zones_for_load_balancer

Adds the specified Availability Zones to the set of Availability Zones for the specified load balancer in EC2-Classic or a default VPC. For load balancers in a non-default VPC, use AttachLoadBalancerToSubnets. The load balancer evenly distributes requests across all its registered Availability Zones that contain instances. For more information, see Add or Remove Availability Zones in the Classic Load Balancers Guide.

EXEC aws.elb.load_balancers.enable_availability_zones_for_load_balancer 
@LoadBalancerName='{{ LoadBalancerName }}' --required, 
@AvailabilityZones='{{ AvailabilityZones }}' --required, 
@region='{{ region }}' --required
;