Module aws_sdk_iotfleetwise::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS IoT FleetWise can respond with.

Structs

• Actuator

  A signal that represents a vehicle device such as the engine, heater, and door locks. Data from an actuator reports the state of a certain vehicle device.

• Attribute

  A signal that represents static information about the vehicle, such as engine type or manufacturing date.

• Branch

  A group of signals that are defined in a hierarchical structure.

• CampaignSummary

  Information about a campaign.

• CanDbcDefinition

  Configurations used to create a decoder manifest.

• CanInterface

  A single controller area network (CAN) device interface.

• CanSignal

  Information about a single controller area network (CAN) signal and the messages it receives and transmits.

• CloudWatchLogDeliveryOptions

  The log delivery option to send data to Amazon CloudWatch Logs.

• ConditionBasedCollectionScheme

  Information about a collection scheme that uses a simple logical expression to recognize what data to collect.

• CreateVehicleError

  An HTTP error resulting from creating a vehicle.

• CreateVehicleRequestItem

  Information about the vehicle to create.

• CreateVehicleResponseItem

  Information about a created vehicle.

• DecoderManifestSummary

  Information about a created decoder manifest. You can use the API operation to return this information about multiple decoder manifests.

• FleetSummary

  Information about a fleet.

• IamRegistrationResponse

  Information about registering an Identity and Access Management (IAM) resource so Amazon Web Services IoT FleetWise edge agent software can transfer your vehicle data to Amazon Timestream.

• IamResources

  The IAM resource that enables Amazon Web Services IoT FleetWise edge agent software to send data to Amazon Timestream.

• InvalidNetworkInterface

  A reason a vehicle network interface isn't valid.

• InvalidSignal

  A reason that a signal isn't valid.

• InvalidSignalDecoder

  A reason that a signal decoder isn't valid.

• ModelManifestSummary

  Information about a vehicle model (model manifest). You can use the API operation to return this information about multiple vehicle models.

• NetworkInterface

  Represents a node and its specifications in an in-vehicle communication network. All signal decoders must be associated with a network node.

• NodeCounts

  Information about the number of nodes and node types in a vehicle network.

• ObdInterface

  A network interface that specifies the On-board diagnostic (OBD) II network protocol.

• ObdSignal

  Information about signal messages using the on-board diagnostics (OBD) II protocol in a vehicle.

• Sensor

  An input component that reports the environmental condition of a vehicle.

• SignalCatalogSummary

  Information about a collection of standardized signals, which can be attributes, branches, sensors, or actuators.

• SignalDecoder

  Information about a signal decoder.

• SignalInformation

  Information about a signal.

• Tag

  A set of key/value pairs that are used to manage the resource.

• TimeBasedCollectionScheme

  Information about a collection scheme that uses a time period to decide how often to collect data.

• TimestreamRegistrationResponse

  Information about the registered Amazon Timestream resources or errors, if any.

• TimestreamResources

  The registered Amazon Timestream resources that Amazon Web Services IoT FleetWise edge agent software can transfer your vehicle data to.

• UpdateVehicleError

  An HTTP error resulting from updating the description for a vehicle.

• UpdateVehicleRequestItem

  Information about the vehicle to update.

• UpdateVehicleResponseItem

  Information about the updated vehicle.

• ValidationExceptionField

  A validation error due to mismatch between the expected data type, length, or pattern of the parameter and the input.

• VehicleStatus

  Information about the state of a vehicle and how it relates to the status of a campaign.

• VehicleSummary

  Information about a vehicle.

Enums

• CampaignStatus
  When writing a match expression against CampaignStatus, 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.
• CollectionScheme

  Specifies what data to collect and how often or when to collect it.

• Compression
  When writing a match expression against Compression, 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.
• DiagnosticsMode
  When writing a match expression against DiagnosticsMode, 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.
• FormattedVss

  Vehicle Signal Specification (VSS) is a precise language used to describe and model signals in vehicle networks. The JSON file collects signal specificiations in a VSS format.

• LogType
  When writing a match expression against LogType, 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.
• ManifestStatus
  When writing a match expression against ManifestStatus, 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.
• NetworkFileDefinition

  Specifications for defining a vehicle network.

• NetworkInterfaceFailureReason
  When writing a match expression against NetworkInterfaceFailureReason, 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.
• NetworkInterfaceType
  When writing a match expression against NetworkInterfaceType, 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.
• Node

  A general abstraction of a signal. A node can be specified as an actuator, attribute, branch, or sensor.

• NodeDataType
  When writing a match expression against NodeDataType, 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.
• RegistrationStatus
  When writing a match expression against RegistrationStatus, 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.
• SignalDecoderFailureReason
  When writing a match expression against SignalDecoderFailureReason, 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.
• SignalDecoderType
  When writing a match expression against SignalDecoderType, 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.
• SpoolingMode
  When writing a match expression against SpoolingMode, 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.
• TriggerMode
  When writing a match expression against TriggerMode, 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.
• UpdateCampaignAction
  When writing a match expression against UpdateCampaignAction, 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.
• UpdateMode
  When writing a match expression against UpdateMode, 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.
• ValidationExceptionReason
  When writing a match expression against ValidationExceptionReason, 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.
• VehicleAssociationBehavior
  When writing a match expression against VehicleAssociationBehavior, 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.
• VehicleState
  When writing a match expression against VehicleState, 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.