Update default data destination to S3

Author: jayantjn

docs/dev-guide/can-over-someip-demo.md

@@ -7,8 +7,8 @@ available to nodes on the Ethernet network.
 
 This demo generates CAN data on a virtual CAN bus, and bridges this data onto SOME/IP. The Reference
 Implementation for AWS IoT FleetWise (FWE) is then provisioned and run to collect the CAN data from
-SOME/IP and upload it to the cloud. The data is then downloaded from Amazon Timestream and plotted
-in an HTML graph format.
+SOME/IP and upload it to the cloud. The data is then downloaded from the specified data destination
+and plotted in an HTML graph format.
 
 The following diagram illustrates the dataflow and artifacts consumed and produced by this demo:
 
@@ -227,8 +227,8 @@ collect data from it.
    The demo script:
 
    1. Registers your AWS account with AWS IoT FleetWise, if not already registered.
-   1. Creates an Amazon Timestream database and table.
-   1. Creates IAM role and policy required for the service to write data to Amazon Timestream.
+   1. Creates an S3 bucket with a bucket policy that allows AWS IoT FleetWise to write data to the
+      bucket.
    1. Creates a signal catalog based on `can-nodes.json`.
    1. Creates a model manifest that references the signal catalog with all of the CAN signals.
    1. Activates the model manifest.
@@ -242,12 +242,29 @@ collect data from it.
    1. Creates a campaign from `campaign-brake-event.json` that contains a condition-based collection
       scheme to capture the engine torque and the brake pressure when the brake pressure is above
       7000, and targets the campaign at the fleet.
+   1. The data uploaded to S3 would be in JSON format, or Parquet format if the
+      `--s3-format PARQUET` option is passed.
    1. Approves the campaign.
    1. Waits until the campaign status is `HEALTHY`, which means the campaign has been deployed to
       the fleet.
-   1. Waits 30 seconds and then downloads the collected data from Amazon Timestream.
+   1. Wait 20 minutes for the data to propagate to S3 and then download it.
    1. Saves the data to an HTML file.
 
+   If `TIMESTREAM` upload is enabled (**Note**: Amazon Timestream for Live Analytics is only
+   available to customers who have already been onboarded in that region. See
+   [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html)),
+   the demo script will instead:
+
+   1. Creates an Amazon Timestream database and table.
+   1. Creates IAM role and policy required for the service to write data to Amazon Timestream.
+   1. Creates a campaign from `campaign-brake-event.json` that contains a condition-based collection
+      scheme to capture the engine torque and the brake pressure when the brake pressure is above
+      7000, and targets the campaign at the fleet.
+   1. Waits 30 seconds and then downloads the collected data from Amazon Timestream.
+   1. Save the data to an HTML file.
+
+   This script will not delete Amazon Timestream or S3 resources.
+
 1. When the script completes, a path to an HTML file is given. _On your local machine_, use `scp` to
    download it, then open it in your web browser:
 
@@ -259,15 +276,18 @@ collect data from it.
    simulated brake pressure signal. As you can see that when hard braking events occur (value above
    7000), collection is triggered and the engine torque signal data is collected.
 
-   Alternatively, if your AWS account is enrolled with Amazon QuickSight or Amazon Managed Grafana,
-   you may use them to browse the data from Amazon Timestream directly.
+   Alternatively, if your upload destination was set to `TIMESTREAM` and AWS account is enrolled
+   with Amazon QuickSight or Amazon Managed Grafana, you may use them to browse the data from Amazon
+   Timestream directly. **Note**: Amazon Timestream for Live Analytics is only available to
+   customers who have already been onboarded in that region. See
+   [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html).
 
    ![](./images/collected_data_plot.png)
 
 ## Clean up
 
 1. Run the following _on the development machine_ to clean up resources created by the
-   `provision.sh` and `demo.sh` scripts. **Note:** The Amazon Timestream resources are not deleted.
+   `provision.sh` and `demo.sh` scripts. **Note:** The S3 resources are not deleted.
 
    ```bash
    cd ~/aws-iot-fleetwise-edge/tools/cloud \

docs/dev-guide/edge-agent-dev-guide-nxp-s32g.md

@@ -175,7 +175,7 @@ mkdir -p ~/aws-iot-fleetwise-deploy \
 ## Clean up
 
 1. Run the following _on the development machine_ to clean up resources created by the
-   `provision.sh` and `demo.sh` scripts. **Note:** The Amazon Timestream resources are not deleted.
+   `provision.sh` and `demo.sh` scripts. **Note:** The S3 resources are not deleted.
 
    ```bash
    cd ~/aws-iot-fleetwise-edge/tools/cloud \

