Amazonka.IoTSecureTunneling.Types.DestinationConfig

Documentation

data DestinationConfig

The destination configuration.

See: newDestinationConfig smart constructor.

Constructors

DestinationConfig'

Fields

• thingName :: Maybe Text

  The name of the IoT thing to which you want to connect.

• services :: NonEmpty Text

  A list of service names that identify the target application. The IoT client running on the destination device reads this value and uses it to look up a port or an IP address and a port. The IoT client instantiates the local proxy, which uses this information to connect to the destination application.

Instances

FromJSON DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

Methods

parseJSON :: Value -> Parser DestinationConfig

parseJSONList :: Value -> Parser [DestinationConfig]

ToJSON DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

Methods

toJSON :: DestinationConfig -> Value

toEncoding :: DestinationConfig -> Encoding

toJSONList :: [DestinationConfig] -> Value

toEncodingList :: [DestinationConfig] -> Encoding

Generic DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

Associated Types

type Rep DestinationConfig :: Type -> Type

Methods

from :: DestinationConfig -> Rep DestinationConfig x

to :: Rep DestinationConfig x -> DestinationConfig

Read DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

Methods

readsPrec :: Int -> ReadS DestinationConfig

readList :: ReadS [DestinationConfig]

readPrec :: ReadPrec DestinationConfig

readListPrec :: ReadPrec [DestinationConfig]

Show DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

Methods

showsPrec :: Int -> DestinationConfig -> ShowS

show :: DestinationConfig -> String

showList :: [DestinationConfig] -> ShowS

NFData DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

Methods

rnf :: DestinationConfig -> ()

Eq DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

Methods

(==) :: DestinationConfig -> DestinationConfig -> Bool

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

Hashable DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

Methods

hashWithSalt :: Int -> DestinationConfig -> Int

hash :: DestinationConfig -> Int

type Rep DestinationConfig

Defined in Amazonka.IoTSecureTunneling.Types.DestinationConfig

type Rep DestinationConfig = D1 ('MetaData "DestinationConfig" "Amazonka.IoTSecureTunneling.Types.DestinationConfig" "amazonka-iotsecuretunneling-2.0-B7tp11579Ld35NvrM5xQuK" 'False) (C1 ('MetaCons "DestinationConfig'" 'PrefixI 'True) (S1 ('MetaSel ('Just "thingName") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)) :*: S1 ('MetaSel ('Just "services") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (NonEmpty Text))))

newDestinationConfig

Arguments

:: NonEmpty Text

$sel:services:DestinationConfig'

-> DestinationConfig

Create a value of DestinationConfig 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:thingName:DestinationConfig', destinationConfig_thingName - The name of the IoT thing to which you want to connect.

$sel:services:DestinationConfig', destinationConfig_services - A list of service names that identify the target application. The IoT client running on the destination device reads this value and uses it to look up a port or an IP address and a port. The IoT client instantiates the local proxy, which uses this information to connect to the destination application.

destinationConfig_thingName :: Lens' DestinationConfig (Maybe Text)

The name of the IoT thing to which you want to connect.

destinationConfig_services :: Lens' DestinationConfig (NonEmpty Text)

A list of service names that identify the target application. The IoT client running on the destination device reads this value and uses it to look up a port or an IP address and a port. The IoT client instantiates the local proxy, which uses this information to connect to the destination application.