Updates SDK to v2.668.0

.changes/2.668.0.json

@@ -0,0 +1,12 @@
+[
+    {
+        "type": "feature",
+        "category": "EFS",
+        "description": "Change the TagKeys argument for UntagResource to a URL parameter to address an issue with the Java and .NET SDKs."
+    },
+    {
+        "type": "feature",
+        "category": "SSM",
+        "description": "Added TimeoutSeconds as part of ListCommands API response."
+    }
+]

CHANGELOG.md

@@ -1,7 +1,11 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.667.0-->
+<!--LATEST=2.668.0-->
 <!--ENTRYINSERT-->
 
+## 2.668.0
+* feature: EFS: Change the TagKeys argument for UntagResource to a URL parameter to address an issue with the Java and .NET SDKs.
+* feature: SSM: Added TimeoutSeconds as part of ListCommands API response.
+
 ## 2.667.0
 * feature: IoTEvents: Doc only update to correct APIs and related descriptions
 * feature: Iot: AWS IoT Core released Fleet Provisioning for scalable onboarding of IoT devices to the cloud. This release includes support for customer's Lambda functions to validate devices during onboarding. Fleet Provisioning also allows devices to send Certificate Signing Requests (CSR) to AWS IoT Core for signing and getting a unique certificate. Lastly,  AWS IoT Core added a feature to register the same certificate for multiple accounts in the same region without needing to register the certificate authority (CA).

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.667.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.668.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/elasticfilesystem-2015-02-01.min.json

@@ -611,15 +611,18 @@
       "input": {
         "type": "structure",
         "required": [
-          "ResourceId"
+          "ResourceId",
+          "TagKeys"
         ],
         "members": {
           "ResourceId": {
             "location": "uri",
             "locationName": "ResourceId"
           },
           "TagKeys": {
-            "shape": "S1h"
+            "shape": "S1h",
+            "location": "querystring",
+            "locationName": "tagKeys"
           }
         }
       }

apis/elasticfilesystem-2015-02-01.normal.json

@@ -1767,7 +1767,8 @@
     "UntagResourceRequest": {
       "type": "structure",
       "required": [
-        "ResourceId"
+        "ResourceId",
+        "TagKeys"
       ],
       "members": {
         "ResourceId": {
@@ -1778,7 +1779,9 @@
         },
         "TagKeys": {
           "shape": "TagKeys",
-          "documentation": "<p>The keys of the key:value tag pairs that you want to remove from the specified EFS resource.</p>"
+          "documentation": "<p>The keys of the key:value tag pairs that you want to remove from the specified EFS resource.</p>",
+          "location": "querystring",
+          "locationName": "tagKeys"
         }
       }
     },

apis/ssm-2014-11-06.min.json

@@ -5550,6 +5550,9 @@
         },
         "CloudWatchOutputConfig": {
           "shape": "Sg4"
+        },
+        "TimeoutSeconds": {
+          "type": "integer"
         }
       }
     },

apis/ssm-2014-11-06.normal.json

@@ -42,7 +42,7 @@
           "shape": "TooManyUpdates"
         }
       ],
