This Guidance demonstrates how to use the Internet of Things (IoT) and Amazon Kinesis Video Streams with Web Real-Time Communication (WebRTC) to monitor videos from a vehicle. Original equipment manufacturers (OEMs) can give their customers the ability to monitor low-latency videos from a vehicle for security purposes, and the video can be accessed from a variety of in-vehicle platforms and viewed on any web browser. This Guidance can help OEMs increase direct revenue and improve engagement with OEM applications and web services.
Architecture Diagram
Step 1
The vehicle authenticates to AWS IoT Core using the credentials provider service.
Step 2
The Amazon Kinesis Video Streams client connects to the signaling channel, awaiting viewer requests.
Step 3
Amazon CloudFront is the content delivery network (CDN) for the static single-page application (SPA) hosted in Amazon Simple Storage Service (Amazon S3).
Step 4
The vehicle owner logs into the mobile client. Amazon Cognito and Amazon API Gateway manage user access for the mobile client.
Step 5
The mobile client calls an API to look up the vehicles that belong to the owner. The owner then selects a specific vehicle to initiate real-time video streaming.
Step 6
The mobile client initiates a connection to the Kinesis Video Streams signaling channel, a websocket connection that the vehicle is listening to for viewer connection requests. The viewer and the vehicle negotiate connection details by sending messages to each other over the signaling channel.
Step 7
The mobile client and the vehicle establish a peer-to-peer connection. The Kinesis Video Streams client streams video data through the WebRTC peer connection, and the vehicle owner views the video stream in the mobile client.
Optionally, the WebRTC data channel can be utilized for bi-directional command and control messages. If a direct, peer-to-peer connection cannot be established, video data can be relayed through the Kinesis Video Streams Traversal Using Relays around NAT (TURN) server.
Step 1
The vehicle authenticates to AWS IoT Core using the credentials provider service.
Step 2
The Amazon Kinesis Video Streams client connects to the signaling channel, awaiting viewer requests.
Step 3
Amazon CloudFront is the content delivery network (CDN) for the static single-page application (SPA) hosted in Amazon Simple Storage Service (Amazon S3).
Step 4
The vehicle owner logs into the mobile client. Amazon Cognito and Amazon API Gateway manage user access for the mobile client.
Step 5
The mobile client calls an API to look up the vehicles that belong to the owner. The owner then selects a specific vehicle to initiate real-time video streaming.
Step 6
The mobile client initiates a connection to the Kinesis Video Streams signaling channel, a websocket connection that the vehicle is listening to for viewer connection requests. The viewer and the vehicle negotiate connection details by sending messages to each other over the signaling channel.
Step 7
The mobile client and the vehicle establish a peer-to-peer connection. The Kinesis Video Streams client streams video data through the WebRTC peer connection, and the vehicle owner views the video stream in the mobile client.
Optionally, the WebRTC data channel can be utilized for bi-directional command and control messages. If a direct, peer-to-peer connection cannot be established, video data can be relayed through the Kinesis Video Streams Traversal Using Relays around NAT (TURN) server.
Well-Architected Pillars
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
-
Operational ExcellenceRead the Operational Excellence whitepaper
WebRTC session count and minutes are counted and logged through the KVS WebRTC service. Each channel is set up on demand, so it can readily match to users. This allows for analysis of overall fleet and individual usage. Visibility into this usage can support billing or credit limits. Sessions can also be anonymized or tokenized to prevent matching to users if required by local regulation.
-
SecurityRead the Security whitepaper
CloudFront secures web application delivery by HTTPS. Amazon Cognito handles user authorization, and an Amazon Cognito token secures access to API Gateway. This architecture secures IoT device access by X.509 certification over mutual transport layer security (mTLS). These devices are granted temporary credentials to access KVS only when there is user demand.
-
ReliabilityRead the Reliability whitepaper
All cloud resources are serverless and scale with demand, helping prevent system downtime even if demand increases.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
This Guidance uses serverless systems to allow for both scalability and minimum configuration and maintenance. AWS IoT Core is purpose-built to manage permissions and configuration of a large fleet of devices, such as vehicles. KVS is built to facilitate peer-to-peer WebRTC with common signaling and support services (such as a TURN server), without infrastructure provisioning or additional configuration.
-
Cost OptimizationRead the Cost Optimization whitepaper
To help minimize data transfer charges, data transferred in and out of the AWS Region is limited to the owner by using CloudFront to distribute an active application and API Gateway for queries. Data transferred to and from the vehicle is limited to small JSON messages with changes in shadow state and temporary credentials.
-
SustainabilityRead the Sustainability whitepaper
The services in this Guidance are serverless and scale with demand, so you do not need to provision and maintain “standing” infrastructure.
Implementation Resources
The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
Related Content
[Title]
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.