Expand description
Data structures used by operation inputs/outputs.
Modules§
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.
Updating actuator data can change the state of a device. For example, you can turn on or off the heater by updating its actuator data.
- 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.
- Campaign
Summary Information about a campaign.
You can use the API operation to return this information about multiple created campaigns.
- CanDbc
Definition 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.
- Cloud
Watch LogDelivery Options The log delivery option to send data to Amazon CloudWatch Logs.
- Condition
Based Collection Scheme Information about a collection scheme that uses a simple logical expression to recognize what data to collect.
- Condition
Based Signal Fetch Config Specifies the condition under which a signal fetch occurs.
- Create
Vehicle Error An HTTP error resulting from creating a vehicle.
- Create
Vehicle Request Item Information about the vehicle to create.
- Create
Vehicle Response Item Information about a created vehicle.
- Custom
Decoding Interface Represents a custom network interface as defined by the customer.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Custom
Decoding Signal Information about signals using a custom decoding protocol as defined by the customer.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Custom
Property Represents a member of the complex data structure. The data type of the property can be either primitive or another
struct
.- Custom
Struct The custom structure represents a complex or higher-order data structure.
- Data
Partition The configuration for signal data storage and upload options. You can only specify these options when the campaign's spooling mode is
TO_DISK
.Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Data
Partition Storage Options Size, time, and location options for the data partition.
- Data
Partition Upload Options The upload options for the data partition. If upload options are specified, you must also specify storage options. See DataPartitionStorageOptions.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Decoder
Manifest Summary Information about a created decoder manifest. You can use the API operation to return this information about multiple decoder manifests.
- Fleet
Summary Information about a fleet.
You can use the API operation to return this information about multiple fleets.
- IamRegistration
Response 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.
For more information, see IAM roles in the Identity and Access Management User Guide.
- Invalid
Network Interface A reason a vehicle network interface isn't valid.
- Invalid
Signal A reason that a signal isn't valid.
- Invalid
Signal Decoder A reason that a signal decoder isn't valid.
- Message
Signal The decoding information for a specific message which support higher order data types.
- Model
Manifest Summary Information about a vehicle model (model manifest). You can use the API operation to return this information about multiple vehicle models.
- Mqtt
Topic Config The MQTT topic to which the Amazon Web Services IoT FleetWise campaign routes data. For more information, see Device communication protocols in the Amazon Web Services IoT Core Developer Guide.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Network
Interface Represents a node and its specifications in an in-vehicle communication network. All signal decoders must be associated with a network node.
To return this information about all the network interfaces specified in a decoder manifest, use the API operation.
- Node
Counts 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.
- OnChange
State Template Update Strategy Vehicles associated with the state template will stream telemetry data when there is a change.
- Periodic
State Template Update Strategy Vehicles associated with the state template will stream telemetry data during a specified time period.
- Ros2
Primitive Message Definition Represents a ROS 2 compliant primitive type message of the complex data structure.
- S3Config
The Amazon S3 bucket where the Amazon Web Services IoT FleetWise campaign sends data. Amazon S3 is an object storage service that stores data as objects within buckets. For more information, see Creating, configuring, and working with Amazon S3 buckets in the Amazon Simple Storage Service User Guide.
- Sensor
An input component that reports the environmental condition of a vehicle.
You can collect data about fluid levels, temperatures, vibrations, or battery voltage from sensors.
- Signal
Catalog Summary Information about a collection of standardized signals, which can be attributes, branches, sensors, or actuators.
- Signal
Decoder Information about a signal decoder.
- Signal
Fetch Information Information about the signal to be fetched.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Signal
Information Information about a signal.
- State
Template Association The state template associated with a vehicle. State templates contain state properties, which are signals that belong to a signal catalog that is synchronized between the Amazon Web Services IoT FleetWise Edge and the Amazon Web Services Cloud.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- State
Template Summary Information about a state template.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Storage
Maximum Size The maximum storage size for the data partition.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Storage
Minimum Time ToLive Information about the minimum amount of time that data will be kept.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Structured
Message Field Name AndData Type Pair Represents a
StructureMessageName
toDataType
map element.- Structured
Message List Definition Represents a list type node of the complex data structure.
- Tag
A set of key/value pairs that are used to manage the resource.
- Time
Based Collection Scheme Information about a collection scheme that uses a time period to decide how often to collect data.
- Time
Based Signal Fetch Config Used to configure a frequency-based vehicle signal fetch.
- Time
Period The length of time between state template updates.
- Timestream
Config The Amazon Timestream table where the Amazon Web Services IoT FleetWise campaign sends data. Timestream stores and organizes data to optimize query processing time and to reduce storage costs. For more information, see Data modeling in the Amazon Timestream Developer Guide.
- Timestream
Registration Response Information about the registered Amazon Timestream resources or errors, if any.
- Timestream
Resources The registered Amazon Timestream resources that Amazon Web Services IoT FleetWise edge agent software can transfer your vehicle data to.
- Update
Vehicle Error An HTTP error resulting from updating the description for a vehicle.
- Update
Vehicle Request Item Information about the vehicle to update.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Update
Vehicle Response Item Information about the updated vehicle.
- Validation
Exception Field A validation error due to mismatch between the expected data type, length, or pattern of the parameter and the input.
- Vehicle
Middleware The vehicle middleware defined as a type of network interface. Examples of vehicle middleware include
ROS2
andSOME/IP
.- Vehicle
Status Information about a campaign associated with a vehicle.
- Vehicle
Summary Information about a vehicle.
To return this information about vehicles in your account, you can use the API operation.
Enums§
- Campaign
Status - 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. - Collection
Scheme 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. - Data
Destination Config The destination where the campaign sends data. You can send data to an MQTT topic, or store it in Amazon S3 or Amazon Timestream.
- Data
Format - When writing a match expression against
DataFormat
, 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. - Default
ForUnmapped Signals Type - When writing a match expression against
DefaultForUnmappedSignalsType
, 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. - Diagnostics
Mode - 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. - Encryption
Status - When writing a match expression against
EncryptionStatus
, 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. - Encryption
Type - When writing a match expression against
EncryptionType
, 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. - Formatted
Vss 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.
- List
Response Scope - When writing a match expression against
ListResponseScope
, 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. - 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. - Manifest
Status - 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. - Network
File Definition Specifications for defining a vehicle network.
- Network
Interface Failure Reason - 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. - Network
Interface Type - 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.
- Node
Data Encoding - When writing a match expression against
NodeDataEncoding
, 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
Data Type - 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. - Primitive
Message Definition Represents a primitive type node of the complex data structure.
- Registration
Status - 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. - Ros2
Primitive Type - When writing a match expression against
Ros2PrimitiveType
, 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. - Signal
Decoder Failure Reason - 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. - Signal
Decoder Type - 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. - Signal
Fetch Config The configuration of the signal fetch operation.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Signal
Node Type - When writing a match expression against
SignalNodeType
, 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. - Signal
Value Type - When writing a match expression against
SignalValueType
, 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. - Spooling
Mode - 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. - State
Template Update Strategy The update strategy for the state template. Vehicles associated with the state template can stream telemetry data with either an
onChange
orperiodic
update strategy.Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
- Storage
Compression Format - When writing a match expression against
StorageCompressionFormat
, 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. - Storage
Maximum Size Unit - When writing a match expression against
StorageMaximumSizeUnit
, 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. - Storage
Minimum Time ToLive Unit - When writing a match expression against
StorageMinimumTimeToLiveUnit
, 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. - Structured
Message The structured message for the message signal. It can be defined with either a
primitiveMessageDefinition
,structuredMessageListDefinition
, orstructuredMessageDefinition
recursively.- Structured
Message List Type - When writing a match expression against
StructuredMessageListType
, 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. - Time
Unit - When writing a match expression against
TimeUnit
, 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. - Trigger
Mode - 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. - Update
Campaign Action - 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. - Update
Mode - 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. - Validation
Exception Reason - 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. - Vehicle
Association Behavior - 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. - Vehicle
Middleware Protocol - When writing a match expression against
VehicleMiddlewareProtocol
, 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. - Vehicle
State - 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.