Updates SDK to v2.1331.0

.changes/2.1331.0.json

@@ -0,0 +1,42 @@
+[
+    {
+        "type": "feature",
+        "category": "Athena",
+        "description": "A new field SubstatementType is added to GetQueryExecution API, so customers have an error free way to detect the query type and interpret the result."
+    },
+    {
+        "type": "feature",
+        "category": "DynamoDB",
+        "description": "Adds deletion protection support to DynamoDB tables. Tables with deletion protection enabled cannot be deleted. Deletion protection is disabled by default, can be enabled via the CreateTable or UpdateTable APIs, and is visible in TableDescription. This setting is not replicated for Global Tables."
+    },
+    {
+        "type": "feature",
+        "category": "EC2",
+        "description": "Introducing Amazon EC2 C7g, M7g and R7g instances, powered by the latest generation AWS Graviton3 processors and deliver up to 25% better performance over Graviton2-based instances."
+    },
+    {
+        "type": "feature",
+        "category": "LakeFormation",
+        "description": "This release adds two new API support \"GetDataCellsFiler\" and \"UpdateDataCellsFilter\", and also updates the corresponding documentation."
+    },
+    {
+        "type": "feature",
+        "category": "MediaPackage",
+        "description": "This release provides the date and time live resources were created."
+    },
+    {
+        "type": "feature",
+        "category": "MediaPackageVod",
+        "description": "This release provides the date and time VOD resources were created."
+    },
+    {
+        "type": "feature",
+        "category": "Route53Resolver",
+        "description": "Add dual-stack and IPv6 support for Route 53 Resolver Endpoint,Add IPv6 target IP in Route 53 Resolver Forwarding Rule"
+    },
+    {
+        "type": "feature",
+        "category": "SageMaker",
+        "description": "There needs to be a user identity to specify the SageMaker user who perform each action regarding the entity. However, these is a not a unified concept of user identity across SageMaker service that could be used today."
+    }
+]

CHANGELOG.md

@@ -1,7 +1,17 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.1330.0-->
+<!--LATEST=2.1331.0-->
 <!--ENTRYINSERT-->
 
+## 2.1331.0
+* feature: Athena: A new field SubstatementType is added to GetQueryExecution API, so customers have an error free way to detect the query type and interpret the result.
+* feature: DynamoDB: Adds deletion protection support to DynamoDB tables. Tables with deletion protection enabled cannot be deleted. Deletion protection is disabled by default, can be enabled via the CreateTable or UpdateTable APIs, and is visible in TableDescription. This setting is not replicated for Global Tables.
+* feature: EC2: Introducing Amazon EC2 C7g, M7g and R7g instances, powered by the latest generation AWS Graviton3 processors and deliver up to 25% better performance over Graviton2-based instances.
+* feature: LakeFormation: This release adds two new API support "GetDataCellsFiler" and "UpdateDataCellsFilter", and also updates the corresponding documentation.
+* feature: MediaPackage: This release provides the date and time live resources were created.
+* feature: MediaPackageVod: This release provides the date and time VOD resources were created.
+* feature: Route53Resolver: Add dual-stack and IPv6 support for Route 53 Resolver Endpoint,Add IPv6 target IP in Route 53 Resolver Forwarding Rule
+* feature: SageMaker: There needs to be a user identity to specify the SageMaker user who perform each action regarding the entity. However, these is a not a unified concept of user identity across SageMaker service that could be used today.
+
 ## 2.1330.0
 * feature: DMS: This release adds DMS Fleet Advisor Target Recommendation APIs and exposes functionality for DMS Fleet Advisor. It adds functionality to start Target Recommendation calculation.
 

README.md

@@ -57,7 +57,7 @@ for further details.
 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.1330.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.1331.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/athena-2017-05-18.min.json

@@ -1797,7 +1797,8 @@
         },
         "ExecutionParameters": {
           "shape": "S1j"
-        }
+        },
+        "SubstatementType": {}
       }
     },
     "Sw": {

apis/athena-2017-05-18.normal.json

@@ -815,7 +815,7 @@
           "shape": "InvalidRequestException"
         }
       ],
-      "documentation": "<p>Lists the data catalogs in the current Amazon Web Services account.</p>"
+      "documentation": "<p>Lists the data catalogs in the current Amazon Web Services account.</p> <note> <p>In the Athena console, data catalogs are listed as \"data sources\" on the <b>Data sources</b> page under the <b>Data source name</b> column.</p> </note>"
     },
     "ListDatabases": {
       "name": "ListDatabases",
@@ -2090,7 +2090,7 @@
           "documentation": "<p>Specifies the Lambda function or functions to use for the data catalog. This is a mapping whose values depend on the catalog type. </p> <ul> <li> <p>For the <code>HIVE</code> data catalog type, use the following syntax. The <code>metadata-function</code> parameter is required. <code>The sdk-version</code> parameter is optional and defaults to the currently supported version.</p> <p> <code>metadata-function=<i>lambda_arn</i>, sdk-version=<i>version_number</i> </code> </p> </li> <li> <p>For the <code>LAMBDA</code> data catalog type, use one of the following sets of required parameters, but not both.</p> <ul> <li> <p>If you have one Lambda function that processes metadata and another for reading the actual data, use the following syntax. Both parameters are required.</p> <p> <code>metadata-function=<i>lambda_arn</i>, record-function=<i>lambda_arn</i> </code> </p> </li> <li> <p> If you have a composite Lambda function that processes both metadata and data, use the following syntax to specify your Lambda function.</p> <p> <code>function=<i>lambda_arn</i> </code> </p> </li> </ul> </li> <li> <p>The <code>GLUE</code> type takes a catalog ID parameter and is required. The <code> <i>catalog_id</i> </code> is the account ID of the Amazon Web Services account to which the Glue catalog belongs.</p> <p> <code>catalog-id=<i>catalog_id</i> </code> </p> <ul> <li> <p>The <code>GLUE</code> data catalog type also applies to the default <code>AwsDataCatalog</code> that already exists in your account, of which you can have only one and cannot modify.</p> </li> <li> <p>Queries that specify a Glue Data Catalog other than the default <code>AwsDataCatalog</code> must be run on Athena engine version 2.</p> </li> </ul> </li> </ul>"
         }
       },
-      "documentation": "<p>Contains information about a data catalog in an Amazon Web Services account.</p>"
+      "documentation": "<p>Contains information about a data catalog in an Amazon Web Services account.</p> <note> <p>In the Athena console, data catalogs are listed as \"data sources\" on the <b>Data sources</b> page under the <b>Data source name</b> column.</p> </note>"
     },
     "DataCatalogSummary": {
       "type": "structure",
@@ -2320,7 +2320,7 @@
       "members": {
         "SelectedEngineVersion": {
           "shape": "NameString",
-          "documentation": "<p>The engine version requested by the user. Possible values are determined by the output of <code>ListEngineVersions</code>, including Auto. The default is Auto.</p>"
+          "documentation": "<p>The engine version requested by the user. Possible values are determined by the output of <code>ListEngineVersions</code>, including AUTO. The default is AUTO.</p>"
         },
         "EffectiveEngineVersion": {
           "shape": "NameString",
@@ -3806,6 +3806,10 @@
         "ExecutionParameters": {
           "shape": "ExecutionParameters",
           "documentation": "<p>A list of values for the parameters in a query. The values are applied sequentially to the parameters in the query in the order in which the parameters occur.</p>"
+        },
+        "SubstatementType": {
+          "shape": "String",
+          "documentation": "<p>The kind of query statement that was run.</p>"
         }
       },
       "documentation": "<p>Information about a single instance of a query execution.</p>"