The repository contains the instructions and code that allows you to reproduce the demo shown in the session Achieving environmental parity through multiple layers of abstractions helps to support AWS IoT FleeWise edge on EWAOL at SOAFEE Virtual Symposium 2022.
The demo will walk you through the exercise of running on EWAOL the AWS IoT FleeWise Edge. The AWS IoT FleeWise Edge will run in a container and the orchestration will be done with k3s. We can use the exact same container image both in the cloud and on a physical target, as long as they are based on an ARM v8 core. We also show how the cdk8s framework can improve the software development process abstracting the orchestration layer.
Deploy Cloud 9 in one of the supported regions
Acknowledge the creation of the stack and press the button Create stack on the bottom right.
The demo-soafee-aws-iotfleetwise-cloud9 CloudFormation stack will take about 3 minutes to be created.
When stack creation has finished, open Cloud9 and, in a terminal, run the following script to create the cdk stack that will deploy all the cloud resources as shown on the architecture above
cd ~/environment/demo-soafee-aws-iotfleetwise
./scripts/resize-c9.sh 20
./scripts/deploy-cloud.shThe above commands will take about 10 minutes to complete. While you wait we encorage you to appreciate how the cloud resources gets deployed through CDK leveraging the AWS IoT FleetWise Construct Library having a look to this file.
This is the quickest option to see AWS IoT FleetWise running without having to build the EWAOL AMI, as detailed in the next paragraph.
We will be using the same orchestrator (k3s) used in EWAOL, so let's get started by installing it
curl -sfL https://get.k3s.io | sh -
sudo ln -s /usr/local/bin/kubectl /usr/bin/kubectlBuild the Vehicle Simulator container image that will feeding signals on the CAN Bus Data where the AWS IoT FleetWise Edge is listening on
sudo ./scripts/build-vsim.shLoad certificate and private key for the vehicle into k3s secrets. These have been created by ./scripts/deploy-cloud.sh above
sudo /usr/local/bin/kubectl create secret generic private-key --from-file=./.tmp/private-key.key
sudo /usr/local/bin/kubectl create secret generic certificate --from-file=./.tmp/certificate.pemDeploy the kubernetes manifest to k3s
./scripts/deploy-k3s.shThe script shows you the AWS IoT FleetWise Edge log. If you stop the script with CTRL+C, this will terminate the containers. As such, if you want to run other commands without stopping the containers, open another terminal.
Now you can connect to the Vehicle Simulator Webapp opening the Cloud9 preview
You can try changing things such as opening/closing the vehicle doors and observe how the data signals values are fed into our Amazon Timestream table. You can either use Amazon Timestream console to run the query or you can paste the command below in one of the Cloud9 terminals.
aws timestream-query query --query-string \
"SELECT * FROM FleetWise.FleetWise WHERE time > ago(5m) ORDER BY time DESC LIMIT 2" \
| jq -r '.Rows[].Data[].ScalarValue'Please note that DoorsState is encoded on 5 bits and the value associated with each door is shown below. The left and right reference are from the point of view of facing the road ahead, while seated inside the vehicle.
| Value | Door |
|---|---|
| 1 | Front left |
| 2 | Front right |
| 4 | Rear left |
| 8 | Rear right |
| 16 | Vehicle trunk lid |
⚠️ THIS SECTION IS UNDER CONSTRUCTION, STAY TUNED !!!
⚠️ THIS SECTION IS UNDER CONSTRUCTION, STAY TUNED !!!
From CloudFormation just delete demo-soafee-aws-iotfleetwise and demo-soafee-aws-iotfleetwise-cloud9 stacks.
This repository depends on and may incorporate or retrieve a number of third-party software packages (such as open source packages) at install-time or build-time or run-time ("External Dependencies"). The External Dependencies are subject to license terms that you must accept in order to use this package. If you do not accept all of the applicable license terms, you should not use this package. We recommend that you consult your company’s open source approval policy before proceeding.
Provided below is a list of External Dependencies and the applicable license identification as indicated by the documentation associated with the External Dependencies as of Amazon's most recent review.
THIS INFORMATION IS PROVIDED FOR CONVENIENCE ONLY. AMAZON DOES NOT PROMISE THAT THE LIST OR THE APPLICABLE TERMS AND CONDITIONS ARE COMPLETE, ACCURATE, OR UP-TO-DATE, AND AMAZON WILL HAVE NO LIABILITY FOR ANY INACCURACIES. YOU SHOULD CONSULT THE DOWNLOAD SITES FOR THE EXTERNAL DEPENDENCIES FOR THE MOST COMPLETE AND UP-TO-DATE LICENSING INFORMATION.
YOUR USE OF THE EXTERNAL DEPENDENCIES IS AT YOUR SOLE RISK. IN NO EVENT WILL AMAZON BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, CONSEQUENTIAL, SPECIAL, INCIDENTAL, OR PUNITIVE DAMAGES (INCLUDING FOR ANY LOSS OF GOODWILL, BUSINESS INTERRUPTION, LOST PROFITS OR DATA, OR COMPUTER FAILURE OR MALFUNCTION) ARISING FROM OR RELATING TO THE EXTERNAL DEPENDENCIES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, EVEN IF AMAZON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THESE LIMITATIONS AND DISCLAIMERS APPLY EXCEPT TO THE EXTENT PROHIBITED BY APPLICABLE LAW.
vsim/Dockerfile depends on third party docker/library/node container image, please refer to license section
vsim/Dockerfile depends on third party docker/library/python container image, please refer to license section