-      "documentation": "<p>Adds or overwrites one or more tags for the specified resource. Tags are metadata that you can assign to your documents, managed instances, maintenance windows, Parameter Store parameters, and patch baselines. Tags enable you to categorize your resources in different ways, for example, by purpose, owner, or environment. Each tag consists of a key and an optional value, both of which you define. For example, you could define a set of tags for your account's managed instances that helps you track each instance's owner and stack level. For example: Key=Owner and Value=DbAdmin, SysAdmin, or Dev. Or Key=Stack and Value=Production, Pre-Production, or Test.</p> <p>Each resource can have a maximum of 50 tags. </p> <p>We recommend that you devise a set of tag keys that meets your needs for each resource type. Using a consistent set of tag keys makes it easier for you to manage your resources. You can search and filter the resources based on the tags you add. Tags don't have any semantic meaning to and are interpreted strictly as a string of characters. </p> <p>For more information about using tags with EC2 instances, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html\">Tagging your Amazon EC2 resources</a> in the <i>Amazon EC2 User Guide</i>.</p>"
+      "documentation": "<p>Adds or overwrites one or more tags for the specified resource. Tags are metadata that you can assign to your documents, managed instances, maintenance windows, Parameter Store parameters, and patch baselines. Tags enable you to categorize your resources in different ways, for example, by purpose, owner, or environment. Each tag consists of a key and an optional value, both of which you define. For example, you could define a set of tags for your account's managed instances that helps you track each instance's owner and stack level. For example: Key=Owner and Value=DbAdmin, SysAdmin, or Dev. Or Key=Stack and Value=Production, Pre-Production, or Test.</p> <p>Each resource can have a maximum of 50 tags. </p> <p>We recommend that you devise a set of tag keys that meets your needs for each resource type. Using a consistent set of tag keys makes it easier for you to manage your resources. You can search and filter the resources based on the tags you add. Tags don't have any semantic meaning to Amazon EC2 and are interpreted strictly as a string of characters. </p> <p>For more information about tags, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html\">Tagging your Amazon EC2 resources</a> in the <i>Amazon EC2 User Guide</i>.</p>"
     },
     "CancelCommand": {
       "name": "CancelCommand",
@@ -4651,6 +4651,10 @@
         "CloudWatchOutputConfig": {
           "shape": "CloudWatchOutputConfig",
           "documentation": "<p>CloudWatch Logs information where you want Systems Manager to send the command output.</p>"
+        },
+        "TimeoutSeconds": {
+          "shape": "TimeoutSeconds",
+          "documentation": "<p>The <code>TimeoutSeconds</code> value specified for a command.</p>"
         }
       },
       "documentation": "<p>Describes a command request.</p>"
@@ -5411,7 +5415,7 @@
       "members": {
         "Content": {
           "shape": "DocumentContent",
-          "documentation": "<p>The content for the new SSM document in JSON or YAML format. We recommend storing the contents for your new document in an external JSON or YAML file and referencing the file in a command.</p> <p>For examples, see the following topics in the <i>AWS Systems Manager User Guide</i>.</p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/systems-manager/latest/userguide/create-ssm-console.html\">Create an SSM document (console)</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/systems-manager/latest/userguide/create-ssm-document-cli.html\">Create an SSM document (AWS CLI)</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/systems-manager/latest/userguide/create-ssm-document-api.html\">Create an SSM document (API)</a> </p> </li> </ul>"
+          "documentation": "<p>The content for the new SSM document in JSON or YAML format. We recommend storing the contents for your new document in an external JSON or YAML file and referencing the file in a command.</p> <p>For examples, see the following topics in the <i>AWS Systems Manager User Guide</i>.</p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/systems-manager/latest/userguide/create-ssm-document-api.html\">Create an SSM document (AWS API)</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/systems-manager/latest/userguide/create-ssm-document-cli.html\">Create an SSM document (AWS CLI)</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/systems-manager/latest/userguide/create-ssm-document-api.html\">Create an SSM document (API)</a> </p> </li> </ul>"
         },
         "Requires": {
           "shape": "DocumentRequiresList",
@@ -5552,7 +5556,7 @@
         },
         "Source": {
           "shape": "OpsItemSource",
-          "documentation": "<p>The origin of the OpsItem, such as Amazon EC2 or Systems Manager.</p> <note> <p>The source name can't contain the following strings: aws, amazon, and amzn. </p> </note>"
+          "documentation": "<p>The origin of the OpsItem, such as EC2 or Systems Manager.</p> <note> <p>The source name can't contain the following strings: aws, amazon, and amzn. </p> </note>"
         },
         "Title": {
           "shape": "OpsItemTitle",
@@ -7451,7 +7455,7 @@
           "documentation": "<p>The value for the filter key.</p>"
         }
       },