docs/dev-guide/edge-agent-dev-guide-renesas-rcar-s4.md

@@ -191,7 +191,7 @@ mkdir -p ~/aws-iot-fleetwise-deploy \
 ## Clean up
 
 1. Run the following _on the development machine_ to clean up resources created by the
-   `provision.sh` and `demo.sh` scripts. **Note:** The Amazon Timestream resources are not deleted.
+   `provision.sh` and `demo.sh` scripts. **Note:** The S3 resources are not deleted.
 
    ```bash
    cd ~/aws-iot-fleetwise-edge/tools/cloud \

docs/dev-guide/edge-agent-dev-guide.md

@@ -168,9 +168,12 @@ collect data from it.
       --campaign-file campaign-brake-event.json
    ```
 
-   - (Optional) To enable S3 upload, append the option `--data-destination S3`. By default the
-     upload format will be JSON. You can change this to Parquet format for S3 by passing
-     `--s3-format PARQUET`.
+   - The default `--data-destination` is S3, and the default upload format is JSON. You can change
+     this to Parquet format for S3 by passing `--s3-format PARQUET`.
+   - (Optional) To enable Amazon Timestream as destination, add the flag
+     `--data-destination TIMESTREAM`. **Note**: Amazon Timestream for Live Analytics is only
+     available to customers who are already onboarded in that region. See
+     [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html).
    - (Optional) To enable IoT topic as destination, add the flag `--data-destination IOT_TOPIC`. To
      define the custom IoT topic use the flag `--iot-topic <TOPIC_NAME>`. Note: The IoT topic data
      destination is a "gated" feature of AWS IoT FleetWise for which you will need to request
@@ -188,8 +191,8 @@ collect data from it.
    The demo script:
 
    1. Registers your AWS account with AWS IoT FleetWise, if not already registered.
-   1. Creates an Amazon Timestream database and table.
-   1. Creates IAM role and policy required for the service to write data to Amazon Timestream.
+   1. Creates an S3 bucket with a bucket policy that allows AWS IoT FleetWise to write data to the
+      bucket.
    1. Creates a signal catalog based on `can-nodes.json`.
    1. Creates a model manifest that references the signal catalog with all of the CAN signals.
    1. Activates the model manifest.
@@ -203,19 +206,25 @@ collect data from it.
    1. Creates a campaign from `campaign-brake-event.json` that contains a condition-based collection
       scheme to capture the engine torque and the brake pressure when the brake pressure is above
       7000, and targets the campaign at the fleet.
+   1. The data uploaded to S3 would be in JSON format, or Parquet format if the
+      `--s3-format PARQUET` option is passed.
    1. Approves the campaign.
    1. Waits until the campaign status is `HEALTHY`, which means the campaign has been deployed to
       the fleet.
-   1. Waits 30 seconds and then downloads the collected data from Amazon Timestream.
+   1. Wait 20 minutes for the data to propagate to S3 and then download it.
    1. Saves the data to an HTML file.
 
-   If S3 upload is enabled, the demo script will instead:
+   If `TIMESTREAM` upload is enabled (**Note**: Amazon Timestream for Live Analytics is only
+   available to customers who have already been onboarded in that region. See
+   [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html)),
+   the demo script will instead:
 
-   1. Create an S3 bucket with a bucket policy that allows AWS IoT FleetWise to write data to the
-      bucket.
-   1. Creates a campaign from `campaign-brake-event.json` to upload the data to S3 in JSON format,
-      or Parquet format if the `--s3-format PARQUET` option is passed.
-   1. Wait 20 minutes for the data to propagate to S3 and then download it.
+   1. Creates an Amazon Timestream database and table.
+   1. Creates IAM role and policy required for the service to write data to Amazon Timestream.
+   1. Creates a campaign from `campaign-brake-event.json` that contains a condition-based collection
+      scheme to capture the engine torque and the brake pressure when the brake pressure is above
+      7000, and targets the campaign at the fleet.
+   1. Waits 30 seconds and then downloads the collected data from Amazon Timestream.
    1. Save the data to an HTML file.
 
    This script will not delete Amazon Timestream or S3 resources.
