Elastic Load Balancing Update: Application Load Balancer (ALB) now supports the gRPC protocol-version. With this release, customers can use ALB to route and load balance gRPC traffic between gRPC enabled clients and microservices.

Author: AWS

.changes/next-release/feature-ElasticLoadBalancing-f672fa2.json

@@ -0,0 +1,6 @@
+{
+    "type": "feature",
+    "category": "Elastic Load Balancing",
+    "contributor": "",
+    "description": "Application Load Balancer (ALB) now supports the gRPC protocol-version. With this release, customers can use ALB to route and load balance gRPC traffic between gRPC enabled clients and microservices."
+}

services/elasticloadbalancingv2/src/main/resources/codegen-resources/service-2.json

@@ -1079,7 +1079,7 @@
         },
         "DefaultActions":{
           "shape":"Actions",
-          "documentation":"<p>The actions for the default rule. The rule must include one forward action or one or more fixed-response actions.</p> <p>If the action type is <code>forward</code>, you specify one or more target groups. The protocol of the target group must be HTTP or HTTPS for an Application Load Balancer. The protocol of the target group must be TCP, TLS, UDP, or TCP_UDP for a Network Load Balancer.</p> <p>[HTTPS listeners] If the action type is <code>authenticate-oidc</code>, you authenticate users through an identity provider that is OpenID Connect (OIDC) compliant.</p> <p>[HTTPS listeners] If the action type is <code>authenticate-cognito</code>, you authenticate users through the user pools supported by Amazon Cognito.</p> <p>[Application Load Balancer] If the action type is <code>redirect</code>, you redirect specified client requests from one URL to another.</p> <p>[Application Load Balancer] If the action type is <code>fixed-response</code>, you drop specified client requests and return a custom HTTP response.</p>"
+          "documentation":"<p>The actions for the default rule.</p>"
         },
         "AlpnPolicy":{
           "shape":"AlpnPolicyName",
@@ -1166,15 +1166,15 @@
         },
         "Conditions":{
           "shape":"RuleConditionList",
-          "documentation":"<p>The conditions. Each rule can optionally include up to one of each of the following conditions: <code>http-request-method</code>, <code>host-header</code>, <code>path-pattern</code>, and <code>source-ip</code>. Each rule can also optionally include one or more of each of the following conditions: <code>http-header</code> and <code>query-string</code>.</p>"
+          "documentation":"<p>The conditions.</p>"
         },
         "Priority":{
           "shape":"RulePriority",
           "documentation":"<p>The rule priority. A listener can't have multiple rules with the same priority.</p>"
         },
         "Actions":{
           "shape":"Actions",
-          "documentation":"<p>The actions. Each rule must include exactly one of the following types of actions: <code>forward</code>, <code>fixed-response</code>, or <code>redirect</code>, and it must be the last action to be performed.</p> <p>If the action type is <code>forward</code>, you specify one or more target groups. The protocol of the target group must be HTTP or HTTPS for an Application Load Balancer. The protocol of the target group must be TCP, TLS, UDP, or TCP_UDP for a Network Load Balancer.</p> <p>[HTTPS listeners] If the action type is <code>authenticate-oidc</code>, you authenticate users through an identity provider that is OpenID Connect (OIDC) compliant.</p> <p>[HTTPS listeners] If the action type is <code>authenticate-cognito</code>, you authenticate users through the user pools supported by Amazon Cognito.</p> <p>[Application Load Balancer] If the action type is <code>redirect</code>, you redirect specified client requests from one URL to another.</p> <p>[Application Load Balancer] If the action type is <code>fixed-response</code>, you drop specified client requests and return a custom HTTP response.</p>"
+          "documentation":"<p>The actions.</p>"
         },
         "Tags":{
           "shape":"TagList",
@@ -1203,6 +1203,10 @@
           "shape":"ProtocolEnum",
           "documentation":"<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 protocols are TCP, TLS, UDP, or TCP_UDP. A TCP_UDP listener must be associated with a TCP_UDP target group. If the target is a Lambda function, this parameter does not apply.</p>"
         },
