Updates SDK to v2.644.0

aws · Mar 23, 2020 · 2f5261f · 2f5261f
1 parent 46b36d1
commit 2f5261f
Show file tree

Hide file tree

Showing 16 changed files with 146 additions and 125 deletions.
diff --git a/.changes/2.644.0.json b/.changes/2.644.0.json
@@ -0,0 +1,17 @@
+[
+    {
+        "type": "feature",
+        "category": "ApiGatewayV2",
+        "description": "Documentation updates to reflect that the default timeout for integrations is now 30 seconds for HTTP APIs."
+    },
+    {
+        "type": "feature",
+        "category": "EC2",
+        "description": "Add EC2ThrottledException to throttledError"
+    },
+    {
+        "type": "feature",
+        "category": "EKS",
+        "description": "Adding new error code IamLimitExceeded for Nodegroups in EKS"
+    }
+]
diff --git a/.changes/next-release/feature-EC2-0ecd30a7.json b/.changes/next-release/feature-EC2-0ecd30a7.json
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,7 +1,12 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.643.0-->
+<!--LATEST=2.644.0-->
 <!--ENTRYINSERT-->
 
+## 2.644.0
+* feature: ApiGatewayV2: Documentation updates to reflect that the default timeout for integrations is now 30 seconds for HTTP APIs.
+* feature: EC2: Add EC2ThrottledException to throttledError
+* feature: EKS: Adding new error code IamLimitExceeded for Nodegroups in EKS
+
 ## 2.643.0
 * feature: ServiceCatalog: Added "productId" and "portfolioId" to responses from CreateConstraint, UpdateConstraint, ListConstraintsForPortfolio, and DescribeConstraint APIs
 

diff --git a/README.md b/README.md
@@ -25,7 +25,7 @@ version.
 To use the SDK in the browser, simply add the following script tag to your
 HTML pages:
 
-    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.643.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.644.0.min.js"></script>
 
 You can also build a custom browser SDK with your specified set of AWS services.
 This can allow you to reduce the SDK's size, specify different API versions of

diff --git a/apis/apigatewayv2-2018-11-29.normal.json b/apis/apigatewayv2-2018-11-29.normal.json
@@ -2822,9 +2822,9 @@
           "documentation": "<p>The template selection expression for the integration.</p>"
         },
         "TimeoutInMillis": {
-          "shape": "IntegerWithLengthBetween50And29000",
+          "shape": "IntegerWithLengthBetween50And30000",
           "locationName": "timeoutInMillis",
-          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds for WebSocket APIs. The default value is 5,000 milliseconds, or 5 seconds for HTTP APIs.</p>"
+          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds for WebSocket APIs and between 50 and 30,000 milliseconds for HTTP APIs. The default timeout is 29 seconds for WebSocket APIs and 30 seconds for HTTP APIs.</p>"
         },
         "TlsConfig": {
           "shape": "TlsConfigInput",
@@ -2922,9 +2922,9 @@
           "documentation": "<p>The template selection expression for the integration. Supported only for WebSocket APIs.</p>"
         },
         "TimeoutInMillis": {
-          "shape": "IntegerWithLengthBetween50And29000",
+          "shape": "IntegerWithLengthBetween50And30000",
           "locationName": "timeoutInMillis",
-          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds for WebSocket APIs. The default value is 5,000 milliseconds, or 5 seconds for HTTP APIs.</p>"
+          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds for WebSocket APIs and between 50 and 30,000 milliseconds for HTTP APIs. The default timeout is 29 seconds for WebSocket APIs and 30 seconds for HTTP APIs.</p>"
         },
         "TlsConfig": {
           "shape": "TlsConfig",
@@ -4599,9 +4599,9 @@
           "documentation": "<p>The template selection expression for the integration. Supported only for WebSocket APIs.</p>"
         },
         "TimeoutInMillis": {
-          "shape": "IntegerWithLengthBetween50And29000",
+          "shape": "IntegerWithLengthBetween50And30000",
           "locationName": "timeoutInMillis",
-          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds for WebSocket APIs. The default value is 5,000 milliseconds, or 5 seconds for HTTP APIs.</p>"
+          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds for WebSocket APIs and between 50 and 30,000 milliseconds for HTTP APIs. The default timeout is 29 seconds for WebSocket APIs and 30 seconds for HTTP APIs.</p>"
         },
         "TlsConfig": {
           "shape": "TlsConfig",
@@ -5497,11 +5497,11 @@
       "min": 0,
       "max": 3600
     },
