vendor: update github.com/aws/aws-sdk-go to get plan9 build fix
This commit is contained in:
Nick Craig-Wood
parent
663e6f3ec0
commit
8b61692754
28 changed files with 4951 additions and 238 deletions
41
vendor/github.com/aws/aws-sdk-go/models/apis/elasticloadbalancing/2012-06-01/api-2.json
generated
vendored
41
vendor/github.com/aws/aws-sdk-go/models/apis/elasticloadbalancing/2012-06-01/api-2.json
generated
vendored
|
|
@ -1,12 +1,12 @@
|
|||
{
|
||||
"version":"2.0",
|
||||
"metadata":{
|
||||
"uid":"elasticloadbalancing-2012-06-01",
|
||||
"apiVersion":"2012-06-01",
|
||||
"endpointPrefix":"elasticloadbalancing",
|
||||
"protocol":"query",
|
||||
"serviceFullName":"Elastic Load Balancing",
|
||||
"signatureVersion":"v4",
|
||||
"uid":"elasticloadbalancing-2012-06-01",
|
||||
"xmlNamespace":"http://elasticloadbalancing.amazonaws.com/doc/2012-06-01/"
|
||||
},
|
||||
"operations":{
|
||||
|
|
@ -235,6 +235,18 @@
|
|||
{"shape":"InvalidEndPointException"}
|
||||
]
|
||||
},
|
||||
"DescribeAccountLimits":{
|
||||
"name":"DescribeAccountLimits",
|
||||
"http":{
|
||||
"method":"POST",
|
||||
"requestUri":"/"
|
||||
},
|
||||
"input":{"shape":"DescribeAccountLimitsInput"},
|
||||
"output":{
|
||||
"shape":"DescribeAccountLimitsOutput",
|
||||
"resultWrapper":"DescribeAccountLimitsResult"
|
||||
}
|
||||
},
|
||||
"DescribeInstanceHealth":{
|
||||
"name":"DescribeInstanceHealth",
|
||||
"http":{
|
||||
|
|
@ -863,6 +875,20 @@
|
|||
"NextMarker":{"shape":"Marker"}
|
||||
}
|
||||
},
|
||||
"DescribeAccountLimitsInput":{
|
||||
"type":"structure",
|
||||
"members":{
|
||||
"Marker":{"shape":"Marker"},
|
||||
"PageSize":{"shape":"PageSize"}
|
||||
}
|
||||
},
|
||||
"DescribeAccountLimitsOutput":{
|
||||
"type":"structure",
|
||||
"members":{
|
||||
"Limits":{"shape":"Limits"},
|
||||
"NextMarker":{"shape":"Marker"}
|
||||
}
|
||||
},
|
||||
"DescribeEndPointStateInput":{
|
||||
"type":"structure",
|
||||
"required":["LoadBalancerName"],
|
||||
|
|
@ -1124,6 +1150,17 @@
|
|||
"CookieExpirationPeriod":{"shape":"CookieExpirationPeriod"}
|
||||
}
|
||||
},
|
||||
"Limit":{
|
||||
"type":"structure",
|
||||
"members":{
|
||||
"Name":{"shape":"Name"},
|
||||
"Max":{"shape":"Max"}
|
||||
}
|
||||
},
|
||||
"Limits":{
|
||||
"type":"list",
|
||||
"member":{"shape":"Limit"}
|
||||
},
|
||||
"Listener":{
|
||||
"type":"structure",
|
||||
"required":[
|
||||
|
|
@ -1223,6 +1260,7 @@
|
|||
},
|
||||
"LoadBalancerScheme":{"type":"string"},
|
||||
"Marker":{"type":"string"},
|
||||
"Max":{"type":"string"},
|
||||
"ModifyLoadBalancerAttributesInput":{
|
||||
"type":"structure",
|
||||
"required":[
|
||||
|
|
@ -1241,6 +1279,7 @@
|
|||
"LoadBalancerAttributes":{"shape":"LoadBalancerAttributes"}
|
||||
}
|
||||
},
|
||||
"Name":{"type":"string"},
|
||||
"PageSize":{
|
||||
"type":"integer",
|
||||
"max":400,
|
||||
|
|
|
|||
102
vendor/github.com/aws/aws-sdk-go/models/apis/elasticloadbalancing/2012-06-01/docs-2.json
generated
vendored
102
vendor/github.com/aws/aws-sdk-go/models/apis/elasticloadbalancing/2012-06-01/docs-2.json
generated
vendored
|
|
@ -1,20 +1,21 @@
|
|||
{
|
||||
"version": "2.0",
|
||||
"service": "<fullname>Elastic Load Balancing</fullname> <p>A load balancer distributes incoming traffic across your EC2 instances. This enables you to increase the availability of your application. The load balancer also monitors the health of its registered instances and ensures that it routes traffic only to healthy instances. You configure your load balancer to accept incoming traffic by specifying one or more listeners, which are configured with a protocol and port number for connections from clients to the load balancer and a protocol and port number for connections from the load balancer to the instances.</p> <p>Elastic Load Balancing supports two types of load balancers: Classic load balancers and Application load balancers (new). A Classic load balancer makes routing and load balancing decisions either at the transport layer (TCP/SSL) or the application layer (HTTP/HTTPS), and supports either EC2-Classic or a VPC. An Application load balancer makes routing and load balancing decisions at the application layer (HTTP/HTTPS), supports path-based routing, and can route requests to one or more ports on each EC2 instance or container instance in your virtual private cloud (VPC). For more information, see the .</p> <p>This reference covers the 2012-06-01 API, which supports Classic load balancers. The 2015-12-01 API supports Application load balancers.</p> <p>To get started, create a load balancer with one or more listeners using <a>CreateLoadBalancer</a>. Register your instances with the load balancer using <a>RegisterInstancesWithLoadBalancer</a>.</p> <p>All Elastic Load Balancing operations are <i>idempotent</i>, which means that they complete at most one time. If you repeat an operation, it succeeds with a 200 OK response code.</p>",
|
||||
"service": "<fullname>Elastic Load Balancing</fullname> <p>A load balancer distributes incoming traffic across your EC2 instances. This enables you to increase the availability of your application. The load balancer also monitors the health of its registered instances and ensures that it routes traffic only to healthy instances. You configure your load balancer to accept incoming traffic by specifying one or more listeners, which are configured with a protocol and port number for connections from clients to the load balancer and a protocol and port number for connections from the load balancer to the instances.</p> <p>Elastic Load Balancing supports two types of load balancers: Classic Load Balancers and Application Load Balancers (new). A Classic Load Balancer makes routing and load balancing decisions either at the transport layer (TCP/SSL) or the application layer (HTTP/HTTPS), and supports either EC2-Classic or a VPC. An Application Load Balancer makes routing and load balancing decisions at the application layer (HTTP/HTTPS), supports path-based routing, and can route requests to one or more ports on each EC2 instance or container instance in your virtual private cloud (VPC). For more information, see the <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/what-is-load-balancing.html\">Elastic Load Balancing User Guide</a>.</p> <p>This reference covers the 2012-06-01 API, which supports Classic Load Balancers. The 2015-12-01 API supports Application Load Balancers.</p> <p>To get started, create a load balancer with one or more listeners using <a>CreateLoadBalancer</a>. Register your instances with the load balancer using <a>RegisterInstancesWithLoadBalancer</a>.</p> <p>All Elastic Load Balancing operations are <i>idempotent</i>, which means that they complete at most one time. If you repeat an operation, it succeeds with a 200 OK response code.</p>",
|
||||
"operations": {
|
||||
"AddTags": "<p>Adds the specified tags to the specified load balancer. Each load balancer can have a maximum of 10 tags.</p> <p>Each tag consists of a key and an optional value. If a tag with the same key is already associated with the load balancer, <code>AddTags</code> updates its value.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/add-remove-tags.html\">Tag Your Classic Load Balancer</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"ApplySecurityGroupsToLoadBalancer": "<p>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.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-security-groups.html#elb-vpc-security-groups\">Security Groups for Load Balancers in a VPC</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"AttachLoadBalancerToSubnets": "<p>Adds one or more subnets to the set of configured subnets for the specified load balancer.</p> <p>The load balancer evenly distributes requests across all registered subnets. For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-manage-subnets.html\">Add or Remove Subnets for Your Load Balancer in a VPC</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"ConfigureHealthCheck": "<p>Specifies the health check settings to use when evaluating the health state of your EC2 instances.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-healthchecks.html\">Configure Health Checks for Your Load Balancer</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"CreateAppCookieStickinessPolicy": "<p>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.</p> <p>This policy is similar to the policy created by <a>CreateLBCookieStickinessPolicy</a>, except that the lifetime of the special Elastic Load Balancing cookie, <code>AWSELB</code>, 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.</p> <p>If the application cookie is explicitly removed or expires, the session stops being sticky until a new application cookie is issued.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html#enable-sticky-sessions-application\">Application-Controlled Session Stickiness</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"CreateLBCookieStickinessPolicy": "<p>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.</p> <p>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.</p> <p>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.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html#enable-sticky-sessions-duration\">Duration-Based Session Stickiness</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"CreateLoadBalancer": "<p>Creates a Classic load balancer.</p> <p>You can add listeners, security groups, subnets, and tags when you create your load balancer, or you can add them later using <a>CreateLoadBalancerListeners</a>, <a>ApplySecurityGroupsToLoadBalancer</a>, <a>AttachLoadBalancerToSubnets</a>, and <a>AddTags</a>.</p> <p>To describe your current load balancers, see <a>DescribeLoadBalancers</a>. When you are finished with a load balancer, you can delete it using <a>DeleteLoadBalancer</a>.</p> <p>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 <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-limits.html\">Limits for Your Classic Load Balancer</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"CreateLoadBalancerListeners": "<p>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.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-listener-config.html\">Listeners for Your Classic Load Balancer</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"AddTags": "<p>Adds the specified tags to the specified load balancer. Each load balancer can have a maximum of 10 tags.</p> <p>Each tag consists of a key and an optional value. If a tag with the same key is already associated with the load balancer, <code>AddTags</code> updates its value.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/add-remove-tags.html\">Tag Your Classic Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"ApplySecurityGroupsToLoadBalancer": "<p>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.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-security-groups.html#elb-vpc-security-groups\">Security Groups for Load Balancers in a VPC</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"AttachLoadBalancerToSubnets": "<p>Adds one or more subnets to the set of configured subnets for the specified load balancer.</p> <p>The load balancer evenly distributes requests across all registered subnets. For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-manage-subnets.html\">Add or Remove Subnets for Your Load Balancer in a VPC</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"ConfigureHealthCheck": "<p>Specifies the health check settings to use when evaluating the health state of your EC2 instances.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-healthchecks.html\">Configure Health Checks for Your Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"CreateAppCookieStickinessPolicy": "<p>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.</p> <p>This policy is similar to the policy created by <a>CreateLBCookieStickinessPolicy</a>, except that the lifetime of the special Elastic Load Balancing cookie, <code>AWSELB</code>, 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.</p> <p>If the application cookie is explicitly removed or expires, the session stops being sticky until a new application cookie is issued.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html#enable-sticky-sessions-application\">Application-Controlled Session Stickiness</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"CreateLBCookieStickinessPolicy": "<p>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.</p> <p>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.</p> <p>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.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html#enable-sticky-sessions-duration\">Duration-Based Session Stickiness</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"CreateLoadBalancer": "<p>Creates a Classic Load Balancer.</p> <p>You can add listeners, security groups, subnets, and tags when you create your load balancer, or you can add them later using <a>CreateLoadBalancerListeners</a>, <a>ApplySecurityGroupsToLoadBalancer</a>, <a>AttachLoadBalancerToSubnets</a>, and <a>AddTags</a>.</p> <p>To describe your current load balancers, see <a>DescribeLoadBalancers</a>. When you are finished with a load balancer, you can delete it using <a>DeleteLoadBalancer</a>.</p> <p>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 <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-limits.html\">Limits for Your Classic Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"CreateLoadBalancerListeners": "<p>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.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-listener-config.html\">Listeners for Your Classic Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"CreateLoadBalancerPolicy": "<p>Creates a policy with the specified attributes for the specified load balancer.</p> <p>Policies are settings that are saved for your load balancer and that can be applied to the listener or the application server, depending on the policy type.</p>",
|
||||
"DeleteLoadBalancer": "<p>Deletes the specified load balancer.</p> <p>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.</p> <p>If the load balancer does not exist or has already been deleted, the call to <code>DeleteLoadBalancer</code> still succeeds.</p>",
|
||||
"DeleteLoadBalancerListeners": "<p>Deletes the specified listeners from the specified load balancer.</p>",
|
||||
"DeleteLoadBalancerPolicy": "<p>Deletes the specified policy from the specified load balancer. This policy must not be enabled for any listeners.</p>",
|
||||
"DeregisterInstancesFromLoadBalancer": "<p>Deregisters the specified instances from the specified load balancer. After the instance is deregistered, it no longer receives traffic from the load balancer.</p> <p>You can use <a>DescribeLoadBalancers</a> to verify that the instance is deregistered from the load balancer.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-deregister-register-instances.html\">Register or De-Register EC2 Instances</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"DeregisterInstancesFromLoadBalancer": "<p>Deregisters the specified instances from the specified load balancer. After the instance is deregistered, it no longer receives traffic from the load balancer.</p> <p>You can use <a>DescribeLoadBalancers</a> to verify that the instance is deregistered from the load balancer.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-deregister-register-instances.html\">Register or De-Register EC2 Instances</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"DescribeAccountLimits": "<p>Describes the current Elastic Load Balancing resource limits for your AWS account.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-limits.html\">Limits for Your Classic Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"DescribeInstanceHealth": "<p>Describes the state of the specified instances with respect to the specified load balancer. If no instances are specified, the call describes the state of all instances that are currently registered with the load balancer. If instances are specified, their state is returned even if they are no longer registered with the load balancer. The state of terminated instances is not returned.</p>",
|
||||
"DescribeLoadBalancerAttributes": "<p>Describes the attributes for the specified load balancer.</p>",
|
||||
"DescribeLoadBalancerPolicies": "<p>Describes the specified policies.</p> <p>If you specify a load balancer name, the action returns the descriptions of all policies created for the load balancer. If you specify a policy name associated with your load balancer, the action returns the description of that policy. If you don't specify a load balancer name, the action returns descriptions of the specified sample policies, or descriptions of all sample policies. The names of the sample policies have the <code>ELBSample-</code> prefix.</p>",
|
||||
|
|
@ -22,20 +23,20 @@
|
|||
"DescribeLoadBalancers": "<p>Describes the specified the load balancers. If no load balancers are specified, the call describes all of your load balancers.</p>",
|
||||
"DescribeTags": "<p>Describes the tags associated with the specified load balancers.</p>",
|
||||
"DetachLoadBalancerFromSubnets": "<p>Removes the specified subnets from the set of configured subnets for the load balancer.</p> <p>After a subnet is removed, all EC2 instances registered with the load balancer in the removed subnet go into the <code>OutOfService</code> state. Then, the load balancer balances the traffic among the remaining routable subnets.</p>",
|
||||
"DisableAvailabilityZonesForLoadBalancer": "<p>Removes the specified Availability Zones from the set of Availability Zones for the specified load balancer.</p> <p>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 <code>OutOfService</code> state. Then, the load balancer attempts to equally balance the traffic among its remaining Availability Zones.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-az.html\">Add or Remove Availability Zones</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"EnableAvailabilityZonesForLoadBalancer": "<p>Adds the specified Availability Zones to the set of Availability Zones for the specified load balancer.</p> <p>The load balancer evenly distributes requests across all its registered Availability Zones that contain instances.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-az.html\">Add or Remove Availability Zones</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"ModifyLoadBalancerAttributes": "<p>Modifies the attributes of the specified load balancer.</p> <p>You can modify the load balancer attributes, such as <code>AccessLogs</code>, <code>ConnectionDraining</code>, and <code>CrossZoneLoadBalancing</code> by either enabling or disabling them. Or, you can modify the load balancer attribute <code>ConnectionSettings</code> by specifying an idle connection timeout value for your load balancer.</p> <p>For more information, see the following in the <i>Classic Load Balancers Guide</i>:</p> <ul> <li> <p> <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-crosszone-lb.html\">Cross-Zone Load Balancing</a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-conn-drain.html\">Connection Draining</a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/access-log-collection.html\">Access Logs</a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-idle-timeout.html\">Idle Connection Timeout</a> </p> </li> </ul>",
|
||||
"RegisterInstancesWithLoadBalancer": "<p>Adds the specified instances to the specified load balancer.</p> <p>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.</p> <p>Note that <code>RegisterInstanceWithLoadBalancer</code> completes when the request has been registered. Instance registration takes a little time to complete. To check the state of the registered instances, use <a>DescribeLoadBalancers</a> or <a>DescribeInstanceHealth</a>.</p> <p>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 <code>OutOfService</code> state. If an Availability Zone is added to the load balancer later, any instances registered with the load balancer move to the <code>InService</code> state.</p> <p>To deregister instances from a load balancer, use <a>DeregisterInstancesFromLoadBalancer</a>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-deregister-register-instances.html\">Register or De-Register EC2 Instances</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"DisableAvailabilityZonesForLoadBalancer": "<p>Removes the specified Availability Zones from the set of Availability Zones for the specified load balancer.</p> <p>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 <code>OutOfService</code> state. Then, the load balancer attempts to equally balance the traffic among its remaining Availability Zones.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-az.html\">Add or Remove Availability Zones</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"EnableAvailabilityZonesForLoadBalancer": "<p>Adds the specified Availability Zones to the set of Availability Zones for the specified load balancer.</p> <p>The load balancer evenly distributes requests across all its registered Availability Zones that contain instances.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-az.html\">Add or Remove Availability Zones</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"ModifyLoadBalancerAttributes": "<p>Modifies the attributes of the specified load balancer.</p> <p>You can modify the load balancer attributes, such as <code>AccessLogs</code>, <code>ConnectionDraining</code>, and <code>CrossZoneLoadBalancing</code> by either enabling or disabling them. Or, you can modify the load balancer attribute <code>ConnectionSettings</code> by specifying an idle connection timeout value for your load balancer.</p> <p>For more information, see the following in the <i>Classic Load Balancer Guide</i>:</p> <ul> <li> <p> <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-crosszone-lb.html\">Cross-Zone Load Balancing</a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-conn-drain.html\">Connection Draining</a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/access-log-collection.html\">Access Logs</a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-idle-timeout.html\">Idle Connection Timeout</a> </p> </li> </ul>",
|
||||
"RegisterInstancesWithLoadBalancer": "<p>Adds the specified instances to the specified load balancer.</p> <p>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.</p> <p>Note that <code>RegisterInstanceWithLoadBalancer</code> completes when the request has been registered. Instance registration takes a little time to complete. To check the state of the registered instances, use <a>DescribeLoadBalancers</a> or <a>DescribeInstanceHealth</a>.</p> <p>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 <code>OutOfService</code> state. If an Availability Zone is added to the load balancer later, any instances registered with the load balancer move to the <code>InService</code> state.</p> <p>To deregister instances from a load balancer, use <a>DeregisterInstancesFromLoadBalancer</a>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-deregister-register-instances.html\">Register or De-Register EC2 Instances</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"RemoveTags": "<p>Removes one or more tags from the specified load balancer.</p>",
|
||||
"SetLoadBalancerListenerSSLCertificate": "<p>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.</p> <p>For more information about updating your SSL certificate, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-update-ssl-cert.html\">Replace the SSL Certificate for Your Load Balancer</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"SetLoadBalancerPoliciesForBackendServer": "<p>Replaces the set of policies associated with the specified port on which the EC2 instance is listening with a new set of policies. At this time, only the back-end server authentication policy type can be applied to the instance ports; this policy type is composed of multiple public key policies.</p> <p>Each time you use <code>SetLoadBalancerPoliciesForBackendServer</code> to enable the policies, use the <code>PolicyNames</code> parameter to list the policies that you want to enable.</p> <p>You can use <a>DescribeLoadBalancers</a> or <a>DescribeLoadBalancerPolicies</a> to verify that the policy is associated with the EC2 instance.</p> <p>For more information about enabling back-end instance authentication, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-create-https-ssl-load-balancer.html#configure_backendauth_clt\">Configure Back-end Instance Authentication</a> in the <i>Classic Load Balancers Guide</i>. For more information about Proxy Protocol, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-proxy-protocol.html\">Configure Proxy Protocol Support</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"SetLoadBalancerPoliciesOfListener": "<p>Replaces the current set of policies for the specified load balancer port with the specified set of policies.</p> <p>To enable back-end server authentication, use <a>SetLoadBalancerPoliciesForBackendServer</a>.</p> <p>For more information about setting policies, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/ssl-config-update.html\">Update the SSL Negotiation Configuration</a>, <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html#enable-sticky-sessions-duration\">Duration-Based Session Stickiness</a>, and <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html#enable-sticky-sessions-application\">Application-Controlled Session Stickiness</a> in the <i>Classic Load Balancers Guide</i>.</p>"
|
||||
"SetLoadBalancerListenerSSLCertificate": "<p>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.</p> <p>For more information about updating your SSL certificate, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-update-ssl-cert.html\">Replace the SSL Certificate for Your Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"SetLoadBalancerPoliciesForBackendServer": "<p>Replaces the set of policies associated with the specified port on which the EC2 instance is listening with a new set of policies. At this time, only the back-end server authentication policy type can be applied to the instance ports; this policy type is composed of multiple public key policies.</p> <p>Each time you use <code>SetLoadBalancerPoliciesForBackendServer</code> to enable the policies, use the <code>PolicyNames</code> parameter to list the policies that you want to enable.</p> <p>You can use <a>DescribeLoadBalancers</a> or <a>DescribeLoadBalancerPolicies</a> to verify that the policy is associated with the EC2 instance.</p> <p>For more information about enabling back-end instance authentication, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-create-https-ssl-load-balancer.html#configure_backendauth_clt\">Configure Back-end Instance Authentication</a> in the <i>Classic Load Balancer Guide</i>. For more information about Proxy Protocol, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-proxy-protocol.html\">Configure Proxy Protocol Support</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"SetLoadBalancerPoliciesOfListener": "<p>Replaces the current set of policies for the specified load balancer port with the specified set of policies.</p> <p>To enable back-end server authentication, use <a>SetLoadBalancerPoliciesForBackendServer</a>.</p> <p>For more information about setting policies, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/ssl-config-update.html\">Update the SSL Negotiation Configuration</a>, <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html#enable-sticky-sessions-duration\">Duration-Based Session Stickiness</a>, and <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html#enable-sticky-sessions-application\">Application-Controlled Session Stickiness</a> in the <i>Classic Load Balancer Guide</i>.</p>"
|
||||
},
|
||||
"shapes": {
|
||||
"AccessLog": {
|
||||
"base": "<p>Information about the <code>AccessLog</code> attribute.</p>",
|
||||
"refs": {
|
||||
"LoadBalancerAttributes$AccessLog": "<p>If enabled, the load balancer captures detailed information of all requests and delivers the information to the Amazon S3 bucket that you specify.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-access-logs.html\">Enable Access Logs</a> in the <i>Classic Load Balancers Guide</i>.</p>"
|
||||
"LoadBalancerAttributes$AccessLog": "<p>If enabled, the load balancer captures detailed information of all requests and delivers the information to the Amazon S3 bucket that you specify.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-access-logs.html\">Enable Access Logs</a> in the <i>Classic Load Balancer Guide</i>.</p>"
|
||||
}
|
||||
},
|
||||
"AccessLogEnabled": {
|
||||
|
|
@ -253,7 +254,7 @@
|
|||
"ConnectionDraining": {
|
||||
"base": "<p>Information about the <code>ConnectionDraining</code> attribute.</p>",
|
||||
"refs": {
|
||||
"LoadBalancerAttributes$ConnectionDraining": "<p>If enabled, the load balancer allows existing requests to complete before the load balancer shifts traffic away from a deregistered or unhealthy instance.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-conn-drain.html\">Configure Connection Draining</a> in the <i>Classic Load Balancers Guide</i>.</p>"
|
||||
"LoadBalancerAttributes$ConnectionDraining": "<p>If enabled, the load balancer allows existing requests to complete before the load balancer shifts traffic away from a deregistered or unhealthy instance.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-conn-drain.html\">Configure Connection Draining</a> in the <i>Classic Load Balancer Guide</i>.</p>"
|
||||
}
|
||||
},
|
||||
"ConnectionDrainingEnabled": {
|
||||
|
|
@ -271,7 +272,7 @@
|
|||
"ConnectionSettings": {
|
||||
"base": "<p>Information about the <code>ConnectionSettings</code> attribute.</p>",
|
||||
"refs": {
|
||||
"LoadBalancerAttributes$ConnectionSettings": "<p>If enabled, the load balancer allows the connections to remain idle (no data is sent over the connection) for the specified duration.</p> <p>By default, Elastic Load Balancing maintains a 60-second idle connection timeout for both front-end and back-end connections of your load balancer. For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-idle-timeout.html\">Configure Idle Connection Timeout</a> in the <i>Classic Load Balancers Guide</i>.</p>"
|
||||
"LoadBalancerAttributes$ConnectionSettings": "<p>If enabled, the load balancer allows the connections to remain idle (no data is sent over the connection) for the specified duration.</p> <p>By default, Elastic Load Balancing maintains a 60-second idle connection timeout for both front-end and back-end connections of your load balancer. For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-idle-timeout.html\">Configure Idle Connection Timeout</a> in the <i>Classic Load Balancer Guide</i>.</p>"
|
||||
}
|
||||
},
|
||||
"CookieExpirationPeriod": {
|
||||
|
|
@ -347,7 +348,7 @@
|
|||
"CrossZoneLoadBalancing": {
|
||||
"base": "<p>Information about the <code>CrossZoneLoadBalancing</code> attribute.</p>",
|
||||
"refs": {
|
||||
"LoadBalancerAttributes$CrossZoneLoadBalancing": "<p>If enabled, the load balancer routes the request traffic evenly across all instances regardless of the Availability Zones.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-crosszone-lb.html\">Configure Cross-Zone Load Balancing</a> in the <i>Classic Load Balancers Guide</i>.</p>"
|
||||
"LoadBalancerAttributes$CrossZoneLoadBalancing": "<p>If enabled, the load balancer routes the request traffic evenly across all instances regardless of the Availability Zones.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-crosszone-lb.html\">Configure Cross-Zone Load Balancing</a> in the <i>Classic Load Balancer Guide</i>.</p>"
|
||||
}
|
||||
},
|
||||
"CrossZoneLoadBalancingEnabled": {
|
||||
|
|
@ -361,7 +362,7 @@
|
|||
"refs": {
|
||||
"CreateAccessPointOutput$DNSName": "<p>The DNS name of the load balancer.</p>",
|
||||
"LoadBalancerDescription$DNSName": "<p>The DNS name of the load balancer.</p>",
|
||||
"LoadBalancerDescription$CanonicalHostedZoneName": "<p>The DNS name of the load balancer.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/using-domain-names-with-elb.html\">Configure a Custom Domain Name</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"LoadBalancerDescription$CanonicalHostedZoneName": "<p>The DNS name of the load balancer.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/using-domain-names-with-elb.html\">Configure a Custom Domain Name</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"LoadBalancerDescription$CanonicalHostedZoneNameID": "<p>The ID of the Amazon Route 53 hosted zone for the load balancer.</p>"
|
||||
}
|
||||
},
|
||||
|
|
@ -426,6 +427,16 @@
|
|||
"refs": {
|
||||
}
|
||||
},
|
||||
"DescribeAccountLimitsInput": {
|
||||
"base": null,
|
||||
"refs": {
|
||||
}
|
||||
},
|
||||
"DescribeAccountLimitsOutput": {
|
||||
"base": null,
|
||||
"refs": {
|
||||
}
|
||||
},
|
||||
"DescribeEndPointStateInput": {
|
||||
"base": "<p>Contains the parameters for DescribeInstanceHealth.</p>",
|
||||
"refs": {
|
||||
|
|
@ -638,10 +649,22 @@
|
|||
"LBCookieStickinessPolicies$member": null
|
||||
}
|
||||
},
|
||||
"Listener": {
|
||||
"base": "<p>Information about a listener.</p> <p>For information about the protocols and the ports supported by Elastic Load Balancing, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-listener-config.html\">Listeners for Your Classic Load Balancer</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"Limit": {
|
||||
"base": "<p>Information about an Elastic Load Balancing resource limit for your AWS account.</p>",
|
||||
"refs": {
|
||||
"ListenerDescription$Listener": null,
|
||||
"Limits$member": null
|
||||
}
|
||||
},
|
||||
"Limits": {
|
||||
"base": null,
|
||||
"refs": {
|
||||
"DescribeAccountLimitsOutput$Limits": "<p>Information about the limits.</p>"
|
||||
}
|
||||
},
|
||||
"Listener": {
|
||||
"base": "<p>Information about a listener.</p> <p>For information about the protocols and the ports supported by Elastic Load Balancing, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-listener-config.html\">Listeners for Your Classic Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"refs": {
|
||||
"ListenerDescription$Listener": "<p>The listener.</p>",
|
||||
"Listeners$member": null
|
||||
}
|
||||
},
|
||||
|
|
@ -665,7 +688,7 @@
|
|||
"Listeners": {
|
||||
"base": null,
|
||||
"refs": {
|
||||
"CreateAccessPointInput$Listeners": "<p>The listeners.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-listener-config.html\">Listeners for Your Classic Load Balancer</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"CreateAccessPointInput$Listeners": "<p>The listeners.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-listener-config.html\">Listeners for Your Classic Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"CreateLoadBalancerListenerInput$Listeners": "<p>The listeners.</p>"
|
||||
}
|
||||
},
|
||||
|
|
@ -678,8 +701,8 @@
|
|||
"base": "<p>The attributes for a load balancer.</p>",
|
||||
"refs": {
|
||||
"DescribeLoadBalancerAttributesOutput$LoadBalancerAttributes": "<p>Information about the load balancer attributes.</p>",
|
||||
"ModifyLoadBalancerAttributesInput$LoadBalancerAttributes": "<p>The attributes of the load balancer.</p>",
|
||||
"ModifyLoadBalancerAttributesOutput$LoadBalancerAttributes": null
|
||||
"ModifyLoadBalancerAttributesInput$LoadBalancerAttributes": "<p>The attributes for the load balancer.</p>",
|
||||
"ModifyLoadBalancerAttributesOutput$LoadBalancerAttributes": "<p>Information about the load balancer attributes.</p>"
|
||||
}
|
||||
},
|
||||
"LoadBalancerDescription": {
|
||||
|
|
@ -719,7 +742,15 @@
|
|||
"base": null,
|
||||
"refs": {
|
||||
"DescribeAccessPointsInput$Marker": "<p>The marker for the next set of results. (You received this marker from a previous call.)</p>",
|
||||
"DescribeAccessPointsOutput$NextMarker": "<p>The marker to use when requesting the next set of results. If there are no additional results, the string is empty.</p>"
|
||||
"DescribeAccessPointsOutput$NextMarker": "<p>The marker to use when requesting the next set of results. If there are no additional results, the string is empty.</p>",
|
||||
"DescribeAccountLimitsInput$Marker": "<p>The marker for the next set of results. (You received this marker from a previous call.)</p>",
|
||||
"DescribeAccountLimitsOutput$NextMarker": "<p>The marker to use when requesting the next set of results. If there are no additional results, the string is empty.</p>"
|
||||
}
|
||||
},
|
||||
"Max": {
|
||||
"base": null,
|
||||
"refs": {
|
||||
"Limit$Max": "<p>The maximum value of the limit.</p>"
|
||||
}
|
||||
},
|
||||
"ModifyLoadBalancerAttributesInput": {
|
||||
|
|
@ -732,10 +763,17 @@
|
|||
"refs": {
|
||||
}
|
||||
},
|
||||
"Name": {
|
||||
"base": null,
|
||||
"refs": {
|
||||
"Limit$Name": "<p>The name of the limit. The possible values are:</p> <ul> <li> <p>classic-listeners</p> </li> <li> <p>classic-load-balancers</p> </li> </ul>"
|
||||
}
|
||||
},
|
||||
"PageSize": {
|
||||
"base": null,
|
||||
"refs": {
|
||||
"DescribeAccessPointsInput$PageSize": "<p>The maximum number of results to return with this call (a number from 1 to 400). The default is 400.</p>"
|
||||
"DescribeAccessPointsInput$PageSize": "<p>The maximum number of results to return with this call (a number from 1 to 400). The default is 400.</p>",
|
||||
"DescribeAccountLimitsInput$PageSize": "<p>The maximum number of results to return with this call.</p>"
|
||||
}
|
||||
},
|
||||
"Policies": {
|
||||
|
|
@ -1047,7 +1085,7 @@
|
|||
"base": null,
|
||||
"refs": {
|
||||
"AddTagsInput$Tags": "<p>The tags.</p>",
|
||||
"CreateAccessPointInput$Tags": "<p>A list of tags to assign to the load balancer.</p> <p>For more information about tagging your load balancer, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/add-remove-tags.html\">Tag Your Classic Load Balancer</a> in the <i>Classic Load Balancers Guide</i>.</p>",
|
||||
"CreateAccessPointInput$Tags": "<p>A list of tags to assign to the load balancer.</p> <p>For more information about tagging your load balancer, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/add-remove-tags.html\">Tag Your Classic Load Balancer</a> in the <i>Classic Load Balancer Guide</i>.</p>",
|
||||
"TagDescription$Tags": "<p>The tags.</p>"
|
||||
}
|
||||
},
|
||||
|
|
@ -1079,7 +1117,7 @@
|
|||
}
|
||||
},
|
||||
"UnsupportedProtocolException": {
|
||||
"base": null,
|
||||
"base": "<p>The specified protocol or signature version is not supported.</p>",
|
||||
"refs": {
|
||||
}
|
||||
},
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@
|
|||
"result_key": "LoadBalancerDescriptions"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
Loading…
Add table
Add a link
Reference in a new issue