Updates SDK to v2.1170.0

.changes/2.1170.0.json

@@ -0,0 +1,27 @@
+[
+    {
+        "type": "feature",
+        "category": "ChimeSDKMeetings",
+        "description": "Adds support for AppKeys and TenantIds in Amazon Chime SDK WebRTC sessions"
+    },
+    {
+        "type": "feature",
+        "category": "DMS",
+        "description": "New api to migrate event subscriptions to event bridge rules"
+    },
+    {
+        "type": "feature",
+        "category": "IoTWireless",
+        "description": "Adds 5 APIs: PutPositionConfiguration, GetPositionConfiguration, ListPositionConfigurations, UpdatePosition, GetPosition for the new Positioning Service feature which enables customers to configure solvers to calculate position of LoRaWAN devices, or specify position of LoRaWAN devices & gateways."
+    },
+    {
+        "type": "feature",
+        "category": "Iot",
+        "description": "This release adds support to register a CA certificate without having to provide a verification certificate. This also allows multiple AWS accounts to register the same CA in the same region."
+    },
+    {
+        "type": "feature",
+        "category": "SageMaker",
+        "description": "Heterogeneous clusters: the ability to launch training jobs with multiple instance types. This enables running component of the training job on the instance type that is most suitable for it. e.g. doing data processing and augmentation on CPU instances and neural network training on GPU instances"
+    }
+]

CHANGELOG.md

@@ -1,7 +1,14 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.1169.0-->
+<!--LATEST=2.1170.0-->
 <!--ENTRYINSERT-->
 
+## 2.1170.0
+* feature: ChimeSDKMeetings: Adds support for AppKeys and TenantIds in Amazon Chime SDK WebRTC sessions
+* feature: DMS: New api to migrate event subscriptions to event bridge rules
+* feature: IoTWireless: Adds 5 APIs: PutPositionConfiguration, GetPositionConfiguration, ListPositionConfigurations, UpdatePosition, GetPosition for the new Positioning Service feature which enables customers to configure solvers to calculate position of LoRaWAN devices, or specify position of LoRaWAN devices & gateways.
+* feature: Iot: This release adds support to register a CA certificate without having to provide a verification certificate. This also allows multiple AWS accounts to register the same CA in the same region.
+* feature: SageMaker: Heterogeneous clusters: the ability to launch training jobs with multiple instance types. This enables running component of the training job on the instance type that is most suitable for it. e.g. doing data processing and augmentation on CPU instances and neural network training on GPU instances
+
 ## 2.1169.0
 * feature: CloudFormation: My AWS Service (placeholder) - Add a new feature Account-level Targeting for StackSet operation
 * feature: Synthetics: This release introduces Group feature, which enables users to group cross-region canaries.

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.1169.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.1170.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/chime-sdk-meetings-2021-07-15.min.json

@@ -143,14 +143,17 @@
           "MeetingFeatures": {
             "shape": "Sq"
           },
-          "PrimaryMeetingId": {}
+          "PrimaryMeetingId": {},
+          "TenantIds": {
+            "shape": "Su"
+          }
         }
       },
       "output": {
         "type": "structure",
         "members": {
           "Meeting": {
-            "shape": "Sv"
+            "shape": "Sx"
           }
         }
       }
@@ -191,14 +194,17 @@
               "shape": "S4"
             }
           },
-          "PrimaryMeetingId": {}
+          "PrimaryMeetingId": {},
+          "TenantIds": {
+            "shape": "Su"
+          }
         }
       },
       "output": {
         "type": "structure",
         "members": {
           "Meeting": {
-            "shape": "Sv"
+            "shape": "Sx"
           },
           "Attendees": {
             "shape": "S9"
@@ -304,7 +310,7 @@
         "type": "structure",
         "members": {
           "Meeting": {
-            "shape": "Sv"
+            "shape": "Sx"
           }
         }
       }
@@ -567,7 +573,11 @@
         }
       }
     },
-    "Sv": {
+    "Su": {
+      "type": "list",
+      "member": {}
+    },
+    "Sx": {
       "type": "structure",
       "members": {
         "MeetingId": {},
@@ -594,7 +604,10 @@
         "MeetingFeatures": {
           "shape": "Sq"
         },
-        "PrimaryMeetingId": {}
+        "PrimaryMeetingId": {},
+        "TenantIds": {
+          "shape": "Su"
+        }
       }
     }
   }

apis/chime-sdk-meetings-2021-07-15.normal.json

@@ -84,7 +84,7 @@
           "shape": "ServiceUnavailableException"
         }
       ],
-      "documentation": "<p>Updates <code>AttendeeCapabilities</code> except the capabilities listed in an <code>ExcludedAttendeeIds</code> table.</p>"
+      "documentation": "<p>Updates <code>AttendeeCapabilities</code> except the capabilities listed in an <code>ExcludedAttendeeIds</code> table.</p> <note> <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see .</p> </note> <p>When using capabilities, be aware of these corner cases:</p> <ul> <li> <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability to receive and you set your <code>content</code> capability to not receive.</p> </li> <li> <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p> </li> <li> <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"
     },
     "CreateAttendee": {
       "name": "CreateAttendee",
@@ -496,7 +496,7 @@
           "shape": "ServiceUnavailableException"
         }
       ],
