class
Amazonite::ApiGateway::TlsConfig
- Amazonite::ApiGateway::TlsConfig
- Reference
- Object
Overview
Specifies the TLS configuration for an integration.
Included Modules
- JSON::Serializable
Defined in:
api_gateway/tls_config.crConstructors
Instance Method Summary
-
#==(other : self)
Returns
trueif this reference is the same as other. -
#hash(hasher)
See
Object#hash(hasher) -
#insecure_skip_verification : Bool | Nil
Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority.
-
#insecure_skip_verification=(insecure_skip_verification : Bool | Nil)
Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority.
- #validate! : Nil
Constructor Detail
Instance Method Detail
Returns true if this reference is the same as other. Invokes same?.
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.