Updates SDK to v2.1134.0

.changes/2.1134.0.json

@@ -0,0 +1,32 @@
+[
+    {
+        "type": "feature",
+        "category": "EC2",
+        "description": "This release introduces a target type Gateway Load Balancer Endpoint for mirrored traffic. Customers can now specify GatewayLoadBalancerEndpoint option during the creation of a traffic mirror target."
+    },
+    {
+        "type": "feature",
+        "category": "Kendra",
+        "description": "Amazon Kendra now provides a data source connector for Jira. For more information, see https://docs.aws.amazon.com/kendra/latest/dg/data-source-jira.html"
+    },
+    {
+        "type": "feature",
+        "category": "Lambda",
+        "description": "Lambda releases NodeJs 16 managed runtime to be available in all commercial regions."
+    },
+    {
+        "type": "feature",
+        "category": "Lightsail",
+        "description": "This release adds support to include inactive database bundles in the response of the GetRelationalDatabaseBundles request."
+    },
+    {
+        "type": "feature",
+        "category": "SSMIncidents",
+        "description": "Adding support for dynamic SSM Runbook parameter values. Updating validation pattern for engagements. Adding ConflictException to UpdateReplicationSet API contract."
+    },
+    {
+        "type": "feature",
+        "category": "WorkSpaces",
+        "description": "Increased the character limit of the login message from 600 to 850 characters."
+    }
+]

CHANGELOG.md

@@ -1,7 +1,15 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.1133.0-->
+<!--LATEST=2.1134.0-->
 <!--ENTRYINSERT-->
 
+## 2.1134.0
+* feature: EC2: This release introduces a target type Gateway Load Balancer Endpoint for mirrored traffic. Customers can now specify GatewayLoadBalancerEndpoint option during the creation of a traffic mirror target.
+* feature: Kendra: Amazon Kendra now provides a data source connector for Jira. For more information, see https://docs.aws.amazon.com/kendra/latest/dg/data-source-jira.html
+* feature: Lambda: Lambda releases NodeJs 16 managed runtime to be available in all commercial regions.
+* feature: Lightsail: This release adds support to include inactive database bundles in the response of the GetRelationalDatabaseBundles request.
+* feature: SSMIncidents: Adding support for dynamic SSM Runbook parameter values. Updating validation pattern for engagements. Adding ConflictException to UpdateReplicationSet API contract.
+* feature: WorkSpaces: Increased the character limit of the login message from 600 to 850 characters.
+
 ## 2.1133.0
 * feature: EC2: This release updates AWS PrivateLink APIs to support IPv6 for PrivateLink Services and Endpoints of type 'Interface'.
 

README.md

@@ -29,7 +29,7 @@ For release notes, see the [CHANGELOG](https://github.com/aws/aws-sdk-js/blob/ma
 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.1133.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.1134.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

apis/ec2-2016-11-15.min.json

@@ -3755,7 +3755,8 @@
           },
           "ClientToken": {
             "idempotencyToken": true
-          }
+          },
+          "GatewayLoadBalancerEndpointId": {}
         }
       },
       "output": {
@@ -26467,6 +26468,9 @@
         "Tags": {
           "shape": "Ss",
           "locationName": "tagSet"
+        },
+        "GatewayLoadBalancerEndpointId": {
+          "locationName": "gatewayLoadBalancerEndpointId"
         }
       }
     },

apis/ec2-2016-11-15.normal.json

@@ -1378,7 +1378,7 @@
       "output": {
         "shape": "CreateTrafficMirrorTargetResult"
       },
-      "documentation": "<p>Creates a target for your Traffic Mirror session.</p> <p>A Traffic Mirror target is the destination for mirrored traffic. The Traffic Mirror source and the Traffic Mirror target (monitoring appliances) can be in the same VPC, or in different VPCs connected via VPC peering or a transit gateway.</p> <p>A Traffic Mirror target can be a network interface, or a Network Load Balancer.</p> <p>To use the target in a Traffic Mirror session, use <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateTrafficMirrorSession.htm\">CreateTrafficMirrorSession</a>.</p>"
+      "documentation": "<p>Creates a target for your Traffic Mirror session.</p> <p>A Traffic Mirror target is the destination for mirrored traffic. The Traffic Mirror source and the Traffic Mirror target (monitoring appliances) can be in the same VPC, or in different VPCs connected via VPC peering or a transit gateway.</p> <p>A Traffic Mirror target can be a network interface, a Network Load Balancer, or a Gateway Load Balancer endpoint.</p> <p>To use the target in a Traffic Mirror session, use <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateTrafficMirrorSession.htm\">CreateTrafficMirrorSession</a>.</p>"
     },
     "CreateTransitGateway": {
       "name": "CreateTransitGateway",
@@ -14893,6 +14893,10 @@
           "shape": "String",
           "documentation": "<p>Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Run_Instance_Idempotency.html\">How to ensure idempotency</a>.</p>",
           "idempotencyToken": true
+        },
+        "GatewayLoadBalancerEndpointId": {
+          "shape": "VpcEndpointId",
+          "documentation": "<p>The ID of the Gateway Load Balancer endpoint.</p>"
         }
       }
     },