@@ -229,8 +238,11 @@ collect data from it.
    simulated brake pressure signal. As you can see that when hard braking events occur (value above
    7000), collection is triggered and the engine torque signal data is collected.
 
-   Alternatively, if your AWS account is enrolled with Amazon QuickSight or Amazon Managed Grafana,
-   you may use them to browse the data from Amazon Timestream directly.
+   Alternatively, if your upload destination was set to `TIMESTREAM` and AWS account is enrolled
+   with Amazon QuickSight or Amazon Managed Grafana, you may use them to browse the data from Amazon
+   Timestream directly. **Note**: Amazon Timestream for Live Analytics is only available to
+   customers who have already been onboarded in that region. See
+   [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html).
 
    ![](./images/collected_data_plot.png)
 
@@ -452,9 +464,12 @@ collect data from it.
       --campaign-file campaign-brake-event.json
    ```
 
-   - (Optional) To enable S3 upload, append the option `--data-destination S3`. By default the
-     upload format will be JSON. You can change this to Parquet format by passing
-     `--s3-format PARQUET`.
+   - The default `--data-destination` is S3, and the default upload format is JSON. You can change
+     this to Parquet format for S3 by passing `--s3-format PARQUET`.
+   - (Optional) To enable Amazon Timestream as destination, add the flag
+     `--data-destination TIMESTREAM`. **Note**: Amazon Timestream for Live Analytics is only
+     available to customers who are already onboarded in that region. See
+     [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html).
    - (Optional) To enable IoT topic as destination, add the flag `--data-destination IOT_TOPIC` To
      define the custom IoT topic use the flag `--iot-topic <TOPIC_NAME>`. Note: The IoT topic data
      destination is a "gated" feature of AWS IoT FleetWise for which you will need to request
@@ -468,8 +483,8 @@ collect data from it.
    The demo script:
 
    1. Registers your AWS account with AWS IoT FleetWise, if not already registered.
-   1. Creates an Amazon Timestream database and table.
-   1. Creates IAM role and policy required for the service to write data to Amazon Timestream.
+   1. Creates an S3 bucket with a bucket policy that allows AWS IoT FleetWise to write data to the
+      bucket.
    1. Creates a signal catalog based on `can-nodes.json`.
    1. Creates a model manifest that references the signal catalog with all of the CAN signals.
    1. Activates the model manifest.
@@ -483,22 +498,27 @@ collect data from it.
    1. Creates a campaign from `campaign-brake-event.json` that contains a condition-based collection
       scheme to capture the engine torque and the brake pressure when the brake pressure is above
       7000, and targets the campaign at the fleet.
+   1. The data uploaded to S3 would be in JSON format, or Parquet format if the
+      `--s3-format PARQUET` option is passed.
    1. Approves the campaign.
    1. Waits until the campaign status is `HEALTHY`, which means the campaign has been deployed to
       the fleet.
-   1. Waits 30 seconds and then downloads the collected data from Amazon Timestream.
+   1. Wait 20 minutes for the data to propagate to S3 and then download it.
    1. Saves the data to an HTML file.
 
-   If S3 upload is enabled, the demo script will additionally:
+   If `TIMESTREAM` upload is enabled, the demo script will instead:
 
-   1. Create an S3 bucket with a bucket policy that allows AWS IoT FleetWise to write data to the
-      bucket.
-   1. Creates an additional campaign from `campaign-brake-event.json` to upload the data to S3 in
-      JSON format, or Parquet format if the `--s3-format PARQUET` option is passed.
-   1. Wait 20 minutes for the data to propagate to S3 and then download it.
-   1. Save the data to an HTML file.
+   **Note**: Amazon Timestream for Live Analytics is only available to customers who have already
+   been onboarded in that region. See
+   [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html).
 
-   This script will not delete Amazon Timestream or S3 resources.
+   1. Creates an Amazon Timestream database and table.
+   1. Creates IAM role and policy required for the service to write data to Amazon Timestream.
+   1. Creates a campaign from `campaign-brake-event.json` that contains a condition-based collection
+      scheme to capture the engine torque and the brake pressure when the brake pressure is above
+      7000, and targets the campaign at the fleet.
+   1. Waits 30 seconds and then downloads the collected data from Amazon Timestream.
+   1. Save the data to an HTML file. This script will not delete Amazon Timestream or S3 resources.
 
 1. When the script completes, a path to an HTML file is given. _On your local machine_, use `scp` to
    download it, then open it in your web browser:
@@ -511,8 +531,11 @@ collect data from it.
    simulated brake pressure signal. As you can see that when hard braking events occur (value above
    7000), collection is triggered and the engine torque signal data is collected.
 
-   Alternatively, if your AWS account is enrolled with Amazon QuickSight or Amazon Managed Grafana,
-   you may use them to browse the data from Amazon Timestream directly.
+   Alternatively, if your upload destination was set to `TIMESTREAM` and AWS account is enrolled
+   with Amazon QuickSight or Amazon Managed Grafana, you may use them to browse the data from Amazon
+   Timestream directly. **Note**: Amazon Timestream for Live Analytics is only available to
+   customers who have already been onboarded in that region. See
+   [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html).
 
    ![](./images/collected_data_plot.png)
 

docs/dev-guide/images/can-over-someip-demo-diagram.jpg

@@ -116,16 +116,19 @@ previous section.
    The demo script will save a set of varables about the run to a demo.env file, which can be used
    by other scripts such as request-forward.sh or cleanup.sh.
 
-   When the script completes, you can view the data forwarded by the second and third campaigns in
-   Timestream, as well as the demo output file(s). A path to an HTML file is given. _On your local
-   machine_, use `scp` to download it, then open it in your web browser:
+   When the script completes, you can view the data forwarded by the second and third campaigns to
+   S3, as well as the demo output file(s). A path to an HTML file is given. _On your local machine_,
+   use `scp` to download it, then open it in your web browser:
 
    ```bash
    scp -i <PATH_TO_PEM> ubuntu@<EC2_IP_ADDRESS>:<PATH_TO_HTML_FILE> .
    ```
 
-   Alternatively, if your AWS account is enrolled with Amazon QuickSight or Amazon Managed Grafana,
-   you may use them to browse the data from Amazon Timestream directly.
+   Alternatively, if your upload destination was set to `TIMESTREAM` and AWS account is enrolled
+   with Amazon QuickSight or Amazon Managed Grafana, you may use them to browse the data from Amazon
+   Timestream directly. **Note**: Amazon Timestream for Live Analytics is only available to
+   customers who have already been onboarded in that region. See
+   [the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html).
 
    As you explore the forwarded data, you can see the brake data from campaign 2 as well as the
    network type signal from campaign 3.
@@ -163,16 +166,18 @@ end time will be passed through to the IoT Job document by the script. The scrip
 argument must be an ISO 8601 UTC formatted time string. e.g. `--end-time 2024-05-25T01:21:23Z`
 
 When the request-forward.sh script completes, you can view the data forwarded by the first campaign
-which was requested through IoT Jobs in Timestream, as well as the demo output file(s). A path to an
-HTML file is given. _On your local machine_, use `scp` to download it, then open it in your web
-browser:
+which was requested through IoT Jobs in S3, as well as the demo output file(s). A path to an HTML
+file is given. _On your local machine_, use `scp` to download it, then open it in your web browser:
 
 ```bash
 scp -i <PATH_TO_PEM> ubuntu@<EC2_IP_ADDRESS>:<PATH_TO_HTML_FILE> .
 ```
 
-Alternatively, if your AWS account is enrolled with Amazon QuickSight or Amazon Managed Grafana, you
-may use them to browse the data from Amazon Timestream directly.
+Alternatively, if your upload destination was set to `TIMESTREAM` and AWS account is enrolled with
+Amazon QuickSight or Amazon Managed Grafana, you may use them to browse the data from Amazon
+Timestream directly. **Note**: Amazon Timestream for Live Analytics is only available to customers
+who have already been onboarded in that region. See
+[the availability change documentation](https://docs.aws.amazon.com/timestream/latest/developerguide/AmazonTimestreamForLiveAnalytics-availability-change.html).
 
 As you explore the forwarded data, you can now see the engine data from campaign 1, in addition to
 the data from the other campaigns.