Package software.amazon.awssdk.services.apigateway.model

Interface TlsConfig.Builder

All Superinterfaces:

Buildable, CopyableBuilder<TlsConfig.Builder,TlsConfig>, SdkBuilder<TlsConfig.Builder,TlsConfig>, SdkPojo

Enclosing class:

TlsConfig

public static interface TlsConfig.Builder
extends SdkPojo, CopyableBuilder<TlsConfig.Builder,TlsConfig>

Method Summary

Modifier and Type	Method	Description
TlsConfig.Builder	insecureSkipVerification(Boolean insecureSkipVerification)	Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority.

Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder

copy

Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder

applyMutation, build

Methods inherited from interface software.amazon.awssdk.core.SdkPojo

equalsBySdkFields, sdkFieldNameToField, sdkFields

Method Detail

insecureSkipVerification

TlsConfig.Builder insecureSkipVerification(Boolean insecureSkipVerification)

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.

Parameters:

insecureSkipVerification - 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.

Returns:

Returns a reference to this object so that method calls can be chained together.