-    "IntegerWithLengthBetween50And29000": {
+    "IntegerWithLengthBetween50And30000": {
       "type": "integer",
-      "documentation": "<p>An integer with a value between [50-29000].</p>",
+      "documentation": "<p>An integer with a value between [50-30000].</p>",
       "min": 50,
-      "max": 29000
+      "max": 30000
     },
     "IntegerWithLengthBetweenMinus1And86400": {
       "type": "integer",
@@ -5593,9 +5593,9 @@
           "documentation": "<p>The template selection expression for the integration. Supported only for WebSocket APIs.</p>"
         },
         "TimeoutInMillis": {
-          "shape": "IntegerWithLengthBetween50And29000",
+          "shape": "IntegerWithLengthBetween50And30000",
           "locationName": "timeoutInMillis",
-          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds for WebSocket APIs. The default value is 5,000 milliseconds, or 5 seconds for HTTP APIs.</p>"
+          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds for WebSocket APIs and between 50 and 30,000 milliseconds for HTTP APIs. The default timeout is 29 seconds for WebSocket APIs and 30 seconds for HTTP APIs.</p>"
         },
         "TlsConfig": {
           "shape": "TlsConfig",
@@ -6778,9 +6778,9 @@
           "documentation": "<p>The template selection expression for the integration.</p>"
         },
         "TimeoutInMillis": {
-          "shape": "IntegerWithLengthBetween50And29000",
+          "shape": "IntegerWithLengthBetween50And30000",
           "locationName": "timeoutInMillis",
-          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds for WebSocket APIs. The default value is 5,000 milliseconds, or 5 seconds for HTTP APIs.</p>"
+          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds for WebSocket APIs and between 50 and 30,000 milliseconds for HTTP APIs. The default timeout is 29 seconds for WebSocket APIs and 30 seconds for HTTP APIs.</p>"
         },
         "TlsConfig": {
           "shape": "TlsConfigInput",
@@ -6878,9 +6878,9 @@
           "documentation": "<p>The template selection expression for the integration. Supported only for WebSocket APIs.</p>"
         },
         "TimeoutInMillis": {
-          "shape": "IntegerWithLengthBetween50And29000",
+          "shape": "IntegerWithLengthBetween50And30000",
           "locationName": "timeoutInMillis",
-          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds for WebSocket APIs. The default value is 5,000 milliseconds, or 5 seconds for HTTP APIs.</p>"
+          "documentation": "<p>Custom timeout between 50 and 29,000 milliseconds for WebSocket APIs and between 50 and 30,000 milliseconds for HTTP APIs. The default timeout is 29 seconds for WebSocket APIs and 30 seconds for HTTP APIs.</p>"
         },
         "TlsConfig": {
           "shape": "TlsConfig",

diff --git a/apis/eks-2017-11-01.normal.json b/apis/eks-2017-11-01.normal.json
@@ -150,7 +150,7 @@
           "shape": "ServiceUnavailableException"
         }
       ],
-      "documentation": "<p>Deletes the Amazon EKS cluster control plane.</p> <p>If you have active services in your cluster that are associated with a load balancer, you must delete those services before deleting the cluster so that the load balancers are deleted properly. Otherwise, you can have orphaned resources in your VPC that prevent you from being able to delete the VPC. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/delete-cluster.html\">Deleting a Cluster</a> in the <i>Amazon EKS User Guide</i>.</p> <p>If you have managed node groups or Fargate profiles attached to the cluster, you must delete them first. For more information, see <a>DeleteNodegroup</a> and<a>DeleteFargateProfile</a>.</p>"
+      "documentation": "<p>Deletes the Amazon EKS cluster control plane.</p> <p>If you have active services in your cluster that are associated with a load balancer, you must delete those services before deleting the cluster so that the load balancers are deleted properly. Otherwise, you can have orphaned resources in your VPC that prevent you from being able to delete the VPC. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/delete-cluster.html\">Deleting a Cluster</a> in the <i>Amazon EKS User Guide</i>.</p> <p>If you have managed node groups or Fargate profiles attached to the cluster, you must delete them first. For more information, see <a>DeleteNodegroup</a> and <a>DeleteFargateProfile</a>.</p>"
     },
     "DeleteFargateProfile": {
       "name": "DeleteFargateProfile",
@@ -926,7 +926,7 @@
         },
         "nodeRole": {
           "shape": "String",
-          "documentation": "<p>The IAM role associated with your node group. The Amazon EKS worker node <code>kubelet</code> daemon makes calls to AWS APIs on your behalf. Worker nodes receive permissions for these API calls through an IAM instance profile and associated policies. Before you can launch worker nodes and register them into a cluster, you must create an IAM role for those worker nodes to use when they are launched. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/worker_node_IAM_role.html\">Amazon EKS Worker Node IAM Role</a> in the <i> <i>Amazon EKS User Guide</i> </i>.</p>"
+          "documentation": "<p>The Amazon Resource Name (ARN) of the IAM role to associate with your node group. The Amazon EKS worker node <code>kubelet</code> daemon makes calls to AWS APIs on your behalf. Worker nodes receive permissions for these API calls through an IAM instance profile and associated policies. Before you can launch worker nodes and register them into a cluster, you must create an IAM role for those worker nodes to use when they are launched. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/worker_node_IAM_role.html\">Amazon EKS Worker Node IAM Role</a> in the <i> <i>Amazon EKS User Guide</i> </i>.</p>"
         },
         "labels": {
           "shape": "labelsMap",
@@ -1687,6 +1687,7 @@
         "Ec2LaunchTemplateVersionMismatch",
         "Ec2SubnetNotFound",
         "IamInstanceProfileNotFound",
+        "IamLimitExceeded",
         "IamNodeRoleNotFound",
         "AsgInstanceLaunchFailures",
         "InstanceLimitExceeded",