docs(client-api-gateway): Documentation updates for Amazon API Gateway

Author: awstools

clients/client-api-gateway/src/models/models_0.ts

@@ -1571,6 +1571,10 @@ export interface TlsConfig {
    *             validation, which includes checking the certificate's expiration date, hostname, and
    *             presence of a root certificate authority. Supported only for <code>HTTP</code> and
    *             <code>HTTP_PROXY</code> integrations.</p>
+   *          <important>
+   *             <p>Enabling <code>insecureSkipVerification</code> isn't recommended, especially for integrations with public
+   *           HTTPS endpoints. If you enable <code>insecureSkipVerification</code>, you increase the risk of man-in-the-middle attacks.</p>
+   *          </important>
    */
   insecureSkipVerification?: boolean;
 }

codegen/sdk-codegen/aws-models/api-gateway.json

@@ -9865,7 +9865,7 @@
         "insecureSkipVerification": {
           "target": "com.amazonaws.apigateway#Boolean",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is\n            issued by a supported certificate authority. This isn’t recommended, but it enables you to\n            use certificates that are signed by private certificate authorities, or certificates\n            that are self-signed. If enabled, API Gateway still performs basic certificate\n            validation, which includes checking the certificate's expiration date, hostname, and\n            presence of a root certificate authority. Supported only for <code>HTTP</code> and\n            <code>HTTP_PROXY</code> integrations.</p>"
+            "smithy.api#documentation": "<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is\n            issued by a supported certificate authority. This isn’t recommended, but it enables you to\n            use certificates that are signed by private certificate authorities, or certificates\n            that are self-signed. If enabled, API Gateway still performs basic certificate\n            validation, which includes checking the certificate's expiration date, hostname, and\n            presence of a root certificate authority. Supported only for <code>HTTP</code> and\n            <code>HTTP_PROXY</code> integrations.</p>\n         <important>\n            <p>Enabling <code>insecureSkipVerification</code> isn't recommended, especially for integrations with public\n          HTTPS endpoints. If you enable <code>insecureSkipVerification</code>, you increase the risk of man-in-the-middle attacks.</p>\n         </important>"
           }
         }
       },