@@ -50503,6 +50507,11 @@
           "shape": "TagList",
           "documentation": "<p>The tags assigned to the Traffic Mirror target.</p>",
           "locationName": "tagSet"
+        },
+        "GatewayLoadBalancerEndpointId": {
+          "shape": "String",
+          "documentation": "<p>The ID of the Gateway Load Balancer endpoint.</p>",
+          "locationName": "gatewayLoadBalancerEndpointId"
         }
       },
       "documentation": "<p>Describes a Traffic Mirror target.</p>"
@@ -50528,7 +50537,8 @@
       "type": "string",
       "enum": [
         "network-interface",
-        "network-load-balancer"
+        "network-load-balancer",
+        "gateway-load-balancer-endpoint"
       ]
     },
     "TrafficMirroringMaxResults": {

apis/finspace-data-2020-07-13.normal.json

@@ -2413,7 +2413,7 @@
           "documentation": "<p>Permission for a resource.</p>"
         }
       },
-      "documentation": "<p>Resource permission for a dataset. When you create a dataset, all the other members of the same user group inherit access to the dataset. You can only create a dataset if your user group has application permission for Create Datasets.</p> <p>The following is a list of valid dataset permissions that you can apply: </p> <ul> <li> <p> <code>ViewDatasetDetails</code> </p> </li> <li> <p> <code>ReadDatasetDetails</code> </p> </li> <li> <p> <code>AddDatasetData</code> </p> </li> <li> <p> <code>CreateSnapshot</code> </p> </li> <li> <p> <code>EditDatasetMetadata</code> </p> </li> <li> <p> <code>DeleteDataset</code> </p> </li> </ul> <p>For more information on the dataset permissions, see <a href=\"https://docs.aws.amazon.com/finspace/latest/userguide/managing-user-permissions.html#supported-dataset-permissions\">Supported Dataset Permissions</a> in the FinSpace User Guide.</p>"
+      "documentation": "<p>Resource permission for a dataset. When you create a dataset, all the other members of the same user group inherit access to the dataset. You can only create a dataset if your user group has application permission for Create Datasets.</p> <p>The following is a list of valid dataset permissions that you can apply: </p> <ul> <li> <p> <code>ViewDatasetDetails</code> </p> </li> <li> <p> <code>ReadDatasetDetails</code> </p> </li> <li> <p> <code>AddDatasetData</code> </p> </li> <li> <p> <code>CreateDataView</code> </p> </li> <li> <p> <code>EditDatasetMetadata</code> </p> </li> <li> <p> <code>DeleteDataset</code> </p> </li> </ul> <p>For more information on the dataset permissions, see <a href=\"https://docs.aws.amazon.com/finspace/latest/userguide/managing-user-permissions.html#supported-dataset-permissions\">Supported Dataset Permissions</a> in the FinSpace User Guide.</p>"
     },
     "ResourcePermissionsList": {
       "type": "list",

apis/iot-2015-05-28.normal.json

@@ -10245,7 +10245,7 @@
         },
         "targetSelection": {
           "shape": "TargetSelection",
-          "documentation": "<p>Specifies whether the job will continue to run (CONTINUOUS), or will be complete after all those things specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing when a change is detected in a target. For example, a job will run on a thing when the thing is added to a target group, even after the job was completed by all things originally in the group.</p>"
+          "documentation": "<p>Specifies whether the job will continue to run (CONTINUOUS), or will be complete after all those things specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing when a change is detected in a target. For example, a job will run on a thing when the thing is added to a target group, even after the job was completed by all things originally in the group.</p> <note> <p>We recommend that you use continuous jobs instead of snapshot jobs for dynamic thing group targets. By using continuous jobs, devices that join the group receive the job execution even after the job has been created.</p> </note>"
         },
         "jobExecutionsRolloutConfig": {
           "shape": "JobExecutionsRolloutConfig",
@@ -10277,7 +10277,7 @@
         },
         "documentParameters": {
           "shape": "ParameterMap",
-          "documentation": "<p>Parameters of a managed template that you can specify to create the job document.</p>"
+          "documentation": "<p>Parameters of an Amazon Web Services managed template that you can specify to create the job document.</p> <note> <p> <code>documentParameters</code> can only be used when creating jobs from Amazon Web Services managed templates. This parameter can't be used with custom job templates or to create jobs from them.</p> </note>"
         }
       }
     },
@@ -11149,11 +11149,11 @@
         },
         "hashAlgorithm": {
           "shape": "HashAlgorithm",
-          "documentation": "<p>The hash algorithm used to code sign the file.</p>"
+          "documentation": "<p>The hash algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses <code>SHA256</code> or <code>SHA1</code>, so you can pass either of them based on which was used for generating the signature.</p>"
         },
         "signatureAlgorithm": {
           "shape": "SignatureAlgorithm",
-          "documentation": "<p>The signature algorithm used to code sign the file.</p>"
+          "documentation": "<p>The signature algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses <code>ECDSA</code> or <code>RSA</code>, so you can pass either of them based on which was used for generating the signature.</p>"
         }
       },
       "documentation": "<p>Describes a custom method used to code sign a file.</p>"
