Skip to main content

AWS Solutions Library

Guidance for Streaming Video from Vehicles to the Cloud on AWS

Overview

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. 

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Download the architecture diagram

Well-Architected Pillars

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.

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.

Read the Operational Excellence 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. 

Read the Security whitepaper

All cloud resources are serverless and scale with demand, helping prevent system downtime even if demand increases.

Read the Reliability 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.

Read the Performance Efficiency 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.  

Read the Cost Optimization whitepaper

The services in this Guidance are serverless and scale with demand, so you do not need to provision and maintain “standing” infrastructure. 

Read the Sustainability whitepaper

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.

Did you find what you were looking for today?

Let us know so we can improve the quality of the content on our pages