Module aws_sdk_braket::types

source ·
Expand description

Data structures used by operation inputs/outputs.

Modules

Structs

  • AlgorithmSpecification

    Defines the Amazon Braket job to be created. Specifies the container image the job uses and the paths to the Python scripts used for entry and training.

  • ContainerImage

    The container image used to create an Amazon Braket job.

  • DataSource

    Information about the source of the data used by the Amazon Braket job.

  • DeviceConfig

    Configures the quantum processing units (QPUs) or simulator used to create and run an Amazon Braket job.

  • DeviceQueueInfo

    Information about tasks and jobs queued on a device.

  • DeviceSummary

    Includes information about the device.

  • HybridJobQueueInfo

    Information about the queue for a specified job.

  • InputFileConfig

    A list of parameters that specify the input channels, type of input data, and where it is located.

  • InstanceConfig

    Configures the resource instances to use while running the Amazon Braket hybrid job on Amazon Braket.

  • JobCheckpointConfig

    Contains information about the output locations for job checkpoint data.

  • JobEventDetails

    Details about the type and time events occurred related to the Amazon Braket job.

  • JobOutputDataConfig

    Specifies the path to the S3 location where you want to store job artifacts and the encryption key used to store them.

  • JobStoppingCondition

    Specifies limits for how long an Amazon Braket job can run.

  • JobSummary

    Provides summary information about an Amazon Braket job.

  • QuantumTaskQueueInfo

    Information about the queue for the specified quantum task.

  • QuantumTaskSummary

    Includes information about a quantum task.

  • S3DataSource

    Information about the data stored in Amazon S3 used by the Amazon Braket job.

  • ScriptModeConfig

    Contains information about the Python scripts used for entry and by an Amazon Braket job.

  • SearchDevicesFilter

    The filter to use for searching devices.

  • SearchJobsFilter

    A filter used to search for Amazon Braket jobs.

  • SearchQuantumTasksFilter

    A filter to use to search for tasks.

Enums

  • CancellationStatus
    When writing a match expression against CancellationStatus, 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.
  • CompressionType
    When writing a match expression against CompressionType, 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.
  • DeviceStatus
    When writing a match expression against DeviceStatus, 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.
  • DeviceType
    When writing a match expression against DeviceType, 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.
  • HybridJobAdditionalAttributeName
    When writing a match expression against HybridJobAdditionalAttributeName, 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.
  • InstanceType
    When writing a match expression against InstanceType, 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.
  • JobEventType
    When writing a match expression against JobEventType, 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.
  • JobPrimaryStatus
    When writing a match expression against JobPrimaryStatus, 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.
  • QuantumTaskAdditionalAttributeName
    When writing a match expression against QuantumTaskAdditionalAttributeName, 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.
  • QuantumTaskStatus
    When writing a match expression against QuantumTaskStatus, 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.
  • QueueName
    When writing a match expression against QueueName, 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.
  • QueuePriority
    When writing a match expression against QueuePriority, 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.
  • SearchJobsFilterOperator
    When writing a match expression against SearchJobsFilterOperator, 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.
  • SearchQuantumTasksFilterOperator
    When writing a match expression against SearchQuantumTasksFilterOperator, 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.