-      "documentation": "<p>The capabilties that you want to update.</p>"
+      "documentation": "<p>The capabilties that you want to update.</p> <note> <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see .</p> </note> <p>When using capabilities, be aware of these corner cases:</p> <ul> <li> <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability to receive and you set your <code>content</code> capability to not receive.</p> </li> <li> <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p> </li> <li> <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"
     }
   },
   "shapes": {
@@ -524,7 +524,7 @@
         },
         "Capabilities": {
           "shape": "AttendeeCapabilities",
-          "documentation": "<p>The capabilities (audio, video, or content) assigned to an attendee.</p>"
+          "documentation": "<p>The capabilities assigned to an attendee: audio, video, or content.</p> <note> <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see .</p> </note> <p>When using capabilities, be aware of these corner cases:</p> <ul> <li> <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability to receive and you set your <code>content</code> capability to not receive.</p> </li> <li> <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p> </li> <li> <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"
         }
       },
       "documentation": "<p>An Amazon Chime SDK meeting attendee. Includes a unique <code>AttendeeId</code> and <code>JoinToken</code>. The <code>JoinToken</code> allows a client to authenticate and join as the specified attendee. The <code>JoinToken</code> expires when the meeting ends, or when <a>DeleteAttendee</a> is called. After that, the attendee is unable to join the meeting. </p> <p>We recommend securely transferring each <code>JoinToken</code> from your server application to the client so that no other client has access to the token except for the one authorized to represent the attendee.</p>"
@@ -550,7 +550,7 @@
           "documentation": "<p>The content capability assigned to an attendee.</p>"
         }
       },
-      "documentation": "<p>The media capabilities of an attendee, including audio, video and content. </p>"
+      "documentation": "<p>The media capabilities of an attendee: audio, video, or content. </p> <note> <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see .</p> </note> <p>When using capabilities, be aware of these corner cases:</p> <ul> <li> <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability to receive and you set your <code>content</code> capability to not receive.</p> </li> <li> <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p> </li> <li> <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"
     },
     "AttendeeIdItem": {
       "type": "structure",
@@ -698,7 +698,7 @@
         },
         "Capabilities": {
           "shape": "AttendeeCapabilities",
-          "documentation": "<p>The capabilities (<code>audio</code>, <code>video</code>, or <code>content</code>) that you want to grant an attendee. If you don't specify capabilities, all users have send and receive capabilities on all media channels by default.</p>"
+          "documentation": "<p>The capabilities (<code>audio</code>, <code>video</code>, or <code>content</code>) that you want to grant an attendee. If you don't specify capabilities, all users have send and receive capabilities on all media channels by default.</p> <note> <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see .</p> </note> <p>When using capabilities, be aware of these corner cases:</p> <ul> <li> <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability to receive and you set your <code>content</code> capability to not receive.</p> </li> <li> <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p> </li> <li> <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"
         }
       }
     },
@@ -772,6 +772,10 @@
         "PrimaryMeetingId": {
           "shape": "PrimaryMeetingId",
           "documentation": "<p>When specified, replicates the media from the primary meeting to the new meeting.</p>"
+        },
+        "TenantIds": {
+          "shape": "TenantIdList",
+          "documentation": "<p>A consistent and opaque identifier, created and maintained by the builder to represent a segment of their users.</p>"
         }
       }
     },
@@ -825,6 +829,10 @@
         "PrimaryMeetingId": {
           "shape": "PrimaryMeetingId",
           "documentation": "<p>When specified, replicates the media from the primary meeting to the new meeting.</p>"
+        },
+        "TenantIds": {
+          "shape": "TenantIdList",
+          "documentation": "<p>A consistent and opaque identifier, created and maintained by the builder to represent a segment of their users.</p>"
         }
       }
     },
@@ -914,7 +922,7 @@
         },
         "Region": {
           "shape": "TranscribeMedicalRegion",
-          "documentation": "<p>The AWS Region passed to Amazon Transcribe Medical. If you don't specify a Region, Amazon Chime uses the meeting's Region.</p>"
+          "documentation": "<p>The AWS Region passed to Amazon Transcribe Medical. If you don't specify a Region, Amazon Chime uses the meeting's Region. </p>"
         },
         "ContentIdentificationType": {
           "shape": "TranscribeMedicalContentIdentificationType",
@@ -1181,6 +1189,10 @@
         "PrimaryMeetingId": {
           "shape": "PrimaryMeetingId",
           "documentation": "<p>When specified, replicates the media from the primary meeting to this meeting.</p>"
+        },
+        "TenantIds": {
+          "shape": "TenantIdList",
+          "documentation": "<p>Array of strings.</p>"
         }
       },
       "documentation": "<p>A meeting created using the Amazon Chime SDK.</p>"
@@ -1267,6 +1279,20 @@
       "type": "string",
       "max": 4096
     },
+    "TenantId": {
+      "type": "string",
+      "max": 256,
+      "min": 2,
+      "pattern": "^(?!.*?(.)\\1{3})[-_!@#$a-zA-Z0-9]*$"
+    },
+    "TenantIdList": {
+      "type": "list",
+      "member": {
+        "shape": "TenantId"
+      },
+      "max": 5,
+      "min": 1
+    },
     "TranscribeContentIdentificationType": {
       "type": "string",
       "enum": [
@@ -1434,7 +1460,8 @@
       "type": "structure",
       "members": {
         "Attendee": {
-          "shape": "Attendee"
+          "shape": "Attendee",
+          "documentation": "<p>The updated attendee data.</p>"
         }
       }
     }

apis/dms-2016-01-01.min.json

@@ -2018,6 +2018,22 @@
           }
         }
       }
+    },
+    "UpdateSubscriptionsToEventBridge": {
+      "input": {
+        "type": "structure",
+        "members": {
+          "ForceMove": {
+            "type": "boolean"
+          }
+        }
+      },
+      "output": {
+        "type": "structure",
+        "members": {
+          "Result": {}
+        }
+      }
     }
   },
   "shapes": {