@@ -12677,7 +12677,7 @@
         },
         "documentParameters": {
           "shape": "DocumentParameters",
-          "documentation": "<p>A map of key-value pairs that you can use as guidance to specify the inputs for creating a job from a managed template.</p>"
+          "documentation": "<p>A map of key-value pairs that you can use as guidance to specify the inputs for creating a job from a managed template.</p> <note> <p> <code>documentParameters</code> can only be used when creating jobs from Amazon Web Services managed templates. This parameter can't be used with custom job templates or to create jobs from them.</p> </note>"
         },
         "document": {
           "shape": "JobDocument",
@@ -13602,7 +13602,7 @@
           "documentation": "<p>Specifies whether a pattern that needs to be replaced in a managed template job document schema is optional or required.</p>"
         }
       },
-      "documentation": "<p>A map of key-value pairs containing the patterns that need to be replaced in a managed template job document schema. You can use the description of each key as a guidance to specify the inputs during runtime when creating a job.</p>"
+      "documentation": "<p>A map of key-value pairs containing the patterns that need to be replaced in a managed template job document schema. You can use the description of each key as a guidance to specify the inputs during runtime when creating a job.</p> <note> <p> <code>documentParameters</code> can only be used when creating jobs from Amazon Web Services managed templates. This parameter can't be used with custom job templates or to create jobs from them.</p> </note>"
     },
     "DocumentParameters": {
       "type": "list",
@@ -14993,7 +14993,7 @@
         },
         "targetSelection": {
           "shape": "TargetSelection",
-          "documentation": "<p>Specifies whether the job will continue to run (CONTINUOUS), or will be complete after all those things specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing when a change is detected in a target. For example, a job will run on a device when the thing representing the device is added to a target group, even after the job was completed by all things originally in the group. </p>"
+          "documentation": "<p>Specifies whether the job will continue to run (CONTINUOUS), or will be complete after all those things specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing when a change is detected in a target. For example, a job will run on a device when the thing representing the device is added to a target group, even after the job was completed by all things originally in the group. </p> <note> <p>We recommend that you use continuous jobs instead of snapshot jobs for dynamic thing group targets. By using continuous jobs, devices that join the group receive the job execution even after the job has been created.</p> </note>"
         },
         "status": {
           "shape": "JobStatus",
@@ -15065,7 +15065,7 @@
         },
         "documentParameters": {
           "shape": "ParameterMap",
-          "documentation": "<p>A key-value map that pairs the patterns that need to be replaced in a managed template job document schema. You can use the description of each key as a guidance to specify the inputs during runtime when creating a job.</p>"
+          "documentation": "<p>A key-value map that pairs the patterns that need to be replaced in a managed template job document schema. You can use the description of each key as a guidance to specify the inputs during runtime when creating a job.</p> <note> <p> <code>documentParameters</code> can only be used when creating jobs from Amazon Web Services managed templates. This parameter can't be used with custom job templates or to create jobs from them.</p> </note>"
         },
         "isConcurrent": {
           "shape": "BooleanWrapperObject"
@@ -15343,7 +15343,7 @@
         },
         "targetSelection": {
           "shape": "TargetSelection",
-          "documentation": "<p>Specifies whether the job will continue to run (CONTINUOUS), or will be complete after all those things specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing when a change is detected in a target. For example, a job will run on a thing when the thing is added to a target group, even after the job was completed by all things originally in the group.</p>"
+          "documentation": "<p>Specifies whether the job will continue to run (CONTINUOUS), or will be complete after all those things specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing when a change is detected in a target. For example, a job will run on a thing when the thing is added to a target group, even after the job was completed by all things originally in the group.</p> <note> <p>We recommend that you use continuous jobs instead of snapshot jobs for dynamic thing group targets. By using continuous jobs, devices that join the group receive the job execution even after the job has been created.</p> </note>"
         },
         "status": {
           "shape": "JobStatus",
@@ -16499,7 +16499,7 @@
         },
         "targetSelection": {
           "shape": "TargetSelection",
-          "documentation": "<p>Specifies whether the job will continue to run (CONTINUOUS), or will be complete after all those things specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing when a change is detected in a target. For example, a job will run on a thing when the thing is added to a target group, even after the job was completed by all things originally in the group. </p>",
+          "documentation": "<p>Specifies whether the job will continue to run (CONTINUOUS), or will be complete after all those things specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing when a change is detected in a target. For example, a job will run on a thing when the thing is added to a target group, even after the job was completed by all things originally in the group. </p> <note> <p>We recommend that you use continuous jobs instead of snapshot jobs for dynamic thing group targets. By using continuous jobs, devices that join the group receive the job execution even after the job has been created.</p> </note>",
           "location": "querystring",
           "locationName": "targetSelection"
         },