libZSservicesZSamazonka-comprehendmedicalZSamazonka-comprehendmedical
Copyright(c) 2013-2021 Brendan Hay
LicenseMozilla Public License, v. 2.0.
MaintainerBrendan Hay <brendan.g.hay+amazonka@gmail.com>
Stabilityauto-generated
Portabilitynon-portable (GHC extensions)
Safe HaskellNone

Amazonka.ComprehendMedical.Types.OutputDataConfig

Description

 
Synopsis

Documentation

data OutputDataConfig Source #

The output properties for a detection job.

See: newOutputDataConfig smart constructor.

Constructors

OutputDataConfig' 

Fields

  • s3Key :: Maybe Text

    The path to the output data files in the S3 bucket. Amazon Comprehend Medical creates an output directory using the job ID so that the output from one job does not overwrite the output of another.

  • s3Bucket :: Text

    When you use the OutputDataConfig object with asynchronous operations, you specify the Amazon S3 location where you want to write the output data. The URI must be in the same region as the API endpoint that you are calling. The location is used as the prefix for the actual location of the output.

Instances

Instances details
Eq OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

Read OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

Show OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

Generic OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

Associated Types

type Rep OutputDataConfig :: Type -> Type #

NFData OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

Methods

rnf :: OutputDataConfig -> () #

Hashable OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

ToJSON OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

FromJSON OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

type Rep OutputDataConfig Source # 
Instance details

Defined in Amazonka.ComprehendMedical.Types.OutputDataConfig

type Rep OutputDataConfig = D1 ('MetaData "OutputDataConfig" "Amazonka.ComprehendMedical.Types.OutputDataConfig" "libZSservicesZSamazonka-comprehendmedicalZSamazonka-comprehendmedical" 'False) (C1 ('MetaCons "OutputDataConfig'" 'PrefixI 'True) (S1 ('MetaSel ('Just "s3Key") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)) :*: S1 ('MetaSel ('Just "s3Bucket") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 Text)))

newOutputDataConfig Source #

Create a value of OutputDataConfig 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:s3Key:OutputDataConfig', outputDataConfig_s3Key - The path to the output data files in the S3 bucket. Amazon Comprehend Medical creates an output directory using the job ID so that the output from one job does not overwrite the output of another.

$sel:s3Bucket:OutputDataConfig', outputDataConfig_s3Bucket - When you use the OutputDataConfig object with asynchronous operations, you specify the Amazon S3 location where you want to write the output data. The URI must be in the same region as the API endpoint that you are calling. The location is used as the prefix for the actual location of the output.

outputDataConfig_s3Key :: Lens' OutputDataConfig (Maybe Text) Source #

The path to the output data files in the S3 bucket. Amazon Comprehend Medical creates an output directory using the job ID so that the output from one job does not overwrite the output of another.

outputDataConfig_s3Bucket :: Lens' OutputDataConfig Text Source #

When you use the OutputDataConfig object with asynchronous operations, you specify the Amazon S3 location where you want to write the output data. The URI must be in the same region as the API endpoint that you are calling. The location is used as the prefix for the actual location of the output.