+        "ProtocolVersion":{
+          "shape":"ProtocolVersion",
+          "documentation":"<p>[HTTP/HTTPS protocol] The protocol version. Specify <code>GRPC</code> to send requests to targets using gRPC. Specify <code>HTTP2</code> to send requests to targets using HTTP/2. The default is <code>HTTP1</code>, which sends requests to targets using HTTP/1.1.</p>"
+        },
         "Port":{
           "shape":"Port",
           "documentation":"<p>The port on which the targets receive traffic. This port is used unless you specify a port override when registering the target. If the target is a Lambda function, this parameter does not apply.</p>"
@@ -1225,7 +1229,7 @@
         },
         "HealthCheckPath":{
           "shape":"Path",
-          "documentation":"<p>[HTTP/HTTPS health checks] The ping path that is the destination on the targets for health checks. The default is /.</p>"
+          "documentation":"<p>[HTTP/HTTPS health checks] The destination for health checks on the targets.</p> <p>[HTTP1 or HTTP2 protocol version] The ping path. The default is /.</p> <p>[GRPC protocol version] The path of a custom health check method with the format /package.service/method. The default is /AWS.ALB/healthcheck.</p>"
         },
         "HealthCheckIntervalSeconds":{
           "shape":"HealthCheckIntervalSeconds",
@@ -1245,7 +1249,7 @@
         },
         "Matcher":{
           "shape":"Matcher",
-          "documentation":"<p>[HTTP/HTTPS health checks] The HTTP codes to use when checking for a successful response from a target.</p>"
+          "documentation":"<p>[HTTP/HTTPS health checks] The HTTP or gRPC codes to use when checking for a successful response from a target.</p>"
         },
         "TargetType":{
           "shape":"TargetTypeEnum",
@@ -1759,6 +1763,7 @@
       },
       "documentation":"<p>Information about a forward action.</p>"
     },
+    "GrpcCode":{"type":"string"},
     "HealthCheckEnabled":{"type":"boolean"},
     "HealthCheckIntervalSeconds":{
       "type":"integer",
@@ -2171,14 +2176,17 @@
     "Marker":{"type":"string"},
     "Matcher":{
       "type":"structure",
-      "required":["HttpCode"],
       "members":{
         "HttpCode":{
           "shape":"HttpCode",
-          "documentation":"<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–399.</p>"
+          "documentation":"<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–399\".</p>"
+        },
+        "GrpcCode":{
+          "shape":"GrpcCode",
+          "documentation":"<p>You can specify values between 0 and 99. You can specify multiple values (for example, \"0,1\") or a range of values (for example, \"0-5\"). The default value is 12.</p>"
         }
       },
-      "documentation":"<p>Information to use when checking for a successful response from a target.</p>"
+      "documentation":"<p>The codes to use when checking for a successful response from a target. If the protocol version is gRPC, these are gRPC codes. Otherwise, these are HTTP codes.</p>"
     },
     "Max":{"type":"string"},
     "ModifyListenerInput":{
@@ -2207,7 +2215,7 @@
         },
         "DefaultActions":{
           "shape":"Actions",
-          "documentation":"<p>The actions for the default rule. The rule must include one forward action or one or more fixed-response actions.</p> <p>If the action type is <code>forward</code>, you specify one or more target groups. The protocol of the target group must be HTTP or HTTPS for an Application Load Balancer. The protocol of the target group must be TCP, TLS, UDP, or TCP_UDP for a Network Load Balancer.</p> <p>[HTTPS listeners] If the action type is <code>authenticate-oidc</code>, you authenticate users through an identity provider that is OpenID Connect (OIDC) compliant.</p> <p>[HTTPS listeners] If the action type is <code>authenticate-cognito</code>, you authenticate users through the user pools supported by Amazon Cognito.</p> <p>[Application Load Balancer] If the action type is <code>redirect</code>, you redirect specified client requests from one URL to another.</p> <p>[Application Load Balancer] If the action type is <code>fixed-response</code>, you drop specified client requests and return a custom HTTP response.</p>"
+          "documentation":"<p>The actions for the default rule.</p>"
         },
         "AlpnPolicy":{
           "shape":"AlpnPolicyName",
@@ -2260,11 +2268,11 @@
         },
         "Conditions":{
           "shape":"RuleConditionList",
-          "documentation":"<p>The conditions. Each rule can include zero or one of the following conditions: <code>http-request-method</code>, <code>host-header</code>, <code>path-pattern</code>, and <code>source-ip</code>, and zero or more of the following conditions: <code>http-header</code> and <code>query-string</code>.</p>"
+          "documentation":"<p>The conditions.</p>"
         },
         "Actions":{
           "shape":"Actions",
-          "documentation":"<p>The actions. Each rule must include exactly one of the following types of actions: <code>forward</code>, <code>fixed-response</code>, or <code>redirect</code>, and it must be the last action to be performed.</p> <p>If the action type is <code>forward</code>, you specify one or more target groups. The protocol of the target group must be HTTP or HTTPS for an Application Load Balancer. The protocol of the target group must be TCP, TLS, UDP, or TCP_UDP for a Network Load Balancer.</p> <p>[HTTPS listeners] If the action type is <code>authenticate-oidc</code>, you authenticate users through an identity provider that is OpenID Connect (OIDC) compliant.</p> <p>[HTTPS listeners] If the action type is <code>authenticate-cognito</code>, you authenticate users through the user pools supported by Amazon Cognito.</p> <p>[Application Load Balancer] If the action type is <code>redirect</code>, you redirect specified client requests from one URL to another.</p> <p>[Application Load Balancer] If the action type is <code>fixed-response</code>, you drop specified client requests and return a custom HTTP response.</p>"
+          "documentation":"<p>The actions.</p>"
         }
       }
     },
