Ingesting data to the cloud - AWS IoT FleetWise

Ingesting data to the cloud

AWS IoT FleetWise is in preview release and is subject to change. We recommend that you use the service only with test data, and not in production environments.

While AWS IoT FleetWise is in preview, you must download the preview AWS SDK and AWS CLI to use the API operations for this service. These API operations aren't available in the public AWS SDK or AWS CLI. For more information, see Preview AWS CLI and AWS SDKs.

The AWS IoT FleetWise Edge Agent software, when installed and running in vehicles, facilitates secure communication between your vehicles and the cloud.

Note
  • AWS IoT FleetWise is not intended for use in, or in association with, the operation of any hazardous environments or critical systems that may lead to serious bodily injury or death or cause environmental or property damage. Vehicle data collected through your use of AWS IoT FleetWise is for informational purposes only, and you may not use AWS IoT FleetWise to control or operate vehicle functions.

  • 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).

To ingest data to the cloud, do the following:

  1. Install the AWS IoT FleetWise Edge Agent software in your vehicle. For more information about how to work with the Edge Agent software, do the following to download the AWS IoT FleetWise Edge Agent software Developer Guide.

    1. Navigate to the AWS IoT FleetWise console.

    2. On the service home page, in the Get started with AWS IoT FleetWise section, choose Explore Edge Agent.

  2. Create or import a signal catalog containing signals that you'll use to create a vehicle model. For more information, see Create a signal catalog (AWS CLI) and Import a signal catalog (AWS CLI).

    Note
    • If you use the AWS IoT FleetWise console to create the first vehicle model, you don't need to manually create a signal catalog. When you create your first vehicle model, AWS IoT FleetWise automatically creates a signal catalog for you. For more information, see Create a vehicle model (console).

    • AWS IoT FleetWise currently supports a signal catalog for each AWS account per Region.

  3. Use signals in the signal catalog to create a vehicle model. For more information, see Create a vehicle model.

    Note
    • If you use the AWS IoT FleetWise console to create a vehicle model, you can upload .dbc files to import signals. .dbc is a file format that Controller Area Network (CAN bus) databases support. After the vehicle model is created, new signals are automatically added to the signal catalog. For more information, see Create a vehicle model (console).

    • If you use the CreateModelManifest API operation to create a vehicle model, you must use the UpdateModelManifest API operation to activate the vehicle model. For more information, see Update a vehicle model (AWS CLI).

    • If you use the AWS IoT FleetWise console to create a vehicle model, AWS IoT FleetWise automatically activates the vehicle model for you.

  4. Create a decoder manifest. The decoder manifest contains decoding information for every signal specified in the vehicle model that you created in the previous step. The decoder manifest is associated with the vehicle model that you created. For more information, see Create and manage decoder manifests.

    Note
    • If you use the CreateDecoderManifest API operation to create a decoder manifest, you must use the UpdateDecoderManifest API operation to activate the decoder manifest. For more information, see Update a decoder manifest (AWS CLI).

    • If you use the AWS IoT FleetWise console to create a decoder manifest, AWS IoT FleetWise automatically activates the decoder manifest for you.

  5. Create vehicles from the vehicle model. Vehicles created from the same vehicle model inherit the same group of signals. You must use AWS IoT Core to provision your vehicle before you can ingest data to the cloud. For more information, see Create, provision, and manage vehicles.

  6. (Optional) Create a fleet to represent a group of vehicles, and then associate individual vehicles with the fleet. This helps you manage multiple vehicles at the same time. For more information, see Create and manage fleets.

  7. Create campaigns. Campaigns are deployed to a vehicle or a fleet of vehicles. Campaigns give the Edge Agent software instructions on how to select, collect, and transfer data to the cloud. For more information, see Collect and transfer data with campaigns.

    Note

    You must use the UpdateCampaign API operation to approve the campaign, before AWS IoT FleetWise can deploy it to the vehicle or fleet. For more information, see Update a campaign (AWS CLI).

The Edge Agent software transfers vehicle data to a Timestream table. You can use Timestream to query your data, and use Amazon QuickSight or Grafana to visualize your data. For more information, see Processing and visualizing vehicle data.