AWS IoT FleetWise will no longer be open to new customers as of April 30, 2026. Existing AWS IoT FleetWise customers can continue using the service. The [Guidance for Connected Mobility on AWS](https://aws.amazon.com/solutions/guidance/connected-mobility-on-aws/) provides guidance on how to develop and deploy modular services for connected mobility solutions that can be used to achieve equivalent capabilities as AWS IoT FleetWise. # What is AWS IoT FleetWise? AWS IoT FleetWise is a managed service that you can use to collect vehicle data and organize it in the cloud. You can use the collected data to improve vehicle quality, performance, and autonomy. With AWS IoT FleetWise, you can collect and organize data from vehicles that use different protocols and data formats. AWS IoT FleetWise helps to transform low-level messages into human-readable values and standardize the data format in the cloud for data analyses. You can also define data collection campaigns to control what vehicle data to collect and when to transfer that data to the cloud. When the vehicle data is in the cloud, you can use it for applications that analyze vehicle fleet health. This data can help you to identify potential maintenance issues, make in-vehicle infotainment systems smarter, and improve advanced technologies like autonomous driving and driver-assistance systems with analytics and machine learning (ML). The following diagram shows the basic architecture of AWS IoT FleetWise. ![\[Architecture of AWS IoT FleetWise\]](http://docs.aws.amazon.com/iot-fleetwise/latest/developerguide/images/architecture-diagram.png) **Topics** + [Benefits](#benefits) + [Use cases](#use-cases) + [Important notice](#important-notice) + [Are you new to AWS IoT FleetWise?](#first-time-user) + [Accessing AWS IoT FleetWise](#acessing-servicename) + [Pricing for AWS IoT FleetWise](#priding-servicename) + [Related services](#related-services) + [Key concepts and features of AWS IoT FleetWise](how-iotfleetwise-works.md) + [AWS Region and feature availability in AWS IoT FleetWise](fleetwise-regions.md) ## Benefits The key benefits of AWS IoT FleetWise are: **Collect vehicle data more intelligently** Improve data relevance with intelligent data collection that sends only the data you need to the cloud for analysis. **Easily analyze standardized, fleet-wide data** Analyze standardized data from a fleet of vehicles without needing to develop a custom data collection or logging system. **Automatic data synchronization in the cloud** Gain a unified view of data collected from both standard sensors (telemetry data) and vision systems (data from cameras, radars, and lidars), and keep it automatically synchronized in the cloud. AWS IoT FleetWise keeps both structured and unstructured vision system data, metadata, and standard sensor data automatically synchronized in the cloud. This streamlines the process to assemble a full picture view of events and gain insights. **Store data at the Edge and forward it under optimal conditions** Reduce transmission costs by temporarily storing data on vehicles. You can forward selected data to the cloud under specified, optimal conditions--such as when vehicles connect to Wi-Fi. **Note** Vision system data is in preview release and is subject to change. ## Use cases The scenarios in which you can use AWS IoT FleetWise include the following: **Train AI/ML models** Continuously improve machine learning models used for autonomous and advanced driver assistance systems by collecting data from production vehicles. **Enhance the digital customer experience** Use data from infotainment systems to make in-vehicle audiovisual content and in-app insights more relevant. **Maintain vehicle fleet health ** Use insights from fleet data to monitor EV battery health and charge levels, manage maintenance schedules, analyze fuel consumption, and more. **Create and manage commands** Use commands to execute commands on a vehicle from the cloud. You can remotely send commands to a vehicle, and within a few seconds, the vehicle will execute the command. For example, you can configure commands to lock a vehicle’s door or set the temperature. **Create and manage state templates** State templates provide a mechanism for vehicle owners to track the state of their vehicle. The AWS IoT FleetWise Edge Agent that runs on the vehicle collects and sends signal updates to the cloud. ## Important notice Vehicle data collected through your use of AWS IoT FleetWise is intended for informational purposes only (including to help you train cloud-based artificial intelligence and machine learning models), and you may not use AWS IoT FleetWise to control or operate vehicle functions. You are solely responsible for all liability that may arise in connection with any use outside of AWS IoT FleetWise's intended purpose and in any manner contrary to applicable vehicle regulations. Vehicle data collected through your use of AWS IoT FleetWise should be evaluated for accuracy as appropriate for your use case, including for purposes of meeting any compliance obligations you may have under applicable vehicle safety regulations (such as safety monitoring and reporting obligations). Such evaluation should include collecting and reviewing information through other industry standard means and sources (such as reports from drivers of vehicles). You and your End Users are solely responsible for all decisions made, advice given, actions taken, and failures to take action based on your use of AWS IoT FleetWise. ## Are you new to AWS IoT FleetWise? If you're new to AWS IoT FleetWise, we recommend that you begin by reading the following sections: + [Key concepts and features of AWS IoT FleetWise](how-iotfleetwise-works.md) + [Set up AWS IoT FleetWise](setting-up.md) + [Tutorial: Get started with AWS IoT FleetWise](fleetwise-getting-started.md) + [Ingest AWS IoT FleetWise data to the cloud](data-ingestion.md) ## Accessing AWS IoT FleetWise You can use the AWS IoT FleetWise console or API to access AWS IoT FleetWise. ## Pricing for AWS IoT FleetWise Vehicles send data to the cloud through MQTT messages. You pay at the end of each month for the vehicles that you created in AWS IoT FleetWise. You also pay for messages that you collect from vehicles. For current information about pricing, see the [AWS IoT FleetWise Pricing](https://aws.amazon.com/iot-fleetwise/pricing/) page. To learn more about the MQTT messaging protocol, see [MQTT](https://docs.aws.amazon.com/iot/latest/developerguide/mqtt.html) in the *AWS IoT Core Developer Guide*. ## Related services AWS IoT FleetWise integrates with the following AWS services to improve the availability and scalability of your cloud solutions. + **AWS IoT Core** – Register and control AWS IoT devices that upload vehicle data to AWS IoT FleetWise, and remotely send commands to a vehicle. For more information, see [What is AWS IoT](https://docs.aws.amazon.com/iot/latest/developerguide/what-is-aws-iot.html) in the *AWS IoT Developer Guide*. + **Amazon Timestream** – Use a time series database to store and analyze your vehicle data. For more information, see [What is Amazon Timestream](https://docs.aws.amazon.com/timestream/latest/developerguide/what-is-timestream.html) in the *Amazon Timestream Developer Guide*. + **Amazon S3** – Use an object storage service to store and manage your vehicle data. For more information, see [What is Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html) in the *Amazon Simple Storage Service User Guide*. # Key concepts and features of AWS IoT FleetWise **Important** Access to certain AWS IoT FleetWise features is currently gated. For more information, see [AWS Region and feature availability in AWS IoT FleetWise](fleetwise-regions.md). The following sections provide an overview of AWS IoT FleetWise service components and how they interact. After you read this introduction, see the [Set up AWS IoT FleetWise](setting-up.md) section to learn how to set up AWS IoT FleetWise. **Topics** + [Key concepts](#key-concepts) + [Features of AWS IoT FleetWise](#iotfleetwise-feature-overview) ## Key concepts AWS IoT FleetWise provides a vehicle modeling framework for you to model your vehicle and its sensors and actuators in the cloud. To enable the secure communication between your vehicle and the cloud, AWS IoT FleetWise also provides a reference implementation to help you develop Edge Agent software that you can install in your vehicle. You can define data collection schemes in the cloud and deploy them to your vehicle. The Edge Agent software running in your vehicle uses data collection schemes to control what data to collect and when to transfer it to the cloud. The following are the core concepts of AWS IoT FleetWise. **Signal** Signals are fundamental structures that you define to contain vehicle data and its metadata. A signal can be an attribute, a branch, a sensor, or an actuator. For example, you can create a sensor to receive in-vehicle temperature values, and to store its metadata, including a sensor name, a data type, and a unit. For more information, see [Manage AWS IoT FleetWise signal catalogs](signal-catalogs.md). **Attribute** Attributes represent static information that generally doesn't change, such as manufacturer and manufacturing date. **Branch** Branches represent signals in a nested structure. Branches demonstrate signal hierarchies. For example, the `Vehicle` branch has a child branch, `Powertrain`. The `Powertrain` branch has a child branch, `combustionEngine`. To locate the `combustionEngine` branch, use the `Vehicle.Powertrain.combustionEngine` expression. **Sensor** Sensor data reports the current state of the vehicle and change over time, as the state of the vehicle changes, such as fluid levels, temperatures, vibrations, or voltage. **Actuator** Actuator data reports the state of a vehicle device, such as motors, heaters, and door locks. Changing the state of a vehicle device can update actuator data. For example, you can define an actuator to represent the heater. The actuator receives new data when you turn on or off the heater. **Custom structure** A custom structure (also known as a struct) represents a complex or higher-order data structure. It facilitates logical binding or grouping of data that originates from the same source. A struct is used when data is read or written in an atomic operation, such as to represent a complex data type or higher-order shape. A signal of struct type is defined in the signal catalog using a reference to a struct data type instead of a primitive data type. Structs can be used for all types of signals including sensors, attributes, actuators, and vision system data types. If a signal of struct type is sent or received, AWS IoT FleetWise expects all included items to have valid values, so all items are mandatory. For example, if a struct contains the items Vehicle.Camera.Image.height, Vehicle.Camera.Image.width, and Vehicle.Camera.Image.data – it's expected that the sent signal contains values for all of these items. Vision system data is in preview release and is subject to change. **Custom property** A custom property represents a member of the complex data structure. The data type of the property can be either primitive or another struct. When representing a higher-order shape using a struct and custom property, the intended higher-order shape is always defined and visioned as a tree structure. The custom property is used to define all the leaf nodes while the struct is used to define all the non-leaf nodes. **Signal catalog** A signal catalog contains a collection of signals. Signals in a signal catalog can be used to model vehicles that use different protocols and data formats. For example, there are two cars made by different automakers: one uses the Control Area Network (CAN bus) protocol; the other one uses the On-board Diagnostics (OBD) protocol. You can define a sensor in the signal catalog to receive in-vehicle temperature values. This sensor can be used to represent the thermocouples in both cars. For more information, see [Manage AWS IoT FleetWise signal catalogs](signal-catalogs.md). **Vehicle model (model manifest)** Vehicle models are declarative structures that you can use to standardize the format of your vehicles and to define relationships between signals in the vehicles. Vehicle models enforce consistent information across multiple vehicles of the same type. You add signals to create vehicle models. For more information, see [Manage AWS IoT FleetWise vehicle modelsVehicle models](vehicle-models.md). **Decoder manifest** Decoder manifests contain decoding information for each signal in vehicle models. Sensors and actuators in vehicles transmit low-level messages (binary data). With decoder manifests, AWS IoT FleetWise is able to transform binary data into human-readable values. Every decoder manifest is associated with a vehicle model. For more information, see [Manage AWS IoT FleetWise decoder manifests](decoder-manifests.md). **Network interface** Contains information about the protocol that the in-vehicle network uses. AWS IoT FleetWise supports the following protocols. **Controller Area Network (CAN bus)** A protocol that defines how data is communicated between electronic control units (ECUs). ECUs can be the engine control unit, airbags, or the audio system. **On-board diagnostic (OBD) II** A further developed protocol that defines how self-diagnostic data is communicated between ECUs. It provides a number of standard diagnostic trouble codes (DTCs) that help identify what is wrong with your vehicle. **Vehicle middleware** The vehicle middleware defined as a type of network interface. Examples of vehicle middleware include Robot Operating System (ROS 2) and Scalable service-Oriented MiddlewarE over IP (SOME/IP). AWS IoT FleetWise supports ROS 2 middleware for vision system data. **Custom interfaces** You can also use your own interface to decode signals at the Edge. This can save you time since you don't need to create decoding rules in the cloud. **Signal decoder** Provides detailed decoding information for a specific signal. Every signal specified in the vehicle model must be paired with a signal decoder. If the decoder manifest contains CAN network interfaces, it must contain CAN decoder signals. If the decoder manifest contains OBD network interfaces, it must contain OBD signal decoders. The decoder manifest must contain message signal decoders if it also contains vehicle middleware interfaces. Or, if the decoder manifest contains custom decoding interfaces, it must also contain custom decoding signals. **Vehicle** A virtual representation of your physical vehicle, such a car or a truck. Vehicles are instances of vehicle models. Vehicles created from the same vehicle model inherit the same group of signals. Each vehicle corresponds to an AWS IoT thing. **Fleet** A fleet represents a group of vehicles. Before you can easily manage a fleet of vehicles, you must associate individual vehicles to a fleet. **Campaign** Contains data collection schemes. You define a campaign in the cloud and deploy it to a vehicle or fleet. Campaigns give the Edge Agent software instructions on how to select, collect, and transfer data to the cloud. **Data partition** Configure partitioned data in a campaign to temporarily store signal data. You configure when and how to forward the data to the cloud. **Data collection scheme** Data collection schemes give the Edge Agent software instructions on how to collect data. Currently, AWS IoT FleetWise supports the condition-based collection scheme and the time-based collection scheme. **Condition-based collection scheme** Use a logical expression to recognize what data to collect. The Edge Agent software collects data when the condition is met. For example, if the expression is `$variable.myVehicle.InVehicleTemperature >35.0`, the Edge Agent software collects temperature values that are greater than 35.0. **Time-based collection scheme** Specify a time period in milliseconds to define how often to collect data. For example, if the time period is 10,000 milliseconds, the Edge Agent software collects data once every 10 seconds. **Commands** Commands execute commands on a vehicle from the cloud. You can remotely send commands to a vehicle, and within a few seconds, the vehicle will execute the command. For example, you can configure commands to lock a vehicle’s door or set the temperature. The command is a resource that's managed by AWS IoT Device Management. It contains reusable configurations that are applied when sending a command execution to the vehicle. For more information, see [AWS IoT commands](https://docs.aws.amazon.com/iot/latest/developerguide/iot-remote-command.html) in the *AWS IoT Core Developer Guide*. **State templates** State templates provide a mechanism for vehicle owners to track the state of their vehicle. The Edge Agent software Agent that runs on the vehicle collects and sends signal updates to the cloud. Each state template contains a list of signals from which data is collected. ## Features of AWS IoT FleetWise The following are the key features of AWS IoT FleetWise. **Vehicle modeling** Build virtual representations of your vehicles and apply a common format to organize vehicle signals. AWS IoT FleetWise supports [Vehicle Signal Specification (VSS)](https://covesa.github.io/vehicle_signal_specification/introduction/overview/) that you can use to standardize vehicle signals. **Scheme-based data collection** Define schemes to transfer only high-value vehicle data to the cloud. You can define condition-based schemes to control what data to collect, such as data in-vehicle temperature values that are greater than 40 degrees. You can also define time-based schemes to control how often to collect data. **Edge Agent for AWS IoT FleetWise software** The Edge Agent software running in vehicles facilitates communication between vehicles and the cloud. While vehicles are connected to the cloud, the Edge Agent software continually receives data collection schemes and collects data accordingly. # AWS Region and feature availability in AWS IoT FleetWise For a list of AWS Regions that support AWS IoT FleetWise, see [AWS IoT FleetWise endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/iotfleetwise.html). AWS IoT FleetWise features differ in their regional support. **Note** Access to the Asia Pacific (Mumbai) Region and some AWS IoT FleetWise features are currently gated. To request access to this AWS Region and all gated features, contact your account manager or the [AWS Support Center](https://console.aws.amazon.com/support/home#/). The following table shows feature support by Region: | Features/Regions | US East (N. Virginia) | Europe (Frankfurt) | Asia Pacific (Mumbai) NOTE: Gated access only | | --- | --- | --- | --- | | [Signal catalogs](signal-catalogs.md) | Yes | Yes | Gated | | [Vehicle models](vehicle-models.md) | Yes | Yes | Gated | | [Decoder manifests](decoder-manifests.md) | Yes | Yes | Gated | | [Vehicles](vehicles.md) | Yes | Yes | Gated | | [Fleets](fleets.md) | Yes | Yes | Gated | | [Campaigns](campaigns.md) | Yes | Yes | Gated | | [Vision system data](define-signal.md) (in preview release) | Yes | Yes | Gated | | [MQTT topic as a campaign data destination](create-campaign.md) | Gated | Gated | Gated | | [Store and forward](store-and-forward.md) | Gated | Gated | Gated | | [Commands](remote-commands.md) | Gated | Gated | Gated | | [Last known state](last-known-state.md) | Gated | Gated | Gated | | [Network agnostic data collection using a custom decoding interface](network-agnostic-data-collection.md) | Gated | Gated | Gated | | [Diagnostic trouble code (DTC) fetching\$1](diagnostic-trouble-codes.md) | Gated | Gated | Gated | \$1DTC fetching offers a range of capabilities that go beyond basic DTC data retrieval. This functionality includes custom features that enable you to define functions at the edge and invoke them by name within condition-based campaign expressions. Additionally, it supports the collection of unbounded strings, providing flexible string data type handling. The Edge Agent can fetch data either on a periodic basis or triggered by specific conditions, enhancing its adaptability and efficiency in data collection processes. For more information, see the [custom function guide](https://github.com/aws/aws-iot-fleetwise-edge/blob/main/docs/dev-guide/custom-function-dev-guide.md) and the [DTC data collection reference implementation](https://github.com/aws/aws-iot-fleetwise-edge/blob/main/docs/dev-guide/edge-agent-uds-dtc-dev-guide.md#dtc_query-function-implementation) in the *Edge Agent Developer Guide*.