-      "documentation": "<p>One or more filters. Use a filter to return a more specific list of documents.</p> <p>For keys, you can specify one or more tags that have been applied to a document. </p> <p>Other valid values include Owner, Name, PlatformTypes, and DocumentType.</p> <p>Note that only one Owner can be specified in a request. For example: <code>Key=Owner,Values=Self</code>.</p> <p>If you use Name as a key, you can use a name prefix to return a list of documents. For example, in the AWS CLI, to return a list of all documents that begin with <code>Te</code>, run the following command:</p> <p> <code>aws ssm list-documents --filters Key=Name,Values=Te</code> </p> <p>If you specify more than two keys, only documents that are identified by all the tags are returned in the results. If you specify more than two values for a key, documents that are identified by any of the values are returned in the results.</p> <p>To specify a custom key and value pair, use the format <code>Key=tag:tagName,Values=valueName</code>.</p> <p>For example, if you created a Key called region and are using the AWS CLI to call the <code>list-documents</code> command: </p> <p> <code>aws ssm list-documents --filters Key=tag:region,Values=east,west Key=Owner,Values=Self</code> </p>"
+      "documentation": "<p>One or more filters. Use a filter to return a more specific list of documents.</p> <p>For keys, you can specify one or more tags that have been applied to a document. </p> <p>Other valid values include <code>Owner</code>, <code>Name</code>, <code>PlatformTypes</code>, <code>DocumentType</code>, and <code>TargetType</code>.</p> <p>Note that only one Owner can be specified in a request. For example: <code>Key=Owner,Values=Self</code>.</p> <p>If you use Name as a key, you can use a name prefix to return a list of documents. For example, in the AWS CLI, to return a list of all documents that begin with <code>Te</code>, run the following command:</p> <p> <code>aws ssm list-documents --filters Key=Name,Values=Te</code> </p> <p>If you specify more than two keys, only documents that are identified by all the tags are returned in the results. If you specify more than two values for a key, documents that are identified by any of the values are returned in the results.</p> <p>To specify a custom key and value pair, use the format <code>Key=tag:tagName,Values=valueName</code>.</p> <p>For example, if you created a Key called region and are using the AWS CLI to call the <code>list-documents</code> command: </p> <p> <code>aws ssm list-documents --filters Key=tag:region,Values=east,west Key=Owner,Values=Self</code> </p>"
     },
     "DocumentKeyValuesFilterKey": {
       "type": "string",
@@ -9949,7 +9953,7 @@
         },
         "Filters": {
           "shape": "CommandFilterList",
-          "documentation": "<p>(Optional) One or more filters. Use a filter to return a more specific list of results. Note that the <code>DocumentName</code> filter is not supported for ListCommandInvocations.</p>"
+          "documentation": "<p>(Optional) One or more filters. Use a filter to return a more specific list of results.</p>"
         },
         "Details": {
           "shape": "Boolean",
@@ -10122,7 +10126,7 @@
         },
         "Filters": {
           "shape": "DocumentKeyValuesFilterList",
-          "documentation": "<p>One or more DocumentKeyValuesFilter objects. Use a filter to return a more specific list of results. For keys, you can specify one or more key-value pair tags that have been applied to a document. Other valid keys include <code>Owner</code>, <code>Name</code>, <code>PlatformTypes</code>, and <code>DocumentType</code>. For example, to return documents you own use <code>Key=Owner,Values=Self</code>. To specify a custom key-value pair, use the format <code>Key=tag:tagName,Values=valueName</code>.</p>"
+          "documentation": "<p>One or more DocumentKeyValuesFilter objects. Use a filter to return a more specific list of results. For keys, you can specify one or more key-value pair tags that have been applied to a document. Other valid keys include <code>Owner</code>, <code>Name</code>, <code>PlatformTypes</code>, <code>DocumentType</code>, and <code>TargetType</code>. For example, to return documents you own use <code>Key=Owner,Values=Self</code>. To specify a custom key-value pair, use the format <code>Key=tag:tagName,Values=valueName</code>.</p>"
         },
         "MaxResults": {
           "shape": "MaxResults",

clients/efs.d.ts

@@ -809,7 +809,7 @@ declare namespace EFS {
     /**
      * The keys of the key:value tag pairs that you want to remove from the specified EFS resource.
      */
-    TagKeys?: TagKeys;
+    TagKeys: TagKeys;
   }
   export interface UpdateFileSystemRequest {
     /**