Updates SDK to v2.1437.0

.changes/2.1437.0.json

@@ -0,0 +1,32 @@
+[
+    {
+        "type": "feature",
+        "category": "ChimeSDKMeetings",
+        "description": "Updated API documentation to include additional exceptions."
+    },
+    {
+        "type": "feature",
+        "category": "EC2",
+        "description": "Documentation updates for Elastic Compute Cloud (EC2)."
+    },
+    {
+        "type": "feature",
+        "category": "Glue",
+        "description": "AWS Glue Crawlers can now accept SerDe overrides from a custom csv classifier. The two SerDe options are LazySimpleSerDe and OpenCSVSerDe. In case, the user wants crawler to do the selection, \"None\" can be selected for this purpose."
+    },
+    {
+        "type": "feature",
+        "category": "PI",
+        "description": "AWS Performance Insights for Amazon RDS is launching Performance Analysis On Demand, a new feature that allows you to analyze database performance metrics and find out the performance issues. You can now use SDK to create, list, get, delete, and manage tags of performance analysis reports."
+    },
+    {
+        "type": "feature",
+        "category": "Route53Domains",
+        "description": "Provide explanation if CheckDomainTransferability return false. Provide requestId if a request is already submitted.  Add sensitive protection for customer information"
+    },
+    {
+        "type": "feature",
+        "category": "SageMaker",
+        "description": "SageMaker Inference Recommender now provides SupportedResponseMIMETypes from DescribeInferenceRecommendationsJob response"
+    }
+]

CHANGELOG.md

@@ -1,7 +1,15 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.1436.0-->
+<!--LATEST=2.1437.0-->
 <!--ENTRYINSERT-->
 
+## 2.1437.0
+* feature: ChimeSDKMeetings: Updated API documentation to include additional exceptions.
+* feature: EC2: Documentation updates for Elastic Compute Cloud (EC2).
+* feature: Glue: AWS Glue Crawlers can now accept SerDe overrides from a custom csv classifier. The two SerDe options are LazySimpleSerDe and OpenCSVSerDe. In case, the user wants crawler to do the selection, "None" can be selected for this purpose.
+* feature: PI: AWS Performance Insights for Amazon RDS is launching Performance Analysis On Demand, a new feature that allows you to analyze database performance metrics and find out the performance issues. You can now use SDK to create, list, get, delete, and manage tags of performance analysis reports.
+* feature: Route53Domains: Provide explanation if CheckDomainTransferability return false. Provide requestId if a request is already submitted.  Add sensitive protection for customer information
+* feature: SageMaker: SageMaker Inference Recommender now provides SupportedResponseMIMETypes from DescribeInferenceRecommendationsJob response
+
 ## 2.1436.0
 * feature: MediaPackage: Fix SDK logging of certain fields.
 * feature: Omics: This release provides support for annotation store versioning and cross account sharing for Omics Analytics

README.md

@@ -71,7 +71,7 @@ require('aws-sdk/lib/maintenance_mode_message').suppress = true;
 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.1436.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.1437.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.normal.json

@@ -82,6 +82,12 @@
         },
         {
           "shape": "ServiceUnavailableException"
+        },
+        {
+          "shape": "ServiceFailureException"
+        },
+        {
+          "shape": "ThrottlingException"
         }
       ],
       "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 attendees can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"
@@ -145,6 +151,9 @@
         {
           "shape": "BadRequestException"
         },
+        {
+          "shape": "ConflictException"
+        },
         {
           "shape": "ForbiddenException"
         },
@@ -182,6 +191,9 @@
         {
           "shape": "BadRequestException"
         },
+        {
+          "shape": "ConflictException"
+        },
         {
           "shape": "ForbiddenException"
         },
@@ -399,6 +411,27 @@
         "shape": "ListTagsForResourceResponse"
       },
       "errors": [
+        {
+          "shape": "BadRequestException"
+        },
+        {
+          "shape": "ForbiddenException"
+        },
+        {
+          "shape": "UnauthorizedException"
+        },
+        {
+          "shape": "LimitExceededException"
+        },
+        {
+          "shape": "ServiceUnavailableException"
+        },
+        {
+          "shape": "ServiceFailureException"
+        },
+        {
+          "shape": "ThrottlingException"
+        },
         {
           "shape": "ResourceNotFoundException"
         }
@@ -501,6 +534,24 @@
         {
           "shape": "BadRequestException"
         },
+        {
+          "shape": "ForbiddenException"
+        },
+        {
+          "shape": "UnauthorizedException"
+        },
+        {
+          "shape": "LimitExceededException"
+        },
+        {
+          "shape": "ServiceUnavailableException"
+        },
+        {
+          "shape": "ServiceFailureException"
+        },
+        {
+          "shape": "ThrottlingException"
+        },
         {
           "shape": "ResourceNotFoundException"
         },
@@ -527,6 +578,24 @@
         {
           "shape": "BadRequestException"
         },
+        {
+          "shape": "ForbiddenException"
+        },
+        {
+          "shape": "UnauthorizedException"
+        },
+        {
+          "shape": "LimitExceededException"
+        },
+        {
+          "shape": "ServiceUnavailableException"
+        },
+        {
+          "shape": "ServiceFailureException"
+        },
+        {
+          "shape": "ThrottlingException"
+        },
         {
           "shape": "ResourceNotFoundException"
         }
@@ -563,6 +632,12 @@
         },
         {
           "shape": "ServiceUnavailableException"
+        },
+        {
+          "shape": "ServiceFailureException"
+        },
+        {
+          "shape": "ThrottlingException"
         }
       ],
       "documentation": "<p>The capabilities 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 attendees can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"