vendor: update all dependencies to latest versions

This commit is contained in:
Nick Craig-Wood 2017-09-30 15:27:27 +01:00
parent 911d121bb9
commit b017fcfe9a
3048 changed files with 537057 additions and 189681 deletions

View file

@ -52,7 +52,8 @@
{"shape":"SSLPolicyNotFoundException"},
{"shape":"CertificateNotFoundException"},
{"shape":"UnsupportedProtocolException"},
{"shape":"TooManyRegistrationsForTargetIdException"}
{"shape":"TooManyRegistrationsForTargetIdException"},
{"shape":"TooManyTargetsException"}
]
},
"CreateLoadBalancer":{
@ -75,7 +76,10 @@
{"shape":"InvalidSecurityGroupException"},
{"shape":"InvalidSchemeException"},
{"shape":"TooManyTagsException"},
{"shape":"DuplicateTagKeysException"}
{"shape":"DuplicateTagKeysException"},
{"shape":"ResourceInUseException"},
{"shape":"AllocationIdNotFoundException"},
{"shape":"AvailabilityZoneNotSupportedException"}
]
},
"CreateRule":{
@ -94,10 +98,12 @@
{"shape":"TooManyTargetGroupsException"},
{"shape":"TooManyRulesException"},
{"shape":"TargetGroupAssociationLimitException"},
{"shape":"IncompatibleProtocolsException"},
{"shape":"ListenerNotFoundException"},
{"shape":"TargetGroupNotFoundException"},
{"shape":"InvalidConfigurationRequestException"},
{"shape":"TooManyRegistrationsForTargetIdException"}
{"shape":"TooManyRegistrationsForTargetIdException"},
{"shape":"TooManyTargetsException"}
]
},
"CreateTargetGroup":{
@ -113,7 +119,8 @@
},
"errors":[
{"shape":"DuplicateTargetGroupNameException"},
{"shape":"TooManyTargetGroupsException"}
{"shape":"TooManyTargetGroupsException"},
{"shape":"InvalidConfigurationRequestException"}
]
},
"DeleteListener":{
@ -372,7 +379,8 @@
{"shape":"CertificateNotFoundException"},
{"shape":"InvalidConfigurationRequestException"},
{"shape":"UnsupportedProtocolException"},
{"shape":"TooManyRegistrationsForTargetIdException"}
{"shape":"TooManyRegistrationsForTargetIdException"},
{"shape":"TooManyTargetsException"}
]
},
"ModifyLoadBalancerAttributes":{
@ -404,6 +412,7 @@
},
"errors":[
{"shape":"TargetGroupAssociationLimitException"},
{"shape":"IncompatibleProtocolsException"},
{"shape":"RuleNotFoundException"},
{"shape":"OperationNotPermittedException"},
{"shape":"TooManyRegistrationsForTargetIdException"},
@ -423,7 +432,8 @@
"resultWrapper":"ModifyTargetGroupResult"
},
"errors":[
{"shape":"TargetGroupNotFoundException"}
{"shape":"TargetGroupNotFoundException"},
{"shape":"InvalidConfigurationRequestException"}
]
},
"ModifyTargetGroupAttributes":{
@ -438,7 +448,8 @@
"resultWrapper":"ModifyTargetGroupAttributesResult"
},
"errors":[
{"shape":"TargetGroupNotFoundException"}
{"shape":"TargetGroupNotFoundException"},
{"shape":"InvalidConfigurationRequestException"}
]
},
"RegisterTargets":{
@ -544,7 +555,9 @@
{"shape":"LoadBalancerNotFoundException"},
{"shape":"InvalidConfigurationRequestException"},
{"shape":"SubnetNotFoundException"},
{"shape":"InvalidSubnetException"}
{"shape":"InvalidSubnetException"},
{"shape":"AllocationIdNotFoundException"},
{"shape":"AvailabilityZoneNotSupportedException"}
]
}
},
@ -584,13 +597,37 @@
"members":{
}
},
"AllocationId":{"type":"string"},
"AllocationIdNotFoundException":{
"type":"structure",
"members":{
},
"error":{
"code":"AllocationIdNotFound",
"httpStatusCode":400,
"senderFault":true
},
"exception":true
},
"AvailabilityZone":{
"type":"structure",
"members":{
"ZoneName":{"shape":"ZoneName"},
"SubnetId":{"shape":"SubnetId"}
"SubnetId":{"shape":"SubnetId"},
"LoadBalancerAddresses":{"shape":"LoadBalancerAddresses"}
}
},
"AvailabilityZoneNotSupportedException":{
"type":"structure",
"members":{
},
"error":{
"code":"AvailabilityZoneNotSupported",
"httpStatusCode":400,
"senderFault":true
},
"exception":true
},
"AvailabilityZones":{
"type":"list",
"member":{"shape":"AvailabilityZone"}
@ -660,16 +697,15 @@
},
"CreateLoadBalancerInput":{
"type":"structure",
"required":[
"Name",
"Subnets"
],
"required":["Name"],
"members":{
"Name":{"shape":"LoadBalancerName"},
"Subnets":{"shape":"Subnets"},
"SubnetMappings":{"shape":"SubnetMappings"},
"SecurityGroups":{"shape":"SecurityGroups"},
"Scheme":{"shape":"LoadBalancerSchemeEnum"},
"Tags":{"shape":"TagList"},
"Type":{"shape":"LoadBalancerTypeEnum"},
"IpAddressType":{"shape":"IpAddressType"}
}
},
@ -720,7 +756,8 @@
"HealthCheckTimeoutSeconds":{"shape":"HealthCheckTimeoutSeconds"},
"HealthyThresholdCount":{"shape":"HealthCheckThresholdCount"},
"UnhealthyThresholdCount":{"shape":"HealthCheckThresholdCount"},
"Matcher":{"shape":"Matcher"}
"Matcher":{"shape":"Matcher"},
"TargetType":{"shape":"TargetTypeEnum"}
}
},
"CreateTargetGroupOutput":{
@ -1080,6 +1117,7 @@
},
"exception":true
},
"IpAddress":{"type":"string"},
"IpAddressType":{
"type":"string",
"enum":[
@ -1152,6 +1190,17 @@
"IpAddressType":{"shape":"IpAddressType"}
}
},
"LoadBalancerAddress":{
"type":"structure",
"members":{
"IpAddress":{"shape":"IpAddress"},
"AllocationId":{"shape":"AllocationId"}
}
},
"LoadBalancerAddresses":{
"type":"list",
"member":{"shape":"LoadBalancerAddress"}
},
"LoadBalancerArn":{"type":"string"},
"LoadBalancerArns":{
"type":"list",
@ -1213,12 +1262,16 @@
"enum":[
"active",
"provisioning",
"active_impaired",
"failed"
]
},
"LoadBalancerTypeEnum":{
"type":"string",
"enum":["application"]
"enum":[
"application",
"network"
]
},
"LoadBalancers":{
"type":"list",
@ -1363,7 +1416,8 @@
"type":"string",
"enum":[
"HTTP",
"HTTPS"
"HTTPS",
"TCP"
]
},
"RegisterTargetsInput":{
@ -1453,7 +1507,7 @@
},
"RulePriority":{
"type":"integer",
"max":99999,
"max":50000,
"min":1
},
"RulePriorityList":{
@ -1542,7 +1596,8 @@
],
"members":{
"LoadBalancerArn":{"shape":"LoadBalancerArn"},
"Subnets":{"shape":"Subnets"}
"Subnets":{"shape":"Subnets"},
"SubnetMappings":{"shape":"SubnetMappings"}
}
},
"SetSubnetsOutput":{
@ -1577,6 +1632,17 @@
"String":{"type":"string"},
"StringValue":{"type":"string"},
"SubnetId":{"type":"string"},
"SubnetMapping":{
"type":"structure",
"members":{
"SubnetId":{"shape":"SubnetId"},
"AllocationId":{"shape":"AllocationId"}
}
},
"SubnetMappings":{
"type":"list",
"member":{"shape":"SubnetMapping"}
},
"SubnetNotFoundException":{
"type":"structure",
"members":{
@ -1637,7 +1703,8 @@
"required":["Id"],
"members":{
"Id":{"shape":"TargetId"},
"Port":{"shape":"Port"}
"Port":{"shape":"Port"},
"AvailabilityZone":{"shape":"ZoneName"}
}
},
"TargetDescriptions":{
@ -1660,7 +1727,8 @@
"UnhealthyThresholdCount":{"shape":"HealthCheckThresholdCount"},
"HealthCheckPath":{"shape":"Path"},
"Matcher":{"shape":"Matcher"},
"LoadBalancerArns":{"shape":"LoadBalancerArns"}
"LoadBalancerArns":{"shape":"LoadBalancerArns"},
"TargetType":{"shape":"TargetTypeEnum"}
}
},
"TargetGroupArn":{"type":"string"},
@ -1748,6 +1816,7 @@
"Target.NotInUse",
"Target.DeregistrationInProgress",
"Target.InvalidState",
"Target.IpUnusable",
"Elb.InternalError"
]
},
@ -1758,10 +1827,18 @@
"healthy",
"unhealthy",
"unused",
"draining"
"draining",
"unavailable"
]
},
"TargetId":{"type":"string"},
"TargetTypeEnum":{
"type":"string",
"enum":[
"instance",
"ip"
]
},
"TooManyCertificatesException":{
"type":"structure",
"members":{

View file

@ -1,38 +1,38 @@
{
"version": "2.0",
"service": "<fullname>Elastic Load Balancing</fullname> <p>A load balancer distributes incoming traffic across targets, such as your EC2 instances. This enables you to increase the availability of your application. The load balancer also monitors the health of its registered targets and ensures that it routes traffic only to healthy targets. 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. You configure a target group with a protocol and port number for connections from the load balancer to the targets, and with health check settings to be used when checking the health status of the targets.</p> <p>Elastic Load Balancing supports two types of load balancers: Classic Load Balancers and Application Load Balancers. 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/\">Elastic Load Balancing User Guide</a>.</p> <p>This reference covers the 2015-12-01 API, which supports Application Load Balancers. The 2012-06-01 API supports Classic Load Balancers.</p> <p>To get started, complete the following tasks:</p> <ol> <li> <p>Create an Application Load Balancer using <a>CreateLoadBalancer</a>.</p> </li> <li> <p>Create a target group using <a>CreateTargetGroup</a>.</p> </li> <li> <p>Register targets for the target group using <a>RegisterTargets</a>.</p> </li> <li> <p>Create one or more listeners for your load balancer using <a>CreateListener</a>.</p> </li> <li> <p>(Optional) Create one or more rules for content routing based on URL using <a>CreateRule</a>.</p> </li> </ol> <p>To delete an Application Load Balancer and its related resources, complete the following tasks:</p> <ol> <li> <p>Delete the load balancer using <a>DeleteLoadBalancer</a>.</p> </li> <li> <p>Delete the target group using <a>DeleteTargetGroup</a>.</p> </li> </ol> <p>All Elastic Load Balancing operations are idempotent, which means that they complete at most one time. If you repeat an operation, it succeeds.</p>",
"service": "<fullname>Elastic Load Balancing</fullname> <p>A load balancer distributes incoming traffic across targets, such as your EC2 instances. This enables you to increase the availability of your application. The load balancer also monitors the health of its registered targets and ensures that it routes traffic only to healthy targets. 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. You configure a target group with a protocol and port number for connections from the load balancer to the targets, and with health check settings to be used when checking the health status of the targets.</p> <p>Elastic Load Balancing supports the following types of load balancers: Application Load Balancers, Network Load Balancers, and Classic Load Balancers.</p> <p>An Application Load Balancer makes routing and load balancing decisions at the application layer (HTTP/HTTPS). A Network Load Balancer makes routing and load balancing decisions at the transport layer (TCP). Both Application Load Balancers and Network Load Balancers can route requests to one or more ports on each EC2 instance or container instance in your virtual private cloud (VPC).</p> <p>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. For more information, see the <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/\">Elastic Load Balancing User Guide</a>.</p> <p>This reference covers the 2015-12-01 API, which supports Application Load Balancers and Network Load Balancers. The 2012-06-01 API supports Classic Load Balancers.</p> <p>To get started, complete the following tasks:</p> <ol> <li> <p>Create a load balancer using <a>CreateLoadBalancer</a>.</p> </li> <li> <p>Create a target group using <a>CreateTargetGroup</a>.</p> </li> <li> <p>Register targets for the target group using <a>RegisterTargets</a>.</p> </li> <li> <p>Create one or more listeners for your load balancer using <a>CreateListener</a>.</p> </li> </ol> <p>To delete a load balancer and its related resources, complete the following tasks:</p> <ol> <li> <p>Delete the load balancer using <a>DeleteLoadBalancer</a>.</p> </li> <li> <p>Delete the target group using <a>DeleteTargetGroup</a>.</p> </li> </ol> <p>All Elastic Load Balancing operations are idempotent, which means that they complete at most one time. If you repeat an operation, it succeeds.</p>",
"operations": {
"AddTags": "<p>Adds the specified tags to the specified resource. You can tag your Application Load Balancers and your target groups.</p> <p>Each tag consists of a key and an optional value. If a resource already has a tag with the same key, <code>AddTags</code> updates its value.</p> <p>To list the current tags for your resources, use <a>DescribeTags</a>. To remove tags from your resources, use <a>RemoveTags</a>.</p>",
"CreateListener": "<p>Creates a listener for the specified Application Load Balancer.</p> <p>You can create up to 10 listeners per load balancer.</p> <p>To update a listener, use <a>ModifyListener</a>. When you are finished with a listener, you can delete it using <a>DeleteListener</a>. If you are finished with both the listener and the load balancer, you can delete them both using <a>DeleteLoadBalancer</a>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listeners.html\">Listeners for Your Application Load Balancers</a> in the <i>Application Load Balancers Guide</i>.</p>",
"CreateLoadBalancer": "<p>Creates an Application Load Balancer.</p> <p>When you create a load balancer, you can specify security groups, subnets, IP address type, and tags. Otherwise, you could do so later using <a>SetSecurityGroups</a>, <a>SetSubnets</a>, <a>SetIpAddressType</a>, and <a>AddTags</a>.</p> <p>To create listeners for your load balancer, use <a>CreateListener</a>. 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/application/load-balancer-limits.html\">Limits for Your Application Load Balancer</a> in the <i>Application Load Balancers Guide</i>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/application-load-balancers.html\">Application Load Balancers</a> in the <i>Application Load Balancers Guide</i>.</p>",
"CreateRule": "<p>Creates a rule for the specified listener.</p> <p>Each rule can have one action and one condition. Rules are evaluated in priority order, from the lowest value to the highest value. When the condition for a rule is met, the specified action is taken. If no conditions are met, the default action for the default rule is taken. For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listeners.html#listener-rules\">Listener Rules</a> in the <i>Application Load Balancers Guide</i>.</p> <p>To view your current rules, use <a>DescribeRules</a>. To update a rule, use <a>ModifyRule</a>. To set the priorities of your rules, use <a>SetRulePriorities</a>. To delete a rule, use <a>DeleteRule</a>.</p>",
"CreateTargetGroup": "<p>Creates a target group.</p> <p>To register targets with the target group, use <a>RegisterTargets</a>. To update the health check settings for the target group, use <a>ModifyTargetGroup</a>. To monitor the health of targets in the target group, use <a>DescribeTargetHealth</a>.</p> <p>To route traffic to the targets in a target group, specify the target group in an action using <a>CreateListener</a> or <a>CreateRule</a>.</p> <p>To delete a target group, use <a>DeleteTargetGroup</a>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html\">Target Groups for Your Application Load Balancers</a> in the <i>Application Load Balancers Guide</i>.</p>",
"AddTags": "<p>Adds the specified tags to the specified Elastic Load Balancing resource. You can tag your Application Load Balancers, Network Load Balancers, and your target groups.</p> <p>Each tag consists of a key and an optional value. If a resource already has a tag with the same key, <code>AddTags</code> updates its value.</p> <p>To list the current tags for your resources, use <a>DescribeTags</a>. To remove tags from your resources, use <a>RemoveTags</a>.</p>",
"CreateListener": "<p>Creates a listener for the specified Application Load Balancer or Network Load Balancer.</p> <p>You can create up to 10 listeners per load balancer.</p> <p>To update a listener, use <a>ModifyListener</a>. When you are finished with a listener, you can delete it using <a>DeleteListener</a>. If you are finished with both the listener and the load balancer, you can delete them both using <a>DeleteLoadBalancer</a>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listeners.html\">Listeners for Your Application Load Balancers</a> in the <i>Application Load Balancers Guide</i> and <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-listeners.html\">Listeners for Your Network Load Balancers</a> in the <i>Network Load Balancers Guide</i>.</p>",
"CreateLoadBalancer": "<p>Creates an Application Load Balancer or a Network Load Balancer.</p> <p>When you create a load balancer, you can specify security groups, subnets, IP address type, and tags. Otherwise, you could do so later using <a>SetSecurityGroups</a>, <a>SetSubnets</a>, <a>SetIpAddressType</a>, and <a>AddTags</a>.</p> <p>To create listeners for your load balancer, use <a>CreateListener</a>. 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/application/load-balancer-limits.html\">Limits for Your Application Load Balancer</a> in the <i>Application Load Balancers Guide</i> and <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-limits.html\">Limits for Your Network Load Balancer</a> in the <i>Network Load Balancers Guide</i>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/application-load-balancers.html\">Application Load Balancers</a> in the <i>Application Load Balancers Guide</i> and <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html\">Network Load Balancers</a> in the <i>Network Load Balancers Guide</i>.</p>",
"CreateRule": "<p>Creates a rule for the specified listener. The listener must be associated with an Application Load Balancer.</p> <p>Rules are evaluated in priority order, from the lowest value to the highest value. When the condition for a rule is met, the specified action is taken. If no conditions are met, the action for the default rule is taken. For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listeners.html#listener-rules\">Listener Rules</a> in the <i>Application Load Balancers Guide</i>.</p> <p>To view your current rules, use <a>DescribeRules</a>. To update a rule, use <a>ModifyRule</a>. To set the priorities of your rules, use <a>SetRulePriorities</a>. To delete a rule, use <a>DeleteRule</a>.</p>",
"CreateTargetGroup": "<p>Creates a target group.</p> <p>To register targets with the target group, use <a>RegisterTargets</a>. To update the health check settings for the target group, use <a>ModifyTargetGroup</a>. To monitor the health of targets in the target group, use <a>DescribeTargetHealth</a>.</p> <p>To route traffic to the targets in a target group, specify the target group in an action using <a>CreateListener</a> or <a>CreateRule</a>.</p> <p>To delete a target group, use <a>DeleteTargetGroup</a>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html\">Target Groups for Your Application Load Balancers</a> in the <i>Application Load Balancers Guide</i> or <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html\">Target Groups for Your Network Load Balancers</a> in the <i>Network Load Balancers Guide</i>.</p>",
"DeleteListener": "<p>Deletes the specified listener.</p> <p>Alternatively, your listener is deleted when you delete the load balancer it is attached to using <a>DeleteLoadBalancer</a>.</p>",
"DeleteLoadBalancer": "<p>Deletes the specified Application Load Balancer and its attached listeners.</p> <p>You can't delete a load balancer if deletion protection is enabled. If the load balancer does not exist or has already been deleted, the call succeeds.</p> <p>Deleting a load balancer does not affect its registered targets. For example, your EC2 instances continue to run and are still registered to their target groups. If you no longer need these EC2 instances, you can stop or terminate them.</p>",
"DeleteLoadBalancer": "<p>Deletes the specified Application Load Balancer or Network Load Balancer and its attached listeners.</p> <p>You can't delete a load balancer if deletion protection is enabled. If the load balancer does not exist or has already been deleted, the call succeeds.</p> <p>Deleting a load balancer does not affect its registered targets. For example, your EC2 instances continue to run and are still registered to their target groups. If you no longer need these EC2 instances, you can stop or terminate them.</p>",
"DeleteRule": "<p>Deletes the specified rule.</p>",
"DeleteTargetGroup": "<p>Deletes the specified target group.</p> <p>You can delete a target group if it is not referenced by any actions. Deleting a target group also deletes any associated health checks.</p>",
"DeregisterTargets": "<p>Deregisters the specified targets from the specified target group. After the targets are deregistered, they no longer receive traffic from the load balancer.</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/application/load-balancer-limits.html\">Limits for Your Application Load Balancer</a> in the <i>Application Load Balancer Guide</i>.</p>",
"DescribeListeners": "<p>Describes the specified listeners or the listeners for the specified Application Load Balancer. You must specify either a load balancer or one or more listeners.</p>",
"DescribeLoadBalancerAttributes": "<p>Describes the attributes for the specified Application Load Balancer.</p>",
"DescribeLoadBalancers": "<p>Describes the specified Application Load Balancers or all of your Application Load Balancers.</p> <p>To describe the listeners for a load balancer, use <a>DescribeListeners</a>. To describe the attributes for a load balancer, use <a>DescribeLoadBalancerAttributes</a>.</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/application/load-balancer-limits.html\">Limits for Your Application Load Balancers</a> in the <i>Application Load Balancer Guide</i> or <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-limits.html\">Limits for Your Network Load Balancers</a> in the <i>Network Load Balancers Guide</i>.</p>",
"DescribeListeners": "<p>Describes the specified listeners or the listeners for the specified Application Load Balancer or Network Load Balancer. You must specify either a load balancer or one or more listeners.</p>",
"DescribeLoadBalancerAttributes": "<p>Describes the attributes for the specified Application Load Balancer or Network Load Balancer.</p>",
"DescribeLoadBalancers": "<p>Describes the specified load balancers or all of your load balancers.</p> <p>To describe the listeners for a load balancer, use <a>DescribeListeners</a>. To describe the attributes for a load balancer, use <a>DescribeLoadBalancerAttributes</a>.</p>",
"DescribeRules": "<p>Describes the specified rules or the rules for the specified listener. You must specify either a listener or one or more rules.</p>",
"DescribeSSLPolicies": "<p>Describes the specified policies or all policies used for SSL negotiation.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html#describe-ssl-policies\">Security Policies</a> in the <i>Application Load Balancers Guide</i>.</p>",
"DescribeTags": "<p>Describes the tags for the specified resources. You can describe the tags for one or more Application Load Balancers and target groups.</p>",
"DescribeTags": "<p>Describes the tags for the specified resources. You can describe the tags for one or more Application Load Balancers, Network Load Balancers, and target groups.</p>",
"DescribeTargetGroupAttributes": "<p>Describes the attributes for the specified target group.</p>",
"DescribeTargetGroups": "<p>Describes the specified target groups or all of your target groups. By default, all target groups are described. Alternatively, you can specify one of the following to filter the results: the ARN of the load balancer, the names of one or more target groups, or the ARNs of one or more target groups.</p> <p>To describe the targets for a target group, use <a>DescribeTargetHealth</a>. To describe the attributes of a target group, use <a>DescribeTargetGroupAttributes</a>.</p>",
"DescribeTargetHealth": "<p>Describes the health of the specified targets or all of your targets.</p>",
"ModifyListener": "<p>Modifies the specified properties of the specified listener.</p> <p>Any properties that you do not specify retain their current values. However, changing the protocol from HTTPS to HTTP removes the security policy and SSL certificate properties. If you change the protocol from HTTP to HTTPS, you must add the security policy and server certificate.</p>",
"ModifyLoadBalancerAttributes": "<p>Modifies the specified attributes of the specified Application Load Balancer.</p> <p>If any of the specified attributes can't be modified as requested, the call fails. Any existing attributes that you do not modify retain their current values.</p>",
"ModifyLoadBalancerAttributes": "<p>Modifies the specified attributes of the specified Application Load Balancer or Network Load Balancer.</p> <p>If any of the specified attributes can't be modified as requested, the call fails. Any existing attributes that you do not modify retain their current values.</p>",
"ModifyRule": "<p>Modifies the specified rule.</p> <p>Any existing properties that you do not modify retain their current values.</p> <p>To modify the default action, use <a>ModifyListener</a>.</p>",
"ModifyTargetGroup": "<p>Modifies the health checks used when evaluating the health state of the targets in the specified target group.</p> <p>To monitor the health of the targets, use <a>DescribeTargetHealth</a>.</p>",
"ModifyTargetGroupAttributes": "<p>Modifies the specified attributes of the specified target group.</p>",
"RegisterTargets": "<p>Registers the specified targets with the specified target group.</p> <p>By default, the load balancer routes requests to registered targets using the protocol and port number for the target group. Alternatively, you can override the port for a target when you register it.</p> <p>The target must be in the virtual private cloud (VPC) that you specified for the target group. If the target is an EC2 instance, it must be in the <code>running</code> state when you register it.</p> <p>To remove a target from a target group, use <a>DeregisterTargets</a>.</p>",
"RemoveTags": "<p>Removes the specified tags from the specified resource.</p> <p>To list the current tags for your resources, use <a>DescribeTags</a>.</p>",
"SetIpAddressType": "<p>Sets the type of IP addresses used by the subnets of the specified Application Load Balancer.</p>",
"RegisterTargets": "<p>Registers the specified targets with the specified target group.</p> <p>By default, the load balancer routes requests to registered targets using the protocol and port number for the target group. Alternatively, you can override the port for a target when you register it.</p> <p>The target must be in the virtual private cloud (VPC) that you specified for the target group. If the target is an EC2 instance, it must be in the <code>running</code> state when you register it.</p> <p>Network Load Balancers do not support the following instance types as targets: C1, CC1, CC2, CG1, CG2, CR1, CS1, G1, G2, HI1, HS1, M1, M2, M3, and T1.</p> <p>To remove a target from a target group, use <a>DeregisterTargets</a>.</p>",
"RemoveTags": "<p>Removes the specified tags from the specified Elastic Load Balancing resource.</p> <p>To list the current tags for your resources, use <a>DescribeTags</a>.</p>",
"SetIpAddressType": "<p>Sets the type of IP addresses used by the subnets of the specified Application Load Balancer or Network Load Balancer.</p> <p>Note that Network Load Balancers must use <code>ipv4</code>.</p>",
"SetRulePriorities": "<p>Sets the priorities of the specified rules.</p> <p>You can reorder the rules as long as there are no priority conflicts in the new order. Any existing rules that you do not specify retain their current priority.</p>",
"SetSecurityGroups": "<p>Associates the specified security groups with the specified load balancer. The specified security groups override the previously associated security groups.</p>",
"SetSubnets": "<p>Enables the Availability Zone for the specified subnets for the specified load balancer. The specified subnets replace the previously enabled subnets.</p>"
"SetSecurityGroups": "<p>Associates the specified security groups with the specified Application Load Balancer. The specified security groups override the previously associated security groups.</p> <p>Note that you can't specify a security group for a Network Load Balancer.</p>",
"SetSubnets": "<p>Enables the Availability Zone for the specified subnets for the specified Application Load Balancer. The specified subnets replace the previously enabled subnets.</p> <p>Note that you can't change the subnets for a Network Load Balancer.</p>"
},
"shapes": {
"Action": {
@ -50,11 +50,11 @@
"Actions": {
"base": null,
"refs": {
"CreateListenerInput$DefaultActions": "<p>The default action for the listener.</p>",
"CreateListenerInput$DefaultActions": "<p>The default action for the listener. For Application Load Balancers, the protocol of the specified target group must be HTTP or HTTPS. For Network Load Balancers, the protocol of the specified target group must be TCP.</p>",
"CreateRuleInput$Actions": "<p>An action. Each action has the type <code>forward</code> and specifies a target group.</p>",
"Listener$DefaultActions": "<p>The default actions for the listener.</p>",
"ModifyListenerInput$DefaultActions": "<p>The default actions.</p>",
"ModifyRuleInput$Actions": "<p>The actions.</p>",
"ModifyListenerInput$DefaultActions": "<p>The default action. For Application Load Balancers, the protocol of the specified target group must be HTTP or HTTPS. For Network Load Balancers, the protocol of the specified target group must be TCP.</p>",
"ModifyRuleInput$Actions": "<p>The actions. The target group must use the HTTP or HTTPS protocol.</p>",
"Rule$Actions": "<p>The actions.</p>"
}
},
@ -68,12 +68,29 @@
"refs": {
}
},
"AllocationId": {
"base": null,
"refs": {
"LoadBalancerAddress$AllocationId": "<p>[Network Load Balancers] The allocation ID of the Elastic IP address.</p>",
"SubnetMapping$AllocationId": "<p>[Network Load Balancers] The allocation ID of the Elastic IP address.</p>"
}
},
"AllocationIdNotFoundException": {
"base": "<p>The specified allocation ID does not exist.</p>",
"refs": {
}
},
"AvailabilityZone": {
"base": "<p>Information about an Availability Zone.</p>",
"refs": {
"AvailabilityZones$member": null
}
},
"AvailabilityZoneNotSupportedException": {
"base": "<p>The specified Availability Zone is not supported.</p>",
"refs": {
}
},
"AvailabilityZones": {
"base": null,
"refs": {
@ -102,7 +119,7 @@
"CertificateList": {
"base": null,
"refs": {
"CreateListenerInput$Certificates": "<p>The SSL server certificate. You must provide exactly one certificate if the protocol is HTTPS.</p>",
"CreateListenerInput$Certificates": "<p>[HTTPS listeners] The SSL server certificate. You must provide exactly one certificate.</p>",
"Listener$Certificates": "<p>The SSL server certificate. You must provide a certificate if the protocol is HTTPS.</p>",
"ModifyListenerInput$Certificates": "<p>The SSL server certificate.</p>"
}
@ -373,16 +390,16 @@
"HealthCheckIntervalSeconds": {
"base": null,
"refs": {
"CreateTargetGroupInput$HealthCheckIntervalSeconds": "<p>The approximate amount of time, in seconds, between health checks of an individual target. The default is 30 seconds.</p>",
"ModifyTargetGroupInput$HealthCheckIntervalSeconds": "<p>The approximate amount of time, in seconds, between health checks of an individual target.</p>",
"CreateTargetGroupInput$HealthCheckIntervalSeconds": "<p>The approximate amount of time, in seconds, between health checks of an individual target. For Application Load Balancers, the range is 5 to 300 seconds. For Network Load Balancers, the supported values are 10 or 30 seconds. The default is 30 seconds.</p>",
"ModifyTargetGroupInput$HealthCheckIntervalSeconds": "<p>The approximate amount of time, in seconds, between health checks of an individual target. For Application Load Balancers, the range is 5 to 300 seconds. For Network Load Balancers, the supported values are 10 or 30 seconds.</p>",
"TargetGroup$HealthCheckIntervalSeconds": "<p>The approximate amount of time, in seconds, between health checks of an individual target.</p>"
}
},
"HealthCheckPort": {
"base": null,
"refs": {
"CreateTargetGroupInput$HealthCheckPort": "<p>The port the load balancer uses when performing health checks on targets. The default is <code>traffic-port</code>, which indicates the port on which each target receives traffic from the load balancer.</p>",
"ModifyTargetGroupInput$HealthCheckPort": "<p>The port to use to connect with the target.</p>",
"CreateTargetGroupInput$HealthCheckPort": "<p>The port the load balancer uses when performing health checks on targets. The default is <code>traffic-port</code>, which is the port on which each target receives traffic from the load balancer.</p>",
"ModifyTargetGroupInput$HealthCheckPort": "<p>The port the load balancer uses when performing health checks on targets.</p>",
"TargetGroup$HealthCheckPort": "<p>The port to use to connect with the target.</p>",
"TargetHealthDescription$HealthCheckPort": "<p>The port to use to connect with the target.</p>"
}
@ -390,10 +407,10 @@
"HealthCheckThresholdCount": {
"base": null,
"refs": {
"CreateTargetGroupInput$HealthyThresholdCount": "<p>The number of consecutive health checks successes required before considering an unhealthy target healthy. The default is 5.</p>",
"CreateTargetGroupInput$UnhealthyThresholdCount": "<p>The number of consecutive health check failures required before considering a target unhealthy. The default is 2.</p>",
"CreateTargetGroupInput$HealthyThresholdCount": "<p>The number of consecutive health checks successes required before considering an unhealthy target healthy. For Application Load Balancers, the default is 5. For Network Load Balancers, the default is 3.</p>",
"CreateTargetGroupInput$UnhealthyThresholdCount": "<p>The number of consecutive health check failures required before considering a target unhealthy. For Application Load Balancers, the default is 2. For Network Load Balancers, this value must be the same as the healthy threshold count.</p>",
"ModifyTargetGroupInput$HealthyThresholdCount": "<p>The number of consecutive health checks successes required before considering an unhealthy target healthy.</p>",
"ModifyTargetGroupInput$UnhealthyThresholdCount": "<p>The number of consecutive health check failures required before considering the target unhealthy.</p>",
"ModifyTargetGroupInput$UnhealthyThresholdCount": "<p>The number of consecutive health check failures required before considering the target unhealthy. For Network Load Balancers, this value must be the same as the healthy threshold count.</p>",
"TargetGroup$HealthyThresholdCount": "<p>The number of consecutive health checks successes required before considering an unhealthy target healthy.</p>",
"TargetGroup$UnhealthyThresholdCount": "<p>The number of consecutive health check failures required before considering the target unhealthy.</p>"
}
@ -401,8 +418,8 @@
"HealthCheckTimeoutSeconds": {
"base": null,
"refs": {
"CreateTargetGroupInput$HealthCheckTimeoutSeconds": "<p>The amount of time, in seconds, during which no response from a target means a failed health check. The default is 5 seconds.</p>",
"ModifyTargetGroupInput$HealthCheckTimeoutSeconds": "<p>The amount of time, in seconds, during which no response means a failed health check.</p>",
"CreateTargetGroupInput$HealthCheckTimeoutSeconds": "<p>The amount of time, in seconds, during which no response from a target means a failed health check. For Application Load Balancers, the range is 2 to 60 seconds and the default is 5 seconds. For Network Load Balancers, this is 10 seconds for TCP and HTTPS health checks and 6 seconds for HTTP health checks.</p>",
"ModifyTargetGroupInput$HealthCheckTimeoutSeconds": "<p>[HTTP/HTTPS health checks] The amount of time, in seconds, during which no response means a failed health check.</p>",
"TargetGroup$HealthCheckTimeoutSeconds": "<p>The amount of time, in seconds, during which no response means a failed health check.</p>"
}
},
@ -414,7 +431,7 @@
"HttpCode": {
"base": null,
"refs": {
"Matcher$HttpCode": "<p>The HTTP codes. You can specify values between 200 and 499. The default value is 200. You can specify multiple values (for example, \"200,202\") or a range of values (for example, \"200-299\").</p>"
"Matcher$HttpCode": "<p>The HTTP codes.</p> <p>For Application Load Balancers, you can specify values between 200 and 499, and the default value is 200. You can specify multiple values (for example, \"200,202\") or a range of values (for example, \"200-299\").</p> <p>For Network Load Balancers, this is 200 to 399.</p>"
}
},
"IncompatibleProtocolsException": {
@ -447,10 +464,16 @@
"refs": {
}
},
"IpAddress": {
"base": null,
"refs": {
"LoadBalancerAddress$IpAddress": "<p>The static IP address.</p>"
}
},
"IpAddressType": {
"base": null,
"refs": {
"CreateLoadBalancerInput$IpAddressType": "<p>The type of IP addresses used by the subnets for your load balancer. The possible values are <code>ipv4</code> (for IPv4 addresses) and <code>dualstack</code> (for IPv4 and IPv6 addresses). Internal load balancers must use <code>ipv4</code>.</p>",
"CreateLoadBalancerInput$IpAddressType": "<p>[Application Load Balancers] The type of IP addresses used by the subnets for your load balancer. The possible values are <code>ipv4</code> (for IPv4 addresses) and <code>dualstack</code> (for IPv4 and IPv6 addresses). Internal load balancers must use <code>ipv4</code>.</p>",
"LoadBalancer$IpAddressType": "<p>The type of IP addresses used by the subnets for your load balancer. The possible values are <code>ipv4</code> (for IPv4 addresses) and <code>dualstack</code> (for IPv4 and IPv6 addresses).</p>",
"SetIpAddressTypeInput$IpAddressType": "<p>The IP address type. The possible values are <code>ipv4</code> (for IPv4 addresses) and <code>dualstack</code> (for IPv4 and IPv6 addresses). Internal load balancers must use <code>ipv4</code>.</p>",
"SetIpAddressTypeOutput$IpAddressType": "<p>The IP address type.</p>"
@ -522,6 +545,18 @@
"LoadBalancers$member": null
}
},
"LoadBalancerAddress": {
"base": "<p>Information about a static IP address for a load balancer.</p>",
"refs": {
"LoadBalancerAddresses$member": null
}
},
"LoadBalancerAddresses": {
"base": null,
"refs": {
"AvailabilityZone$LoadBalancerAddresses": "<p>[Network Load Balancers] The static IP address.</p>"
}
},
"LoadBalancerArn": {
"base": null,
"refs": {
@ -555,7 +590,7 @@
"LoadBalancerAttributeKey": {
"base": null,
"refs": {
"LoadBalancerAttribute$Key": "<p>The name of the attribute.</p> <ul> <li> <p> <code>access_logs.s3.enabled</code> - Indicates whether access logs stored in Amazon S3 are enabled. The value is <code>true</code> or <code>false</code>.</p> </li> <li> <p> <code>access_logs.s3.bucket</code> - The name of the S3 bucket for the access logs. This attribute is required if access logs in Amazon S3 are enabled. The bucket must exist in the same region as the load balancer and have a bucket policy that grants Elastic Load Balancing permission to write to the bucket.</p> </li> <li> <p> <code>access_logs.s3.prefix</code> - The prefix for the location in the S3 bucket. If you don't specify a prefix, the access logs are stored in the root of the bucket.</p> </li> <li> <p> <code>deletion_protection.enabled</code> - Indicates whether deletion protection is enabled. The value is <code>true</code> or <code>false</code>.</p> </li> <li> <p> <code>idle_timeout.timeout_seconds</code> - The idle timeout value, in seconds. The valid range is 1-3600. The default is 60 seconds.</p> </li> </ul>"
"LoadBalancerAttribute$Key": "<p>The name of the attribute.</p> <ul> <li> <p> <code>access_logs.s3.enabled</code> - [Application Load Balancers] Indicates whether access logs stored in Amazon S3 are enabled. The value is <code>true</code> or <code>false</code>.</p> </li> <li> <p> <code>access_logs.s3.bucket</code> - [Application Load Balancers] The name of the S3 bucket for the access logs. This attribute is required if access logs in Amazon S3 are enabled. The bucket must exist in the same region as the load balancer and have a bucket policy that grants Elastic Load Balancing permission to write to the bucket.</p> </li> <li> <p> <code>access_logs.s3.prefix</code> - [Application Load Balancers] The prefix for the location in the S3 bucket. If you don't specify a prefix, the access logs are stored in the root of the bucket.</p> </li> <li> <p> <code>deletion_protection.enabled</code> - Indicates whether deletion protection is enabled. The value is <code>true</code> or <code>false</code>.</p> </li> <li> <p> <code>idle_timeout.timeout_seconds</code> - [Application Load Balancers] The idle timeout value, in seconds. The valid range is 1-4000. The default is 60 seconds.</p> </li> </ul>"
}
},
"LoadBalancerAttributeValue": {
@ -613,6 +648,7 @@
"LoadBalancerTypeEnum": {
"base": null,
"refs": {
"CreateLoadBalancerInput$Type": "<p>The type of load balancer to create. The default is <code>application</code>.</p>",
"LoadBalancer$Type": "<p>The type of load balancer.</p>"
}
},
@ -643,8 +679,8 @@
"Matcher": {
"base": "<p>Information to use when checking for a successful response from a target.</p>",
"refs": {
"CreateTargetGroupInput$Matcher": "<p>The HTTP codes to use when checking for a successful response from a target. The default is 200.</p>",
"ModifyTargetGroupInput$Matcher": "<p>The HTTP codes to use when checking for a successful response from a target.</p>",
"CreateTargetGroupInput$Matcher": "<p>[HTTP/HTTPS health checks] The HTTP codes to use when checking for a successful response from a target.</p>",
"ModifyTargetGroupInput$Matcher": "<p>[HTTP/HTTPS health checks] The HTTP codes to use when checking for a successful response from a target.</p>",
"TargetGroup$Matcher": "<p>The HTTP codes to use when checking for a successful response from a target.</p>"
}
},
@ -707,7 +743,7 @@
"Name": {
"base": null,
"refs": {
"Limit$Name": "<p>The name of the limit. The possible values are:</p> <ul> <li> <p>application-load-balancers</p> </li> <li> <p>listeners-per-application-load-balancer</p> </li> <li> <p>rules-per-application-load-balancer</p> </li> <li> <p>target-groups</p> </li> <li> <p>targets-per-application-load-balancer</p> </li> </ul>"
"Limit$Name": "<p>The name of the limit. The possible values are:</p> <ul> <li> <p>application-load-balancers</p> </li> <li> <p>listeners-per-application-load-balancer</p> </li> <li> <p>listeners-per-network-load-balancer</p> </li> <li> <p>network-load-balancers</p> </li> <li> <p>rules-per-application-load-balancer</p> </li> <li> <p>target-groups</p> </li> <li> <p>targets-per-application-load-balancer</p> </li> </ul>"
}
},
"OperationNotPermittedException": {
@ -729,8 +765,8 @@
"Path": {
"base": null,
"refs": {
"CreateTargetGroupInput$HealthCheckPath": "<p>The ping path that is the destination on the targets for health checks. The default is /.</p>",
"ModifyTargetGroupInput$HealthCheckPath": "<p>The ping path that is the destination for the health check request.</p>",
"CreateTargetGroupInput$HealthCheckPath": "<p>[HTTP/HTTPS health checks] The ping path that is the destination on the targets for health checks. The default is /.</p>",
"ModifyTargetGroupInput$HealthCheckPath": "<p>[HTTP/HTTPS health checks] The ping path that is the destination for the health check request.</p>",
"TargetGroup$HealthCheckPath": "<p>The destination for the health check request.</p>"
}
},
@ -753,12 +789,12 @@
"ProtocolEnum": {
"base": null,
"refs": {
"CreateListenerInput$Protocol": "<p>The protocol for connections from clients to the load balancer.</p>",
"CreateTargetGroupInput$Protocol": "<p>The protocol to use for routing traffic to the targets.</p>",
"CreateTargetGroupInput$HealthCheckProtocol": "<p>The protocol the load balancer uses when performing health checks on targets. The default is the HTTP protocol.</p>",
"CreateListenerInput$Protocol": "<p>The protocol for connections from clients to the load balancer. For Application Load Balancers, the supported protocols are HTTP and HTTPS. For Network Load Balancers, the supported protocol is TCP.</p>",
"CreateTargetGroupInput$Protocol": "<p>The protocol to use for routing traffic to the targets. For Application Load Balancers, the supported protocols are HTTP and HTTPS. For Network Load Balancers, the supported protocol is TCP.</p>",
"CreateTargetGroupInput$HealthCheckProtocol": "<p>The protocol the load balancer uses when performing health checks on targets. The TCP protocol is supported only if the protocol of the target group is TCP. For Application Load Balancers, the default is HTTP. For Network Load Balancers, the default is TCP.</p>",
"Listener$Protocol": "<p>The protocol for connections from clients to the load balancer.</p>",
"ModifyListenerInput$Protocol": "<p>The protocol for connections from clients to the load balancer.</p>",
"ModifyTargetGroupInput$HealthCheckProtocol": "<p>The protocol to use to connect with the target.</p>",
"ModifyListenerInput$Protocol": "<p>The protocol for connections from clients to the load balancer. Application Load Balancers support HTTP and HTTPS and Network Load Balancers support TCP.</p>",
"ModifyTargetGroupInput$HealthCheckProtocol": "<p>The protocol the load balancer uses when performing health checks on targets. The TCP protocol is supported only if the protocol of the target group is TCP.</p>",
"TargetGroup$Protocol": "<p>The protocol to use for routing traffic to the targets.</p>",
"TargetGroup$HealthCheckProtocol": "<p>The protocol to use to connect with the target.</p>"
}
@ -834,7 +870,7 @@
"RuleConditionList": {
"base": null,
"refs": {
"CreateRuleInput$Conditions": "<p>A condition. Each condition specifies a field name and a single value.</p> <p>If the field name is <code>host-header</code>, you can specify a single host name (for example, my.example.com). A host name is case insensitive, can be up to 128 characters in length, and can contain any of the following characters. Note that you can include up to three wildcard characters.</p> <ul> <li> <p>A-Z, a-z, 0-9</p> </li> <li> <p>- .</p> </li> <li> <p>* (matches 0 or more characters)</p> </li> <li> <p>? (matches exactly 1 character)</p> </li> </ul> <p>If the field name is <code>path-pattern</code>, you can specify a single path pattern. A path pattern is case sensitive, can be up to 128 characters in length, and can contain any of the following characters. Note that you can include up to three wildcard characters.</p> <ul> <li> <p>A-Z, a-z, 0-9</p> </li> <li> <p>_ - . $ / ~ \" ' @ : +</p> </li> <li> <p>&amp; (using &amp;amp;)</p> </li> <li> <p>* (matches 0 or more characters)</p> </li> <li> <p>? (matches exactly 1 character)</p> </li> </ul>",
"CreateRuleInput$Conditions": "<p>The conditions. Each condition specifies a field name and a single value.</p> <p>If the field name is <code>host-header</code>, you can specify a single host name (for example, my.example.com). A host name is case insensitive, can be up to 128 characters in length, and can contain any of the following characters. Note that you can include up to three wildcard characters.</p> <ul> <li> <p>A-Z, a-z, 0-9</p> </li> <li> <p>- .</p> </li> <li> <p>* (matches 0 or more characters)</p> </li> <li> <p>? (matches exactly 1 character)</p> </li> </ul> <p>If the field name is <code>path-pattern</code>, you can specify a single path pattern. A path pattern is case sensitive, can be up to 128 characters in length, and can contain any of the following characters. Note that you can include up to three wildcard characters.</p> <ul> <li> <p>A-Z, a-z, 0-9</p> </li> <li> <p>_ - . $ / ~ \" ' @ : +</p> </li> <li> <p>&amp; (using &amp;amp;)</p> </li> <li> <p>* (matches 0 or more characters)</p> </li> <li> <p>? (matches exactly 1 character)</p> </li> </ul>",
"ModifyRuleInput$Conditions": "<p>The conditions.</p>",
"Rule$Conditions": "<p>The conditions.</p>"
}
@ -886,7 +922,7 @@
"SecurityGroups": {
"base": null,
"refs": {
"CreateLoadBalancerInput$SecurityGroups": "<p>The IDs of the security groups to assign to the load balancer.</p>",
"CreateLoadBalancerInput$SecurityGroups": "<p>[Application Load Balancers] The IDs of the security groups to assign to the load balancer.</p>",
"LoadBalancer$SecurityGroups": "<p>The IDs of the security groups for the load balancer.</p>",
"SetSecurityGroupsInput$SecurityGroups": "<p>The IDs of the security groups.</p>",
"SetSecurityGroupsOutput$SecurityGroupIds": "<p>The IDs of the security groups associated with the load balancer.</p>"
@ -947,7 +983,7 @@
"SslPolicyName": {
"base": null,
"refs": {
"CreateListenerInput$SslPolicy": "<p>The security policy that defines which ciphers and protocols are supported. The default is the current predefined security policy.</p>",
"CreateListenerInput$SslPolicy": "<p>[HTTPS listeners] The security policy that defines which ciphers and protocols are supported. The default is the current predefined security policy.</p>",
"Listener$SslPolicy": "<p>The security policy that defines which ciphers and protocols are supported. The default is the current predefined security policy.</p>",
"ModifyListenerInput$SslPolicy": "<p>The security policy that defines which protocols and ciphers are supported. For more information, see <a href=\"http://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html#describe-ssl-policies\">Security Policies</a> in the <i>Application Load Balancers Guide</i>.</p>",
"SslPolicy$Name": "<p>The name of the policy.</p>",
@ -994,9 +1030,23 @@
"base": null,
"refs": {
"AvailabilityZone$SubnetId": "<p>The ID of the subnet.</p>",
"SubnetMapping$SubnetId": "<p>The ID of the subnet.</p>",
"Subnets$member": null
}
},
"SubnetMapping": {
"base": "<p>Information about a subnet mapping.</p>",
"refs": {
"SubnetMappings$member": null
}
},
"SubnetMappings": {
"base": null,
"refs": {
"CreateLoadBalancerInput$SubnetMappings": "<p>The IDs of the subnets to attach to the load balancer. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.</p> <p>[Network Load Balancers] You can specify one Elastic IP address per subnet.</p> <p>[Application Load Balancers] You cannot specify Elastic IP addresses for your subnets.</p>",
"SetSubnetsInput$SubnetMappings": "<p>The IDs of the subnets. You must specify subnets from at least two Availability Zones. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.</p> <p>The load balancer is allocated one static IP address per subnet. You cannot specify your own Elastic IP addresses.</p>"
}
},
"SubnetNotFoundException": {
"base": "<p>The specified subnet does not exist.</p>",
"refs": {
@ -1005,8 +1055,8 @@
"Subnets": {
"base": null,
"refs": {
"CreateLoadBalancerInput$Subnets": "<p>The IDs of the subnets to attach to the load balancer. You can specify only one subnet per Availability Zone. You must specify subnets from at least two Availability Zones.</p>",
"SetSubnetsInput$Subnets": "<p>The IDs of the subnets. You must specify at least two subnets. You can add only one subnet per Availability Zone.</p>"
"CreateLoadBalancerInput$Subnets": "<p>The IDs of the subnets to attach to the load balancer. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.</p> <p>[Application Load Balancers] You must specify subnets from at least two Availability Zones.</p>",
"SetSubnetsInput$Subnets": "<p>The IDs of the subnets. You must specify subnets from at least two Availability Zones. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.</p>"
}
},
"Tag": {
@ -1110,7 +1160,7 @@
"TargetGroupAttributeKey": {
"base": null,
"refs": {
"TargetGroupAttribute$Key": "<p>The name of the attribute.</p> <ul> <li> <p> <code>deregistration_delay.timeout_seconds</code> - The amount time for Elastic Load Balancing to wait before changing the state of a deregistering target from <code>draining</code> to <code>unused</code>. The range is 0-3600 seconds. The default value is 300 seconds.</p> </li> <li> <p> <code>stickiness.enabled</code> - Indicates whether sticky sessions are enabled. The value is <code>true</code> or <code>false</code>.</p> </li> <li> <p> <code>stickiness.type</code> - The type of sticky sessions. The possible value is <code>lb_cookie</code>.</p> </li> <li> <p> <code>stickiness.lb_cookie.duration_seconds</code> - The time period, in seconds, during which requests from a client should be routed to the same target. After this time period expires, the load balancer-generated cookie is considered stale. The range is 1 second to 1 week (604800 seconds). The default value is 1 day (86400 seconds).</p> </li> </ul>"
"TargetGroupAttribute$Key": "<p>The name of the attribute.</p> <ul> <li> <p> <code>deregistration_delay.timeout_seconds</code> - The amount time for Elastic Load Balancing to wait before changing the state of a deregistering target from <code>draining</code> to <code>unused</code>. The range is 0-3600 seconds. The default value is 300 seconds.</p> </li> <li> <p> <code>stickiness.enabled</code> - [Application Load Balancers] Indicates whether sticky sessions are enabled. The value is <code>true</code> or <code>false</code>.</p> </li> <li> <p> <code>stickiness.type</code> - [Application Load Balancers] The type of sticky sessions. The possible value is <code>lb_cookie</code>.</p> </li> <li> <p> <code>stickiness.lb_cookie.duration_seconds</code> - [Application Load Balancers] The time period, in seconds, during which requests from a client should be routed to the same target. After this time period expires, the load balancer-generated cookie is considered stale. The range is 1 second to 1 week (604800 seconds). The default value is 1 day (86400 seconds).</p> </li> </ul>"
}
},
"TargetGroupAttributeValue": {
@ -1175,7 +1225,7 @@
"TargetHealthReasonEnum": {
"base": null,
"refs": {
"TargetHealth$Reason": "<p>The reason code. If the target state is <code>healthy</code>, a reason code is not provided.</p> <p>If the target state is <code>initial</code>, the reason code can be one of the following values:</p> <ul> <li> <p> <code>Elb.RegistrationInProgress</code> - The target is in the process of being registered with the load balancer.</p> </li> <li> <p> <code>Elb.InitialHealthChecking</code> - The load balancer is still sending the target the minimum number of health checks required to determine its health status.</p> </li> </ul> <p>If the target state is <code>unhealthy</code>, the reason code can be one of the following values:</p> <ul> <li> <p> <code>Target.ResponseCodeMismatch</code> - The health checks did not return an expected HTTP code.</p> </li> <li> <p> <code>Target.Timeout</code> - The health check requests timed out.</p> </li> <li> <p> <code>Target.FailedHealthChecks</code> - The health checks failed because the connection to the target timed out, the target response was malformed, or the target failed the health check for an unknown reason.</p> </li> <li> <p> <code>Elb.InternalError</code> - The health checks failed due to an internal error.</p> </li> </ul> <p>If the target state is <code>unused</code>, the reason code can be one of the following values:</p> <ul> <li> <p> <code>Target.NotRegistered</code> - The target is not registered with the target group.</p> </li> <li> <p> <code>Target.NotInUse</code> - The target group is not used by any load balancer or the target is in an Availability Zone that is not enabled for its load balancer.</p> </li> <li> <p> <code>Target.InvalidState</code> - The target is in the stopped or terminated state.</p> </li> </ul> <p>If the target state is <code>draining</code>, the reason code can be the following value:</p> <ul> <li> <p> <code>Target.DeregistrationInProgress</code> - The target is in the process of being deregistered and the deregistration delay period has not expired.</p> </li> </ul>"
"TargetHealth$Reason": "<p>The reason code. If the target state is <code>healthy</code>, a reason code is not provided.</p> <p>If the target state is <code>initial</code>, the reason code can be one of the following values:</p> <ul> <li> <p> <code>Elb.RegistrationInProgress</code> - The target is in the process of being registered with the load balancer.</p> </li> <li> <p> <code>Elb.InitialHealthChecking</code> - The load balancer is still sending the target the minimum number of health checks required to determine its health status.</p> </li> </ul> <p>If the target state is <code>unhealthy</code>, the reason code can be one of the following values:</p> <ul> <li> <p> <code>Target.ResponseCodeMismatch</code> - The health checks did not return an expected HTTP code.</p> </li> <li> <p> <code>Target.Timeout</code> - The health check requests timed out.</p> </li> <li> <p> <code>Target.FailedHealthChecks</code> - The health checks failed because the connection to the target timed out, the target response was malformed, or the target failed the health check for an unknown reason.</p> </li> <li> <p> <code>Elb.InternalError</code> - The health checks failed due to an internal error.</p> </li> </ul> <p>If the target state is <code>unused</code>, the reason code can be one of the following values:</p> <ul> <li> <p> <code>Target.NotRegistered</code> - The target is not registered with the target group.</p> </li> <li> <p> <code>Target.NotInUse</code> - The target group is not used by any load balancer or the target is in an Availability Zone that is not enabled for its load balancer.</p> </li> <li> <p> <code>Target.IpUnusable</code> - The target IP address is reserved for use by a load balancer.</p> </li> <li> <p> <code>Target.InvalidState</code> - The target is in the stopped or terminated state.</p> </li> </ul> <p>If the target state is <code>draining</code>, the reason code can be the following value:</p> <ul> <li> <p> <code>Target.DeregistrationInProgress</code> - The target is in the process of being deregistered and the deregistration delay period has not expired.</p> </li> </ul>"
}
},
"TargetHealthStateEnum": {
@ -1187,7 +1237,14 @@
"TargetId": {
"base": null,
"refs": {
"TargetDescription$Id": "<p>The ID of the target.</p>"
"TargetDescription$Id": "<p>The ID of the target. If the target type of the target group is <code>instance</code>, specify an instance ID. If the target type is <code>ip</code>, specify an IP address.</p>"
}
},
"TargetTypeEnum": {
"base": null,
"refs": {
"CreateTargetGroupInput$TargetType": "<p>The type of target that you must specify when registering targets with this target group. The possible values are <code>instance</code> (targets are specified by instance ID) or <code>ip</code> (targets are specified by IP address). The default is <code>instance</code>. Note that you can't specify targets for a target group using both instance IDs and IP addresses.</p> <p>If the target type is <code>ip</code>, specify IP addresses from the subnets of the virtual private cloud (VPC) for the target group, the RFC 1918 range (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16), and the RFC 6598 range (100.64.0.0/10). You can't specify publicly routable IP addresses.</p>",
"TargetGroup$TargetType": "<p>The type of target that you must specify when registering targets with this target group. The possible values are <code>instance</code> (targets are specified by instance ID) or <code>ip</code> (targets are specified by IP address).</p>"
}
},
"TooManyCertificatesException": {
@ -1246,7 +1303,8 @@
"ZoneName": {
"base": null,
"refs": {
"AvailabilityZone$ZoneName": "<p>The name of the Availability Zone.</p>"
"AvailabilityZone$ZoneName": "<p>The name of the Availability Zone.</p>",
"TargetDescription$AvailabilityZone": "<p>The Availability Zone where the IP address is to be registered. Specify <code>all</code> to register an IP address outside the target group VPC with all Availability Zones that are enabled for the load balancer.</p> <p>If the IP address is in a subnet of the VPC for the target group, the Availability Zone is automatically detected and this parameter is optional.</p> <p>This parameter is not supported if the target type of the target group is <code>instance</code>.</p>"
}
}
}

View file

@ -59,6 +59,42 @@
"state": "success"
}
]
},
"TargetInService":{
"delay":15,
"maxAttempts":40,
"operation":"DescribeTargetHealth",
"acceptors":[
{
"argument":"TargetHealthDescriptions[].TargetHealth.State",
"expected":"healthy",
"matcher":"pathAll",
"state":"success"
},
{
"matcher": "error",
"expected": "InvalidInstance",
"state": "retry"
}
]
},
"TargetDeregistered": {
"delay": 15,
"maxAttempts": 40,
"operation": "DescribeTargetHealth",
"acceptors": [
{
"matcher": "error",
"expected": "InvalidTarget",
"state": "success"
},
{
"argument":"TargetHealthDescriptions[].TargetHealth.State",
"expected":"unused",
"matcher":"pathAll",
"state":"success"
}
]
}
}
}