Amazon API Gateway Update: Documentation updates for Amazon API Gateway

AWS · AWS · commit 509473559cc5 · 2022-06-22T18:19:23.000Z
diff --git a/.changes/next-release/feature-AmazonAPIGateway-36f04e1.json b/.changes/next-release/feature-AmazonAPIGateway-36f04e1.json
@@ -0,0 +1,6 @@
+{
+    "type": "feature",
+    "category": "Amazon API Gateway",
+    "contributor": "",
+    "description": "Documentation updates for Amazon API Gateway"
+}
diff --git a/services/apigateway/src/main/resources/codegen-resources/service-2.json b/services/apigateway/src/main/resources/codegen-resources/service-2.json
@@ -6536,7 +6536,7 @@
       "members":{
         "insecureSkipVerification":{
           "shape":"Boolean",
-          "documentation":"<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate 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>"
+          "documentation":"<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate 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>"
         }
       },
       "documentation":"<p>Specifies the TLS configuration for an integration.</p>"

Original file line number	Diff line number	Diff line change
`@@ -6536,7 +6536,7 @@`
`6536`	`6536`	`"members":{`
`6537`	`6537`	`"insecureSkipVerification":{`
`6538`	`6538`	`"shape":"Boolean",`
`6539`		- "documentation":"<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate 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>"
	`6539`	+ "documentation":"<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate 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>"
`6540`	`6540`	`}`
`6541`	`6541`	`},`
`6542`	`6542`	`"documentation":"<p>Specifies the TLS configuration for an integration.</p>"`