Updates SDK to v2.393.0

.changes/2.393.0.json

@@ -0,0 +1,22 @@
+[
+    {
+        "type": "bugfix",
+        "category": "S3 managed uploader",
+        "description": "S3 managed uploader will not uriEscape tags when doing a multi-part upload."
+    },
+    {
+        "type": "feature",
+        "category": "ACMPCA",
+        "description": "Added TagOnCreate parameter to the CreateCertificateAuthority operation, updated the Tag regex pattern to align with AWS tagging APIs, and added RevokeCertificate limit."
+    },
+    {
+        "type": "feature",
+        "category": "ApiGatewayManagementApi",
+        "description": "Fixes a typo in the 'max' constraint."
+    },
+    {
+        "type": "feature",
+        "category": "WorkLink",
+        "description": "This is the initial SDK release for Amazon WorkLink. Amazon WorkLink is a fully managed, cloud-based service that enables secure, one-click access to internal websites and web apps from mobile phones. With Amazon WorkLink, employees can access internal websites as seamlessly as they access any other website. IT administrators can manage users, devices, and domains by enforcing their own security and access policies via the AWS Console or the AWS SDK."
+    }
+]

CHANGELOG.md

@@ -1,7 +1,13 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.392.0-->
+<!--LATEST=2.393.0-->
 <!--ENTRYINSERT-->
 
+## 2.393.0
+* bugfix: S3 managed uploader: S3 managed uploader will not uriEscape tags when doing a multi-part upload.
+* feature: ACMPCA: Added TagOnCreate parameter to the CreateCertificateAuthority operation, updated the Tag regex pattern to align with AWS tagging APIs, and added RevokeCertificate limit.
+* feature: ApiGatewayManagementApi: Fixes a typo in the 'max' constraint.
+* feature: WorkLink: This is the initial SDK release for Amazon WorkLink. Amazon WorkLink is a fully managed, cloud-based service that enables secure, one-click access to internal websites and web apps from mobile phones. With Amazon WorkLink, employees can access internal websites as seamlessly as they access any other website. IT administrators can manage users, devices, and domains by enforcing their own security and access policies via the AWS Console or the AWS SDK.
+
 ## 2.392.0
 * feature: AppStream: This API update includes support for tagging Stack, Fleet, and ImageBuilder resources at creation time.
 * feature: DMS: Update for DMS TestConnectionSucceeds waiter

README.md

@@ -23,7 +23,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.392.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.393.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/acm-pca-2017-08-22.min.json

@@ -28,7 +28,10 @@
             "shape": "Se"
           },
           "CertificateAuthorityType": {},
-          "IdempotencyToken": {}
+          "IdempotencyToken": {},
+          "Tags": {
+            "shape": "Sm"
+          }
         }
       },
       "output": {
@@ -90,7 +93,7 @@
         "type": "structure",
         "members": {
           "CertificateAuthority": {
-            "shape": "Sx"
+            "shape": "S11"
           }
         }
       }
@@ -248,7 +251,7 @@
           "CertificateAuthorities": {
             "type": "list",
             "member": {
-              "shape": "Sx"
+              "shape": "S11"
             }
           },
           "NextToken": {}
@@ -273,7 +276,7 @@
         "type": "structure",
         "members": {
           "Tags": {
-            "shape": "S1t"
+            "shape": "Sm"
           },
           "NextToken": {}
         }
@@ -315,7 +318,7 @@
         "members": {
           "CertificateAuthorityArn": {},
           "Tags": {
-            "shape": "S1t"
+            "shape": "Sm"
           }
         }
       }
@@ -330,7 +333,7 @@
         "members": {
           "CertificateAuthorityArn": {},
           "Tags": {
-            "shape": "S1t"
+            "shape": "Sm"
           }
         }
       }
@@ -404,7 +407,20 @@
         }
       }
     },
-    "Sx": {
+    "Sm": {
+      "type": "list",
+      "member": {
+        "type": "structure",
+        "required": [
+          "Key"
+        ],
+        "members": {
+          "Key": {},
+          "Value": {}
+        }
+      }
+    },
+    "S11": {
       "type": "structure",
       "members": {
         "Arn": {},
@@ -434,19 +450,6 @@
           "type": "timestamp"
         }
       }
-    },
-    "S1t": {
-      "type": "list",
-      "member": {
-        "type": "structure",
-        "required": [
-          "Key"
-        ],
-        "members": {
-          "Key": {},
-          "Value": {}
-        }
-      }
     }
   }
 }

apis/acm-pca-2017-08-22.normal.json

@@ -32,6 +32,9 @@
         {
           "shape": "InvalidPolicyException"
         },
+        {
+          "shape": "InvalidTagException"
+        },
         {
           "shape": "LimitExceededException"
         }
@@ -387,6 +390,9 @@
         {
           "shape": "InvalidStateException"
         },
+        {
+          "shape": "LimitExceededException"
+        },
         {
           "shape": "ResourceNotFoundException"
         },
@@ -758,6 +764,10 @@
         "IdempotencyToken": {
           "shape": "IdempotencyToken",
           "documentation": "<p>Alphanumeric string that can be used to distinguish between calls to <b>CreateCertificateAuthority</b>. Idempotency tokens time out after five minutes. Therefore, if you call <b>CreateCertificateAuthority</b> multiple times with the same idempotency token within a five minute period, ACM PCA recognizes that you are requesting only one certificate. As a result, ACM PCA issues only one. If you change the idempotency token for each call, however, ACM PCA recognizes that you are requesting multiple certificates.</p>"
+        },
+        "Tags": {
+          "shape": "TagList",
+          "documentation": "<p>Key-value pairs that will be attached to the new private CA. You can associate up to 50 tags with a private CA.</p>"
         }
       }
     },
