AWS IoT fleet wise Vehicles Decoder manifests and verhicle creation

[akashenji]

Using an iwg26 device and following the procedure below:
https://github.com/aws/aws-iot-fleetwise-edge/blob/main/docs/iwave-g26-tutorial/iwave-g26-tutorial.md#step-7-collect-gps-and-obd-data

While running demo.sh in Cloud Shell, the following error is returned:

Error Output from demo.sh:

Reading network interfaces from network-interface-obd.json
Reading network interfaces from network-interface-custom-location.json
Creating decoder manifest with network interfaces...

An error occurred (AccessDeniedException) when calling the CreateDecoderManifest operation: Account is not allow-listed to use edge first modeling features

Please let me know what this error means and whether this procedure is correct for creating the decoder manifests and vehicle.

[jayantjn]

Hi @akashenji, you are getting the AccessDeniedException as your account is not allowlisted for the gated features. These are the steps to request allowlisting for the AWS IoT FleetWise gated features:

• Go to https://support.console.aws.amazon.com/support/home#/
• Click 'Create case'
• Select service: 'Account', category: 'Other Account Issues', severity: 'General question'.
• Enter the subject: "Allow-listing for AWS IoT FleetWise gated features", description: "Please allow-list my account ID XXXXXXXXXXXX for AWS IoT FleetWise gated features."

You should be able to create the decoder manifest once the allowlisting is completed.
Please reach out if you have any further questions!

[akashenji]

Hi @jayantjn,
Thanks for the information.
I am able to create the manifest, vehicle, and campaigns now.
I have added my vehicle to the campaigns, and I can see that my devices are active and healthy.
Where can I see the data sent from the devices to the server, and what services need to be enabled to read the data in the cloud?

[jayantjn]

Hello @akashenji, the demo.sh script allows you to specify where your data should be stored using the --data-destination argument. You have three options:

1. TIMESTREAM (default) - Data will be stored in Amazon Timestream
2. S3 - Data will be uploaded to Amazon S3
3. IOT_TOPIC - Data will be published to an IoT topic

If you have run the script without using this data-destination argument, the data will automatically be stored in Amazon Timestream. When running the demo.sh script, you will see the name of the Timestream database in the terminal. To access your collected data, navigate to Amazon Timestream in the AWS Console where you can execute queries against this database.