Amazonka.APIGateway.Types.TlsConfig

Documentation

data TlsConfig

Specifies the TLS configuration for an integration.

See: newTlsConfig smart constructor.

Constructors

TlsConfig'

Fields

• insecureSkipVerification :: Maybe Bool

  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.

Instances

FromJSON TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

Methods

parseJSON :: Value -> Parser TlsConfig

parseJSONList :: Value -> Parser [TlsConfig]

ToJSON TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

Methods

toJSON :: TlsConfig -> Value

toEncoding :: TlsConfig -> Encoding

toJSONList :: [TlsConfig] -> Value

toEncodingList :: [TlsConfig] -> Encoding

Generic TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

Associated Types

type Rep TlsConfig :: Type -> Type

Methods

from :: TlsConfig -> Rep TlsConfig x

to :: Rep TlsConfig x -> TlsConfig

Read TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

Methods

readsPrec :: Int -> ReadS TlsConfig

readList :: ReadS [TlsConfig]

readPrec :: ReadPrec TlsConfig

readListPrec :: ReadPrec [TlsConfig]

Show TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

Methods

showsPrec :: Int -> TlsConfig -> ShowS

show :: TlsConfig -> String

showList :: [TlsConfig] -> ShowS

NFData TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

Methods

rnf :: TlsConfig -> ()

Eq TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

Methods

(==) :: TlsConfig -> TlsConfig -> Bool

(/=) :: TlsConfig -> TlsConfig -> Bool

Hashable TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

Methods

hashWithSalt :: Int -> TlsConfig -> Int

hash :: TlsConfig -> Int

type Rep TlsConfig

Defined in Amazonka.APIGateway.Types.TlsConfig

type Rep TlsConfig = D1 ('MetaData "TlsConfig" "Amazonka.APIGateway.Types.TlsConfig" "amazonka-apigateway-2.0-zw0Lbt4rUGxZBjJ4Rpfi" 'False) (C1 ('MetaCons "TlsConfig'" 'PrefixI 'True) (S1 ('MetaSel ('Just "insecureSkipVerification") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Bool))))

newTlsConfig :: TlsConfig

Create a value of TlsConfig with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:insecureSkipVerification:TlsConfig', tlsConfig_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.

tlsConfig_insecureSkipVerification :: Lens' TlsConfig (Maybe Bool)

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.