/* * Copyright 2018-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved. * * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with * the License. A copy of the License is located at * * http://aws.amazon.com/apache2.0 * * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions * and limitations under the License. */ package com.amazonaws.services.apigateway.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.protocol.StructuredPojo; import com.amazonaws.protocol.ProtocolMarshaller; /** *
* Specifies the TLS configuration for an integration. *
*/ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class TlsConfig implements Serializable, Cloneable, StructuredPojo { /** *
* 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 HTTP
and HTTP_PROXY
* integrations.
*
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public HTTPS
* endpoints. If you enable insecureSkipVerification
, you increase the risk of man-in-the-middle
* attacks.
*
* 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 HTTP
and HTTP_PROXY
* integrations.
*
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public HTTPS
* endpoints. If you enable insecureSkipVerification
, you increase the risk of man-in-the-middle
* attacks.
*
HTTP
and HTTP_PROXY
integrations.
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public
* HTTPS endpoints. If you enable insecureSkipVerification
, you increase the risk of
* man-in-the-middle attacks.
*
* 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 HTTP
and HTTP_PROXY
* integrations.
*
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public HTTPS
* endpoints. If you enable insecureSkipVerification
, you increase the risk of man-in-the-middle
* attacks.
*
HTTP
and HTTP_PROXY
integrations.
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public
* HTTPS endpoints. If you enable insecureSkipVerification
, you increase the risk of
* man-in-the-middle attacks.
*
* 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 HTTP
and HTTP_PROXY
* integrations.
*
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public HTTPS
* endpoints. If you enable insecureSkipVerification
, you increase the risk of man-in-the-middle
* attacks.
*
HTTP
and HTTP_PROXY
integrations.
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public
* HTTPS endpoints. If you enable insecureSkipVerification
, you increase the risk of
* man-in-the-middle attacks.
*
* 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 HTTP
and HTTP_PROXY
* integrations.
*
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public HTTPS
* endpoints. If you enable insecureSkipVerification
, you increase the risk of man-in-the-middle
* attacks.
*
HTTP
and HTTP_PROXY
integrations.
* Enabling insecureSkipVerification
isn't recommended, especially for integrations with public
* HTTPS endpoints. If you enable insecureSkipVerification
, you increase the risk of
* man-in-the-middle attacks.
*