Module aws_sdk_bedrock::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon Bedrock can respond with.

Structs

• CloudWatchConfig

  CloudWatch logging configuration.

• CustomModelSummary

  Summary information for a custom model.

• FoundationModelDetails

  Information about a foundation model.

• FoundationModelSummary

  Summary information for a foundation model.

• LoggingConfig

  Configuration fields for invokation logging.

• ModelCustomizationJobSummary

  Information about one customization job

• OutputDataConfig

  S3 Location of the output data.

• ProvisionedModelSummary

  Set of fields associated with a provisioned throughput.

• S3Config

  S3 configuration for storing log data.

• Tag

  Definition of the key/value pair for a tag.

• TrainingDataConfig

  S3 Location of the training data.

• TrainingMetrics

  Metrics associated with the custom job.

• ValidationDataConfig

  Array of up to 10 validators.

• Validator

  Information about a validator.

• ValidatorMetric

  The metric for the validator.

• VpcConfig

  VPC configuration.

Enums

• CommitmentDuration
  When writing a match expression against CommitmentDuration, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FineTuningJobStatus
  When writing a match expression against FineTuningJobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• InferenceType
  When writing a match expression against InferenceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ModelCustomization
  When writing a match expression against ModelCustomization, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ModelCustomizationJobStatus
  When writing a match expression against ModelCustomizationJobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ModelModality
  When writing a match expression against ModelModality, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ProvisionedModelStatus
  When writing a match expression against ProvisionedModelStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SortByProvisionedModels
  When writing a match expression against SortByProvisionedModels, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SortJobsBy
  When writing a match expression against SortJobsBy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SortModelsBy
  When writing a match expression against SortModelsBy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SortOrder
  When writing a match expression against SortOrder, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.