@@ -1282,7 +1292,7 @@
       "type": "string",
       "max": 128,
       "min": 1,
-      "pattern": "[\\p{L}\\p{Z}\\p{N}_.:\\/=+\\-@]*"
+      "pattern": "^([\\p{L}\\p{Z}\\p{N}_.:/=+\\-@]*)$"
     },
     "TagList": {
       "type": "list",
@@ -1296,7 +1306,7 @@
       "type": "string",
       "max": 256,
       "min": 0,
-      "pattern": "[\\p{L}\\p{Z}\\p{N}_.:\\/=+\\-@]*"
+      "pattern": "^([\\p{L}\\p{Z}\\p{N}_.:/=+\\-@]*)$"
     },
     "UntagCertificateAuthorityRequest": {
       "type": "structure",
@@ -1365,5 +1375,5 @@
       ]
     }
   },
-  "documentation": "<p>You can use the ACM PCA API to create a private certificate authority (CA). You must first call the <a>CreateCertificateAuthority</a> operation. If successful, the operation returns an Amazon Resource Name (ARN) for your private CA. Use this ARN as input to the <a>GetCertificateAuthorityCsr</a> operation to retrieve the certificate signing request (CSR) for your private CA certificate. Sign the CSR using the root or an intermediate CA in your on-premises PKI hierarchy, and call the <a>ImportCertificateAuthorityCertificate</a> to import your signed private CA certificate into ACM PCA. </p> <p>Use your private CA to issue and revoke certificates. These are private certificates that identify and secure client computers, servers, applications, services, devices, and users over SSLS/TLS connections within your organization. Call the <a>IssueCertificate</a> operation to issue a certificate. Call the <a>RevokeCertificate</a> operation to revoke a certificate. </p> <note> <p>Certificates issued by your private CA can be trusted only within your organization, not publicly.</p> </note> <p>Your private CA can optionally create a certificate revocation list (CRL) to track the certificates you revoke. To create a CRL, you must specify a <a>RevocationConfiguration</a> object when you call the <a>CreateCertificateAuthority</a> operation. ACM PCA writes the CRL to an S3 bucket that you specify. You must specify a bucket policy that grants ACM PCA write permission. </p> <p>You can also call the <a>CreateCertificateAuthorityAuditReport</a> to create an optional audit report that lists every time the CA private key is used. The private key is used for signing when the <b>IssueCertificate</b> or <b>RevokeCertificate</b> operation is called. </p>"
+  "documentation": "<p>You can use the ACM PCA API to create a private certificate authority (CA). You must first call the <a>CreateCertificateAuthority</a> operation. If successful, the operation returns an Amazon Resource Name (ARN) for your private CA. Use this ARN as input to the <a>GetCertificateAuthorityCsr</a> operation to retrieve the certificate signing request (CSR) for your private CA certificate. Sign the CSR using the root or an intermediate CA in your on-premises PKI hierarchy, and call the <a>ImportCertificateAuthorityCertificate</a> to import your signed private CA certificate into ACM PCA. </p> <p>Use your private CA to issue and revoke certificates. These are private certificates that identify and secure client computers, servers, applications, services, devices, and users over SSLS/TLS connections within your organization. Call the <a>IssueCertificate</a> operation to issue a certificate. Call the <a>RevokeCertificate</a> operation to revoke a certificate. </p> <note> <p>Certificates issued by your private CA can be trusted only within your organization, not publicly.</p> </note> <p>Your private CA can optionally create a certificate revocation list (CRL) to track the certificates you revoke. To create a CRL, you must specify a <a>RevocationConfiguration</a> object when you call the <a>CreateCertificateAuthority</a> operation. ACM PCA writes the CRL to an S3 bucket that you specify. You must specify a bucket policy that grants ACM PCA write permission. </p> <p>You can also call the <a>CreateCertificateAuthorityAuditReport</a> to create an optional audit report, which enumerates all of the issued, valid, expired, and revoked certificates from the CA.</p> <note> <p>Each ACM PCA API operation has a throttling limit which determines the number of times the operation can be called per second. For more information, see <a href=\"acm-pca/latest/userguide/PcaLimits.html#PcaLimits-api\">API Rate Limits in ACM PCA</a> in the ACM PCA user guide.</p> </note>"
 }

apis/acm-pca-2017-08-22.waiters2.json

@@ -48,6 +48,12 @@
                     "matcher": "path",
                     "argument": "AuditReportStatus",
                     "expected": "SUCCESS"
+                },
+                {
+                    "state": "failure",
+                    "matcher": "path",
+                    "argument": "AuditReportStatus",
+                    "expected": "FAILED"
                 }
             ]
         }

apis/apigatewaymanagementapi-2018-11-29.normal.json

@@ -45,7 +45,7 @@
   "shapes": {
     "Data": {
       "type": "blob",
-      "max": "131072",
+      "max": 131072,
       "documentation": "<p>The data to be sent to the client specified by its connection id.</p>"
     },
     "PostToConnectionRequest": {

apis/metadata.json

@@ -680,5 +680,8 @@
   },
   "backup": {
     "name": "Backup"
+  },
+  "worklink": {
+    "name": "WorkLink"
   }
 }

apis/worklink-2018-09-25.examples.json

@@ -0,0 +1,5 @@
+{
+  "version": "1.0",
+  "examples": {
+  }
+}