@@ -2321,15 +2329,15 @@
         },
         "HealthCheckPath":{
           "shape":"Path",
-          "documentation":"<p>[HTTP/HTTPS health checks] The ping path that is the destination for the health check request.</p>"
+          "documentation":"<p>[HTTP/HTTPS health checks] The destination for health checks on the targets.</p> <p>[HTTP1 or HTTP2 protocol version] The ping path. The default is /.</p> <p>[GRPC protocol version] The path of a custom health check method with the format /package.service/method. The default is /AWS.ALB/healthcheck.</p>"
         },
         "HealthCheckEnabled":{
           "shape":"HealthCheckEnabled",
           "documentation":"<p>Indicates whether health checks are enabled.</p>"
         },
         "HealthCheckIntervalSeconds":{
           "shape":"HealthCheckIntervalSeconds",
-          "documentation":"<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> <p>With Network Load Balancers, you can't modify this setting.</p>"
+          "documentation":"<p>The approximate amount of time, in seconds, between health checks of an individual target. For HTTP and HTTPS health checks, the range is 5 to 300 seconds. For TPC health checks, the supported values are 10 or 30 seconds.</p> <p>With Network Load Balancers, you can't modify this setting.</p>"
         },
         "HealthCheckTimeoutSeconds":{
           "shape":"HealthCheckTimeoutSeconds",
@@ -2341,11 +2349,11 @@
         },
         "UnhealthyThresholdCount":{
           "shape":"HealthCheckThresholdCount",
-          "documentation":"<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>"
+          "documentation":"<p>The number of consecutive health check failures required before considering the target unhealthy. For target groups with a protocol of TCP or TLS, this value must be the same as the healthy threshold count.</p>"
         },
         "Matcher":{
           "shape":"Matcher",
-          "documentation":"<p>[HTTP/HTTPS health checks] The HTTP codes to use when checking for a successful response from a target. The possible values are from 200 to 499. You can specify multiple values (for example, \"200,202\") or a range of values (for example, \"200-299\"). The default is 200.</p> <p>With Network Load Balancers, you can't modify this setting.</p>"
+          "documentation":"<p>[HTTP/HTTPS health checks] The HTTP or gRPC codes to use when checking for a successful response from a target.</p> <p>With Network Load Balancers, you can't modify this setting.</p>"
         }
       }
     },
@@ -2421,6 +2429,7 @@
         "TCP_UDP"
       ]
     },
+    "ProtocolVersion":{"type":"string"},
     "QueryStringConditionConfig":{
       "type":"structure",
       "members":{
@@ -2520,7 +2529,7 @@
         },
         "Targets":{
           "shape":"TargetDescriptions",
-          "documentation":"<p>The targets.</p> <p>To register a target by instance ID, specify the instance ID. To register a target by IP address, specify the IP address. To register a Lambda function, specify the ARN of the Lambda function.</p>"
+          "documentation":"<p>The targets.</p>"
         }
       }
     },
@@ -3031,11 +3040,11 @@
         },
         "HealthCheckPath":{
           "shape":"Path",
-          "documentation":"<p>The destination for the health check request.</p>"
+          "documentation":"<p>The destination for health checks on the targets.</p>"
         },
         "Matcher":{
           "shape":"Matcher",
-          "documentation":"<p>The HTTP codes to use when checking for a successful response from a target.</p>"
+          "documentation":"<p>The HTTP or gRPC codes to use when checking for a successful response from a target.</p>"
         },
         "LoadBalancerArns":{
           "shape":"LoadBalancerArns",
@@ -3044,6 +3053,10 @@
         "TargetType":{
           "shape":"TargetTypeEnum",
           "documentation":"<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>"
+        },
+        "ProtocolVersion":{
+          "shape":"ProtocolVersion",
+          "documentation":"<p>[HTTP/HTTPS protocol] The protocol version. The possible values are <code>GRPC</code>, <code>HTTP1</code>, and <code>HTTP2</code>.</p>"
         }
       },
       "documentation":"<p>Information about a target group.</p>"